Installing the Order Control Application Client

8 Installing the Order Control Application Client

This chapter describes how to install the Oracle Communications ASAP Order Control Application (OCA) client. Before installing the OCA client, read these chapters:

About Order Control Application Client Session and User Configuration

Any OCA client can have sessions to one or more ASAP instances. There is a one-to-one relationship between a session and an ASAP instance.

If you are planning to operate more than 500 OCA clients, consider increasing the value of OCA_MAX_SESSIONS parameter in the ASAP.cfg file. The default number of sessions is 100.

You may also extend OCA client to connect to multiple ASAP instances by adding new server sessions to OCA client.

You can configure additional OCA client users in the Oracle WebLogic Server. For more information on configuring OCA client users, see the discussion on GUI interface security in ASAP System Administrator's Guide.

Note:

If you have errors with the OCA client and security exceptions are generated by the WebLogic Server you may need to update an OCA-related security setting within a server domain.

In the WebLogic Remote Console, navigate to the Security section, and under Realms, click on your realm (For example, myrealm).
On the General tab, locate the Check Roles and Policies for entry and change it to Web Applications and EJBs protected in DD.
Click Apply.
Restart your Oracle WebLogic Server.

Installing Oracle Communications ASAP OCA Thick Client

To install Oracle Communications ASAP OCA Thick Client:

Unzip the OCA client zip file available in the ASAP 8.0.0 software to a local folder. For Example: C:\<username>\Desktop\asap800B90ClientWin
After extraction, you will see the OCAClient directory
Open the configuration file and update the settings according to your environment: OCAClient\config\OCA.cfg
Save the changes.
Run the following script to launch the Client:
runocaclient.bat

This starts the client and automatically creates a desktop shortcut named OCA Client
You can start the OCA Client using either of the following:
- The runocaclient.bat script.
- The desktop shortcut OCA Client

Configuring the OCA Client on Systems with Multiple Interfaces or IP Addresses

If the Windows computer hosting your OCA client is configured with more than one network interface or IP address or if the hostname of your computer maps to a network address that the WebLogic Server cannot contact (for example when the OCA user is accessing ASAP over a VPN) configure your client as follows:

Open the runocaclient.bat script in a text editor.
Add the following line to JAVA_OPTS at the beginning of the script:
```
-Dweblogic.corba.client.bidir=true
```

Localizing the Order Control Application Client

Perform the following procedures to translate OCA client interface components to a language other than English:

All elements that can be translated are contained in the OCAResources.properties file. Specifically, elements that can be translated are:

Screen titles
Field labels
Informational labels (such as the number of work orders found)
Menus and their contents
List headers
OCA-specific error messages
Tooltips
OCA-populated drop-down lists

Elements that cannot be translated are:

Error messages that are generated by the OCA SRP
Data that appears within fields and data lists
Data that appears in some drop-down lists populated by systems external to the OCA client

It is not necessary to modify the OCA.cfg file.

Configuring Your Locale

To configure your locale:

On your Windows system, click Start, point to Settings, and click Control Panel. The Control Panel dialog appears.
Double-click the Clock and Region Options icon. The Clock and Region Options dropdown menu appears.
Select the target locale, such as French (Canada).

Translating the Template File

To translate the template files:

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.
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
...
```
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:\Users\XXX\Downloads\asap800BxxxClientWin\OCAClient\lib.
In the runocaclient.bat script, add the '-Duser.language=fr_ca' flag before the classpath flag.
Append the ocac_lang.jar file to the classpath.