Manually configuring the properties files

Although most configuration tasks can be performed by using the WebSphere Partner Gateway - Express GUI, you may find it useful to perform manual configuration for the following tasks:

The following sections describe how to configure timeout property values and how and when to use JACL scripts for manual configuration.

Configuring timeout values

If a trading partner takes a long time to process a message and send the MDN back, WebSphere Partner Gateway - Express may fail with a timeout message. To fix this problem or prevent it from happening, you can configure the following timeout property values: the synchronous/socket connection timeout value and the asynchronous MDN timeout value. The following steps describe how to configure timeout property values.

Configuring synchronous/socket connection timeout value

The following steps describe how to configure the synchronous/socket connection timeout value.

  1. Open the bcg.properties file. This file is located in the following directory.
    <ProductDir>/config
  2. Find the following property:
    bcg.connector.sender.as2parm.SyncMDNtimeout=60000
  3. Change the number 60000 to represent a new number of milliseconds.
  4. Save and close the file.

Configuring asynchronous MDN timeout value

The following steps describe how to configure the asynchronous MDN timeout value.

  1. Open the partner.properties file for the trading partner whose MDN timeout value you want to configure. This file is located in the following directory: <ProductDir>/config/partners/<name_of_parner>
  2. Find the following property:
    bcg.connector.sender.as2.parm.MDNTimeout=10
  3. Change the number 10 to represent a new number of minutes.
  4. Save and close the file.

Using JACL scripts for manual configuration

Although most of the configuration tasks can be done in the WebSphere Partner Gateway - Express GUI, the following JACL scripts are provided for manual configuration. You can invoke the scripts by following the instructions provided inside each script. The JACL scripts are located at <ProductDir>/jaclScripts.

Note:
For detailed instructions on running the bcgSetCRLDP.jacl script, see Running the bcgSetCRLDP.jacl script.

Important:
Any WAS configuration changes made manually or through the WebSphere Partner Gateway - Express GUI require the WAS server to be restarted.

Table 6. JACL scripts
JACL script Description
bcgApplication.jacl This script is used for installing, uninstalling, or updating the application. It also sets the WAS extended class path (ws_ext_dirs).
Caution:
This JACL file works on the existing application deployment, so you must supply the appropriate arguments to the scripts.
bcgClientAuth.jacl This script sets the client authentication required flag.
bcgCustomService.jacl This script sets up the custom service.
bcgSetCRLDP.jacl This script enables or disables CRL distribution point checking when the revocation check is performed. See Running the bcgSetCRLDP.jacl script for instructions on using this script.
bcgJavaWorkingDirectory.jacl This script sets the current working directory for JVM.
bcgSetJVMHeapAttrs.jacl This script changes the initial heap size and maximum heap size of the JVM for WAS.
bcgSsl.jacl This script configures the WAS server for inbound SSL server authentication. It configures the WAS server's keystore and truststore.
Caution:
This JACL file modifies the SSL inbound keystore and truststore file entries in the security.xml file. If you give incorrect entries to the script's arguments, the WebSphere Partner Gateway - Express server will fail to start.

Copyright IBM Corp. 2003, 2005