Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Before You Begin
  4. Pre-Installation Tasks
  5. B2B Data Exchange Installation
  6. Post-Installation Tasks
  7. Installing the Partners Portal on Non-B2B Data Exchange Nodes
  8. Upgrading B2B Data Exchange
  9. Starting and Stopping B2B Data Exchange
  10. Optional B2B Data Exchange Configuration
  11. Installing and Configuring the B2B Data Exchange Accelerator for Data Archive
  12. Uninstallation

B2B Data Exchange Installation and Configuration Guide

B2B Data Exchange Installation and Configuration Guide

Configuring a PowerCenter Integration Service to Access B2B Data Exchange

Configuring a PowerCenter Integration Service to Access
B2B Data Exchange

During the
B2B Data Exchange
installation or upgrade, you define a PowerCenter Integration Service that
B2B Data Exchange
uses to run workflows. If required, you can configure a different PowerCenter Integration Service to access
B2B Data Exchange
.
In the Java classpath for the PowerCenter Integration Service, add the path to the
B2B Data Exchange
class files.
  1. Log in to the Administrator tool and select the PowerCenter Integration Service that runs the workflows for
    B2B Data Exchange
    .
  2. On the
    Processes
    tab, edit the Java SDK ClassPath property and add the location of the
    B2B Data Exchange
    Java classes at the beginning of the ClassPath property:
    <B2B Data Exchange installation directory>
    \powercenter\lib\activemq-broker-5.16.5.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\activemq-client-5.16.5.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\activemq-kahadb-store-5.16.5.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\activemq-spring-5.16.5.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\dx-client-powercenter-10.5.3.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\commons-logging-1.1.3.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\log4j-1.2-api-2.17.1.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\log4j-api-2.17.1.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\log4j-core-2.17.1.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\log4j-slf4j-impl-2.17.1.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\slf4j-api-1.7.25.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\activemq-broker-5.16.2.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\activemq-client-5.16.2.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\activemq-kahadb-store-5.16.2.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\activemq-spring-5.16.2.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\geronimo-spec-j2ee-management-1.0-M1.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\geronimo-spec-jms-1.0-M1.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\geronimo-spec-jta-1.0-M1.jar;
    <B2B Data Exchange installation directory>
    \powercenter\lib\hawtbuf-1.11.jar
    If the installation log file lists invalidated subscriptions, manually run them. You can find the installation log file in the following directory: <Data Integration Hub installation directory>/logs
    During the upgrade, Data Integration Hub invalidates the automatic relational database subscriptions that have the following configurations:•
    Subscription field mapping.•
    Subscription delivery strategy is to insert new rows and update rows that exist in the target.
    For more information about running the subscriptions manually, see the Data Integration Hub Operator
    You can reference the libraries if the you can access the
    <B2B Data Exchange installation directory>
    from PowerCenter, or you can copy the library files locally.
  3. Add environment variables to the
    B2B Data Exchange
    console and server integration services.
    Integration Service
    Environment Variable
    DX_CONSOLE_URL
    rmi://<HostName>:<dx.tpm.rmi.port>
    DX_SERVER_URL
    rmi://<HostName>:<dx.rmi.port>
    You can find the RMI port numbers for the console and server in the following location:
    <Data Integration Hub installation directory>\conf\dx-configuration.properties
    By default:
    • dx.tpm.rmi.port
      : 18096
    • dx.rmi.port
      : 18095
  4. Save the changes.

0 COMMENTS

We’d like to hear from you!