Configure and Deploy the E-Business Suite Asserter
After registering the E-Business Suite Asserter in Oracle Identity Cloud Service, you must configure and deploy the E-Business Suite Asserter that will act as an interface between an identity token issued by Oracle Identity Cloud Service and a user session created in Oracle E-Business Suite.
Create a Wallet for the E-Business Suite Asserter
For security purposes, the E-Business Suite Asserter component uses a wallet to register the client ID, client secret, and Oracle Identity Cloud Service URL as parameters.
cwallet.sso
file.
Update the E-Business Suite Asserter Configuration File
After you register the Identity Cloud Service E-Business Suite Asserter (EBS Asserter), you can configure the asserter configuration file to connect with Oracle Identity Cloud Service during authentication.
Starting from Identity Cloud Service E-Business Suite Asserter version 19.1.4-1.4.0 onward, the asserter contains a properties file called bridge.properties
. This file is located inside the ebs.war
file. You need to update the information in the bridge.properties
file, and then regenerate the ebs.war
file, before deploying it to a WebLogic Server.
Note:
For E-Business Suite Asserter versions before 19.1.4-1.4.0 release, the war file may not contain thebridge.properties
file inside. You need to create this file in a folder of the E-Business Suite Asserter's WebLogic server, update its content as per step 3, save the file, and then set an environment variable, as per the following example: export ebs_property_file="/opt/ebssdk/bridge.properties"
Configure Hostname Verification in WebLogic Console
You can configure the hostname verification in Oracle WebLogic Server Administration Console.
- Start the Oracle WebLogic Server Administration Console by entering
http://wls_host:wls_port/console
in the URL line of a web browser. For example,https://ebsasserter.example.com:7002/console
. - Log in to WebLogic console as an administrator.
- In the left panel, click Lock & Edit, expand Environment, select Servers.
- Click the name of the target server where you want to deploy the EBS Asserter. In this example, AdminServer.
- Click the SSL tab. Scroll down and expand the Advanced section.
- Update the Hostname Verification parameter with the value None, and then click Save.
- Click Activate Changes.
- Restart the servers.
Configure Keystores in WebLogic Console
If you are using Custom Trust Store in WebLogic for asserter deployment, instead of using Custom Identity and Custom Trust Store with WebLogic server, use Custom Identity and Java Trust Store. With this configuration, you do not need to import Oracle Identity Cloud Service certificate.
- Start the Oracle WebLogic Server Administration Console by entering
http://wls_host:wls_port/console
in the URL line of a web browser. For example,https://ebsasserter.example.com:7002/console
. - Log in to WebLogic console as an administrator.
- In the left panel, click Lock & Edit, expand Environment, select Servers.
- Click the name of the target server where you want to configure the keystore.
- Click Keystores under the Configuration tab.
- In the left panel, click Lock & Edit to make the changes.
- Select Custom Identity and Java Trust Store.
- Click Save and Activate Changes.
- Restart the WebLogic server.
Define the Data Source
In the Oracle WebLogic Server where E-Business Suite Asserter is deployed, you must configure database connectivity by adding data sources to your WebLogic domain. WebLogic Java Database Connectivity (JDBC) data sources provide database access and database connection management.