After You Install

Once ebXML Protocol Manager is installed and configured, it must then operate in conjunction with an eGate Project before it can perform its intended functions. You must create these Projects specifically for ebXML Protocol Manager.

See the eXchange Integrator User’s Guide and eGate Integrator User’s Guide for detailed information on incorporating these types of Projects into eGate. See Run-time Steps for a sample business scenario with Projects already created, using eXchange and ebXML Protocol Manager.

The rest of this section provides important information on steps you must take to ensure that ebXML Protocol Manager operates correctly with eGate and eXchange.

Database Scripts

eXchange allows you to collect database information and persist data about your TP profiles. eXchange provides database scripts to create and upgrade this database feature for eXchange. For more information, see the eXchange Integrator User’s Guide.

You can also track message delivery histories, using the eXchange Message Tracking feature. See Using Message Tracking for more information.

Additional Policy .jar Files Required To Run SME

To correctly use ebXML Protocol Manager, you must download and apply additional policy .jar files. This operation provides reliable cryptographic features that use libraries supplied with SeeBeyond Secure Messaging Extension (SME), contained in the SMEWebServices.sar installation file.

The type of .jar files required depends on the version of Java Virtual Machine (JVM) you are using. Refer to your JVM vendor for exact details on the specific policy .jar file requirements.

Use Table 2–1 to determine which JRE is included in your eGate Logical Host.

To download the required policy.jar files

1. Scroll to the bottom of the appropriate Web page listed in Table 2–1 for your Logical Host’s JRE.

2. Click the DOWNLOAD link for Unlimited Strength Jurisdiction Policy Files 1.4.2. (or, for AIX, Unlimited Strength Jurisdiction Policy Files 1.4.1).

3. Click the link to download the .zip file containing the required policy .jar files as follows:

   • For JRE 1.4.2, follow the link Download jce_policy-1_4_2.zip.

   • For JRE 1.4.1, follow the link Download jce_policy-1_4_1.zip.

4. Extract the following required policy .jar files:

   • local_policy.jar

   • US_export_policy.jar

5. For each of your Logical Hosts, using the extracted .jar files, replace the existing versions of these files in the following location:

   <Logical Host>\jre\lib\security\

6. If you are running a repository on AIX, also replace, using the extracted .jar files, the existing versions of these files in the following location:

   <AIX Repository>/jre/1.4.x/lib/security/

See Also

For complete information on SME, see the Secure Messaging Extension User’s Guide.

Additional File for ebXML Cryptographic Features

For ebXML, you must also download and apply an additional .jar file, xss4j.jar, for XML security. This file can be downloaded as part of the XML Security Suite, from the following Web site:

http://www.alphaworks.ibm.com/tech/xmlsecuritysuite

The only file needed is xss4j.jar. After extracting it, copy it to the following location for each Logical Host:

<logicalhost>\stcis\lib\

The directories stcis\lib\ are not created by the initial installation. They are created automatically when you first run the Logical Host. If you are copying this file to its correct location, and you have not yet run the Logical Host, you must first create the folders manually.