E1: SEC: Trusted Node Configuration for Running UBES

(Doc ID 816185.1)

Last updated on MAY 30, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
Checked for relevance on 02/18/2011

Goal

We have separated our Production and non-Production environments. Each has an Enterprise Server that is the primary Security server \ Logic server with a separate Enterprise server for Batch processing.  We used the SSO Environment Configuration Tools within EnterpriseOne to create SSO Nodes, Token lifetime, and Trusted node configuration for a non-production Portal installation. We then modified the tokengen.ini file to correspond to this configuration.

The Portal install is able to utilize the configuration and Logic and Batch processes are correctly serviced by the appropriate server. However, Fat clients now must point to the non-production security server for any non-production batch jobs to complete successfully, and then repoint to the production security server for production UBE's to complete successfully. Currently the SSO configuration is only in place for the non-production environments. I would like clarification if this is expected behavior, or, is there a different setup that may alleviate this issue?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms