Table of Contents
Advertisement
the flexibility to decide which documents are to be persisted in the message store.
You can choose not to store an inbound, outbound or both inbound and outbound
WebSphere Partner Gateway documents in message store.
For example, to configure the message store option for an AS2 connection between
a trading partner and a internal partner, perform the following steps:
1. Create a partner connection between AS > None.
2. List the partner connection between trading partner and internal partner.
3. Edit the attributes for the AS2 package and set the Message Store Required
4. Edit the attributes for the none package and set the Message Store Required
See the WebSphere Partner Gateway Hub Configuration Guide for more information
about setting the message store attributes at the package, protocol, and document
type.
Prerequisite to setup WebSphere Partner Gateway - WebSphere
Transformation Extender Integration Environment
Before you begin
Here are the prerequisites required to setup the integration environment of
WebSphere Partner Gateway and WebSphere Transformation Extender:
1. WebSphere Partner Gateway V6.2 is installed and running.
2. WebSphere Transformation Extender V8.2 is installed and running.
3. WebSphere Transformation Extender server must have access to the WebSphere
4. Copy the dtxpi.jar from the WebSphere Transformation Extender installation
5. Restart WebSphere Partner Gateway bcgdocmgr server to pick up the new jar
6. Add WebSphere Transformation Extender installation directory in the system
7. If using the WebSphere Transformation Extender RMI Server, then start the
8. Open a command prompt and access WebSphere Transformation Extender
9. In WebSphere Partner Gateway console, provide values for the attributes:
40
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide
attribute to Yes.
attribute to No.
Partner Gateway common file system.
directory into the directory <WebSphere Partner Gateway Install>\router\lib\
userexits. This jar file contains the WebSphere Transformation Extender
runtime classes that are required to invoke WebSphere Transformation Extender
for performing the transformation.
files.
path even if you are not using the WebSphere Transformation Extender RMI
Server, instead running the environment locally. Restart WebSphere Partner
Gateway to pick up the new path settings.
Server.
install directory. Enter the command startRMIServer.bat -verbose. The
verbose option will display the port number of the RMI Server that it is
listening.
v wtx.rmihostname
v wtx.rmiport
v rmiuseserver
v bcg.wtx.mapLocation, which is under system administration tab
Advertisement
Table of Contents
