Oracle E-Business Suite Integrated SOA Gateway Implementation Guide Release 12.1 Part Number E12169-06 | Contents | Previous | Next |
After successfully installing Oracle E-Business Suite Integrated SOA Gateway, implementors or integration repository administrators need to perform the following necessary setup tasks to enable its functions and establish the connection to application database schema at run time:
For detailed information on how to install and enable Oracle E-Business Suite Integrated SOA Gateway upgraded from earlier releases, see Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12, My Oracle Support Knowledge Document 556540.1 for details.
For troubleshooting information on potential problem symptoms and corresponding solutions for Oracle E-Business Suite Integrated SOA Gateway, see Oracle E-Business Suite Integrated SOA Gateway Troubleshooting Guide, Release 12, My Oracle Support Knowledge Document 726414.1 for details.
Note: If you are planning to use the Java APIs for Forms interfaces published in Oracle Integration Repository that encapsulate Oracle Forms logic, see Troubleshooting Oracle Supply Chain Management Web Services, My Oracle Support Knowledge Document 966982.1 for troubleshooting information related to Oracle Supply Chain Management Web services.
Before enabling ASADMIN user, make sure that all workflow agent listeners, service components, background engines, and notification mailers are all up and running. You can verify the information in Oracle Workflow Manager. Otherwise, the 'Apps Schema Connect Role' (UMX|APPS_SCHEMA_CONNECT) assignment will not be reflected correctly to the ASADMIN user after it is enabled.
Note: Ensure that the APPLSYS.WF_ERROR queue is enabled in order for the Workflow Deferred Notification Agent Listener to run.
Use the following steps to enable ASADMIN user:
Log in to Oracle E-Business Suite with an administrator role and choose the User Management responsibility in the Navigator.
Click the Users link from the navigation menu to open the User Maintenance window.
Enter information in the search area to locate the ASADMIN user.
Click the Update icon next to the ASADMIN user to open the Update User window.
Remove the Active To date field and click Apply.
Click the Reset Password icon next to the ASADMIN user to open the Reset Password window.
Enter new password twice and click Submit.
After the ASADMIN user is enabled from Oracle E-Business Suite, you must perform the following tasks:
Verify if the ASADMIN user has the 'Apps Schema Connect Role' (UMX|APPS_SCHEMA_CONNECT) role in wf_user_roles.
If the 'Apps Schema Connect Role' role is not present in the wf_user_roles for the ASADMIN user, then run the 'Workflow Directory Services User/Role Validation' concurrent program to grant the role.
Reset the ASADMIN password in the file system.
Update the file as shown below to reset the password:
$INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml
<user>
<name>ASADMIN</name>
<display-name>Default Apps SOA User</display-name>
<description>Used by SOAProvider for DB connection</description>
<credentials>!<NEW PASSWORD></credentials>
</user>
Note: The password should be preceded by a '!' (Exclamation) so that when OAFM is started, it gets encrypted. For example, if the password is 'welcome', then you have to change it to "!welcome". In addition, the password of ASADMIN should be synchronized between system-jazn-data.xml file and the database through the application user interfaces.
Caution: Do not use the same password given in this example for "ASADMIN" user. Use different password instead to avoid some potential security risk in your system.
Bounce the middle-tier and retry the generation process.
An appropriate Oracle E-Business Suite user account should be created to establish the Applications database connection at run time. If you do not want to use the default user ASADMIN who is enabled during the installation for database connection, alternatively you can create another Oracle E-Business Suite user account for establishing the connection.
Use the following steps to create an Oracle E-Business Suite user account in Oracle User Management and then configure user in technology stack:
Use Oracle User Management to create an Oracle E-Business Suite user account in addition to the default user ASADMIN that has been enabled during the installation.
You can create an account using either one of the following ways:
Create a new user account without using an existing user
This approach lets you create a new user account and add the newly created user information to the application schema and TCA schema simultaneously. And this new user will automatically become an Oracle E-Business Suite user.
Create a user account by using an existing user
If you have an existing Oracle E-Business Suite user that you want to use, then use this approach by first locating the user, and then creating an account associated with it.
To create a new user account without using an existing user:
Log in to Oracle E-Business Suite with an administrator role and choose the User Management responsibility in the Navigator.
Click the Users link from the navigation menu to open the User Maintenance window.
To register or create a new person, select 'External Organization Contacts' from the Register drop-down list and click Go.
In the Register Business Contact window, enter appropriate information for the new user for whom you want to have an account created:
E-mail: Enter an appropriate e-mail address
First Name: Enter the first name of the person
Last Name: Enter the last name of the person
Organization: Select an appropriate organization
Phone Number: Optionally enter the person's contact number
In the Account Information region, select one of the following options for the account password:
Generate Automatically: This allows the system to automatically generate the password.
Enter Manually: The system prompts you to enter the password and a confirmation of the password.
Click Submit. A confirmation message appears indicating that the new Oracle E-Business Suite user account has been created.
To create a user account by using an existing user:
Log in to Oracle E-Business Suite with an administrator role and choose the User Management responsibility in the Navigator.
Click the Users link from the navigation menu to open the User Maintenance window.
Enter information in the search area to locate the appropriate user for whom you wish to create an account.
Please note that only those users who are part of the application schema and present in either HR database or TCA database will be displayed in the search result.
Click the Create User icon next to the person's name if the account does not exist. This opens the Create User Account window.
Enter the appropriate information in the Create User Account window including e-mail address, active dates, and password.
Click Submit.
After creating an Oracle E-Business Suite user account, you will grant the 'Apps Schema Connect Role' (UMX|APPS_SCHEMA_CONNECT) user role to the user. Thus, the user will have the privilege to access the Applications database schema at run time.
To grant a user role to the user:
Log in to Oracle E-Business Suite with an administrator role and choose the User Management responsibility.
Select the Users link from the navigation menu.
Enter appropriate information in the search area to locate either an existing user account or the user account that you just created in Creating an Oracle E-Business Suite User Account. Click Go.
Click the Update icon next to the user with 'Active' account status to open the Update User window.
Click Assign Roles.
In the search window, search for the 'Apps Schema Connect Role' (UMX|APPS_SCHEMA_CONNECT). Choose this role and click Select.
Enter a justification in the Justification filed and click Apply.
You will see a confirmation message indicating you have successfully assigned the role.
Once a new user account is created and assigned with the 'Apps Schema Connect Role' role, you must configure the user in technology stack. This configuration allows the new user to be used by SOA Provider for the application database connection at run time.
To configure the user in technology stack:
Set the context variable s_soaprovider_user to the new user that you just created in Creating an Oracle E-Business Suite User Account.
Use the following steps to modify $INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml:
Please note that this file will not be overwritten when AutoConfig is run; therefore, user name and password are preserved.
Change ASADMIN user to the new user that you just created in Creating an Oracle E-Business Suite User Account.
Change the password for the ASADMIN user to the password which was provided while creating the new user.
Note: The password should be preceded by a '!' (exclamation) so that when OAFM oc4j is started, it gets encrypted. For example, if the password is 'welcome', then you have to change it to '!weclome'.
The password of ASADMIN should be synchronized between system-jazn-data.xml file and the database through the application user interfaces.
The following example shows the information details on user name and password change:
Existing Values:
<user>
<name>ASADMIN</name>
<display-name>Default Apps SOA User</display-name>
<description>Used by SOAProvider for DB connection</description>
<credentials>!ASADMIN</credentials>
New Values:
<user>
<name>New_User</name>
<display-name>Default Apps SOA User</display-name>
<description>Used by SOAProvider for DB connection</description>
<credentials>!New_PASSWORD</credentials>
Run AutoConfig.
Oracle E-Business Suite Integrated SOA Gateway uses profile options to set necessary parameters in determining appropriate service providers for XML Gateway Map service enablement and enabling SOA auditing feature.
Specifically, these profiles determine the following features:
Appropriate service providers that are used in enabling services for XML Gateway Maps.
The availability of the SOA Monitor auditing feature.
The following table lists the profile options used in Oracle E-Business Suite Integrated SOA Gateway:
Profile Option | Description | Required | Default Value |
---|---|---|---|
FND: XML Gateway Map Service Provider | Use this profile option to select an appropriate service provider in enabling services for XML Gateway Map interface type. Based on the selected profile value, the interface details page displays an appropriate Web Service region or more than one region. You can select one of the following three profile values:
| Yes | SOAP (SOA Provider)
Important: If you do not start from this release and your system has Web Service Provider based service integration for enabling generic XML Gateway services, set the profile option to 'Both' (Web Service Provider and SOA Provider) instead. This allows the Web Service - Web Service Provider region and the Web Service - SOA Provider region to be displayed simultaneously if Web services are available. Otherwise, Web Service Provider will be disabled and any invocations of generic XML Gateway Web services will return a fault message. |
SOA: Web Service Audit | Use this profile option to enable/disable the SOA auditing feature. If it is enabled, SOAP request and response messages are audited in SOA Monitor. | Yes | ON Please note that this profile value can be overridden by clicking on the Turn Off Audit or Turn On Audit button in the SOA Monitor main page. For example, clicking Turn Off Audit will override the default value and disable the SOA Monitor auditing feature. |
For information on how to set profile options, see Oracle E-Business Suite System Administrator's Guide - Maintenance for details.
Copyright © 2008, 2010, Oracle and/or its affiliates. All rights reserved.