The following procedure describes how to add new server sessions for a given OCA client.

OCA users that have access privileges to multiple OCA sessions can select one or more sessions to use when performing order queries or audit log queries.

You need to perform the following procedure only if you intend to add new session configurations; ASAP installation automatically creates one session to the OCA JSRP.

To add new server session configurations to the OCA web client application:

1. To open the web-based client, open a web browser and type:

   http://WebLogic_host:WebLogic_port/ASAP_envID/OCA
   

   For example: http://10.15.15.15:7001/AS47/OCA

   WebLogic_host is the WebLogic host on which ASAP is deployed and WebLogic_port is the WebLogic port.

   ASAP_envID is the ASAP environment ID. An ASAP system can have multiple ASAP instances with multiple environments.

   The OCA Web Client Configuration screen appears.

   Note:

   For information on how to open OCA web client using https connection, see ASAP OCA Client SSL Configuration (Doc ID 1514874.1) knowledge article on My Oracle Support.

2. Click Add Server Session Configuration.

3. Supply the following information.

   • ASAP Environment ID: The ASAP environment ID is a unique identifier for each ASAP environment within an ASAP instance. Maximum of four alphanumeric characters.

   • Control Database Host: This is the host name or IP address of the ASAP Database Server.

   • Control Database Port: Enter Control Database Port.

   • Control Database Name: The name of the control database for the ASAP instance.

   • Control User Name: The control database user ID.

   • Control User Password: The control database user password.

   • WebLogic Administrator: WebLogic Server system administration login ID.

   • WebLogic Password: WebLogic Server system administration login password.

   • WebLogic Target Server: The name of the WebLogic Server for the ASAP instance.

4. Click Add Server Session.

   A message appears confirming the successful addition of the server session, or any errors related to the addition of the server session.

5. Click Continue to return to the OCA Web Client Configuration screen. The new server session appears in the Registered Server Sessions list.

To launch an OCA thin client server session:

1. Open a web browser and type:

   http://WebLogic_Host:WebLogic_port/ASAP_envID/OCA
   

   For example: http://10.15.15.15:7001/AS47/OCA

   WebLogic_host is the WebLogic host on which ASAP is deployed and WebLogic_port is the WebLogic port.

   ASAP_envID is the ASAP environment ID. An ASAP system can have multiple ASAP instances with multiple environments.

   The OCA Web Client Configuration screen appears.

2. Select a server to launch from the Select from the following Registered Server Sessions list.

3. Set the following global parameters:

   • Language Code: Language code for the language in which translatable information is returned to and displayed by the client. If applied, all translatable fields are shown in the OCA client native language, as specified by the LANGUAGE variable.

   • Idle Timeout: Maximum idle time, in minutes, after which the OCA SRP server terminates the OCA client connection. Set to zero (0) to disable this feature.

   • Events Supported: Enables the propagation of SARM events.

   • Max Open Windows: The number of detail windows a user can have open at one time.

   • Default Template: The template (user or global) that will be selected by default in the Order Entry Wizard after OCA client is launched.

   • Date Format: The date format that will be displayed in the OCA client including in work order headers, the Work Order Query window and its results, the Work Order Release dialog box, audit logs, report generation dialog boxes, and in standard ASAP reports. This date format is also displayed in OCA Console log (messages in OCA Console window), New Work Order window, Work Order Details window, and Events Message Board window.

4. Click Launch Selected Server Sessions.

   Note:

   The ASAP installer creates a user named ASAP_admin that you can use to access the OCA client. Users with the access privileges can change the default user name and password using the WebLogic Server Administration Console.

To configure your locale:

1. On your Windows system, click Start, point to Settings, and click Control Panel. The Control Panel dialog appears.

2. Double-click the Regional and Language Options icon. The Regional and Language Options dialog appears.

3. Select the target locale, such as "French (Canada)".

To configure your browser if you are running the OCA applet:

1. Open the web browser and select Tools > Internet Options.

2. In the General tab, click Languages.

3. In the Language Preference dialog, click Add.

4. Ensure that "French(Canada)[fr-ca]" and "English(United States)[en-us]" are included in the list.

5. Click OK.

To translate the template files:

1. Open the OCAResources.properties file and save it with a different name. For example, if you are producing a French properties file, you could name it OCAResources_fr_ca.properties.

2. Open the OCAResources_fr_ca.properties file and translate the values to the right of the equals sign as required. For example:

   # OCA Frame Temp Action
   TMP_ACTION=Ajouter
   TMP_ASDLDELAYFAIL=ASDL insuccès retardée
   TMP_ASDLRETRY=ASDL réessayage
   ...
   

3. Package the translated OCAResources_fr_ca.properties file into a new JAR file (ocac_lang.jar).

   For example, type:

   jar uvf ocac_lang.jar
   

   For the OCA client (Windows platform), ocac_lang.jar is located in $OCA_ClientHOME\lib.

   For example, C:\Program Files\Oracle Communications\ASAP\OCAClient\lib.

   If you are running OCA as a web application, you must copy the OCAResources_fr_ca.properties to the UNIX platform using FTP, compile it, and package it to ocac_lang.jar on the server side. On the server side, ocac_lang.jar is normally bundled in asapENV.ear.

4. In the Target command, add the "-Duser.language=fr_ca" flag before the classpath flag.

5. Append the ocac_lang.jar file to the classpath.