10  Command Line Utilities

Using the command-line utility, you can invoke both Refresh Application Data Interface and Refresh Target Datastore process.

Topics:

·        Prerequisites

·        Invoking the Command Line Utilities

Prerequisites

·        You must have access and execute permission to the following directory:

·        $FIC_HOME/ficdb/bin

·        If the secured protocol is enabled for accessing the OFSAA application then “CURL_CA_BUNDLE” environment variable must be set where the application is installed. The variable points to the path where the CA certificate is available that is generated during application deployment.

·        For example: CURL_CA_BUNDLE=/usr/share/ssl/certs/ca-bundle.crt.

Invoking the Command Line Utilities

To invoke the command-line utility for refreshing ADI and Target Datastore, follow these steps:

1.     Once the prerequisites are met, navigate to $FIC_HOME/ficdb/bin path and execute RefreshADI.sh and then RefreshDS.sh. This expects two mandatory parameters:

a.     The information Domain name where DIH is installed. It is mandatory to enter this in uppercase.

b.     OFSAA Login ID, which can be specified in either lower or uppercase.

2.     For example, see the following window.

a.     For Refreshing Application Data Interface, use the following command:

b.     ./RefreshADI.sh <INFODOM_NAME> <OFSAA_USER>

Figure 99: Refreshing Target Datastore command

Description of Invoking the Command Line Utilities Window This illustration displays command-line utility for refreshing ADI and Target Datastore.

a.     For Refreshing Target Datastore, use the following command:

b.     ./RefreshDS.sh <INFODOM_NAME> <OFSAA_USER>

Figure 100: Refreshing Target Datastore command

Description of Invoking the Command Line Utilities Window This illustration displays command-line utility for refreshing ADI and Target Datastore.

NOTE:   

If the webserver is Websphere, an error message is displayed in the console as “Refresh Target Datastore as fail”.

Verify this from the application window, and ignore the message in the command prompt and proceed.

If the webserver is Weblogic, an error message is displayed "curl: (35) SSL connect error". In this case, invoke the process from the application window and proceed.