Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.


Share this Page URL
Help

Chapter 19: Enveloping and de-enveloping > Configure Company E for XML to EDI o... - Pg. 627

19.4 Configure Company E for XML to EDI outbound In this section, we perform the configuration for the outbound EDI, which encompasses the configuration of the enveloper. Note: In this example, the EDI standard is: ANSI-X12, with the protocol being X12V4R1. 19.4.1 Enable JMS WebSphere Partner Gateway uses the JMS API to interact with WebSphere MQ. The JMS API is part of the Java 2 Platform, Enterprise Edition (J2EE), specification. It is a layer that is developed on top of the standard WebSphere MQ API. You must set up the mapping between JMS objects and WebSphere MQ objects. The mapping is retrieved by the JMS API using the Java Naming and Directory InterfaceTM (JNDI) API. JNDI providers can be anything, for example Lightweight Directory Access Protocol (LDAP) servers or naming services provided by other WebSphere Application Server instances in your network or a simple file. The actual mapping commands are independent of the JNDI provider. WebSphere MQ provides the JMSAdmin tool to store the links between a JMS object and a WebSphere MQ object in a JNDI directory. Set up your choice of JNDI provider in the JMSAdmin.config configuration file, which you can find in the Java\bin directory in the WebSphere MQ installation folder. Perform the mapping on the machine where the JMS application is running, and not on the machine that runs the real JMS server (or queue manager). On the WebSphere Partner Gateway Enterprise machine, open the file jmsadmin.config in the folder C:\WMQ\Java\bin in a text editor. 1. Uncomment the INITIAL_CONTEXT_FACTORY setting for the JNDI provider of your choice. Example 19-3 on page 628 is set for the file-based JNDI provider. Each JNDI provider needs to be addressed in a different way, which is expressed via the PROVIDER_URL parameter. 2. Update the file-based URL to point to a valid directory on the file system, for example C:\WMQ\Java\JNDI. Notice that the syntax of PROVIDER_URL uses the forward slash instead of the normal backward slash of Windows Note: Make sure that you uncomment only one setting of each parameter. If you want to use multiple providers, you need to create multiple configuration files and pass the name of the configuration file as a parameter when running the tool JMSAdmin. Chapter 19. Enveloping and de-enveloping 627