ASAP OCA Client SSL Configuration
(Doc ID 1514874.1)
Last updated on MAY 21, 2021
Applies to:Oracle Communications ASAP - Version 7.2.0 to 7.2.0 [Release 7.2]
Information in this document applies to any platform.
In ASAP 7.2.0 Patch 1, support for Secure Sockets Layer (SSL) connectivity between the Order Control Application (OCA) Client (both the Thick Client and the Java Applet Thin Client) and WebLogic Server was added. This allows the OCA Client to communicate with WebLogic over an SSL channel where the connection is secure and the data exchanged is encrypted.
This article describes the configuration steps for making the OCA Client communicate with a WebLogic server using SSL.
Pre 7.2.0 Patch 1 OCA Client Connectivity
Prior to 7.2.0 Patch 1, the OCA Clients connected to the WebLogic non-SSL port over t3/http.
The OCA Thick Client retrieved the WebLogic port number from the PORT parameter in the OCA client OCA.cfg configuration file. For example,
The OCA Java Applet Thin Client used the WebLogic port number from the INFO column of the tbl_server_info table of the CTRL database.
Post 7.2.0 Patch 1 OCA Client Connectivity
Starting in 7.2.0 Patch 1, OCA Clients connect to the WebLogic SSL port over t3s/https by default.
For the OCA Thick Client, a new SSL_PORT parameter in the OCA.cfg file specifies the WebLogic SSL port. The default SSL_PORT value in the OCA.cfg file is 7002. If the SSL port is not 7002, you must modify the OCA.cfg file with the correct SSL port number.
When SSL_PORT is specified in the OCA.cfg file, the OCA Thick Client connects to WebLogic using the specified SSL port, even if a non-SSL port is also specified in the OCA.cfg file.
In the following example, the OCA Thick Client connects to the WebLogic server SSL port 17002:
For the OCA Java Applet Thin Client, the syntax of the tbl_server_info INFO field is extended. SSL ports are indicated by the “SSL:” prefix. For example: The INFO value “SSL:17002” would indicate that port 17002 is an SSL port, whereas “23456” would indicate that port 23456 is a non-SSL port.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Pre 7.2.0 Patch 1 OCA Client Connectivity|
|Post 7.2.0 Patch 1 OCA Client Connectivity|
|ASAP Installation and Upgrade Considerations|
|Installing and Configuring the OCA Thick Client to Use SSL|
|Configuring the OCA Thin Client to use Self-Signed Certificates|
|OCA Applet (Versions up to and including 22.214.171.124 and 126.96.36.199)|
|OCA Web Start (Versions 188.8.131.52+ and 184.108.40.206+)|
|Creating a Self-Signed Custom Identity/Keystore|
|Troubleshooting OCA Client SSL errors|