Optional configuration includes tasks that you might want to perform after you install or upgrade
B2B Data Exchange
, or at a later date.
The
B2B Data Exchange
components send information through ports. You can change the default port numbers based on the requirements of your network environment.
When different components process information or encounter errors, log files contain information that you can use to analyze and troubleshoot the installed components. You can change the location of the log files or define custom logs.
To increase performance and reliability, you can change the maximum memory allocation for the
B2B Data Exchange
JMS Broker service, the
embedded
B2B Data Exchange
server broker, or the embedded
B2B Data Exchange
console broker.
If you change the database user credentials for the
B2B Data Exchange
repository
or for the operational data store, you must update the
B2B Data Exchange
configuration files. If you are running the Dashboard and Reports component, you must also update the relevant PowerCenter connections.
If you use the Dashboard and Reports component, and the IP addresses of the machine that hosts
B2B Data Exchange
change any time after the installation, you must update the IP addresses in the dashboard configuration file.
For the
B2B Data Exchange
Dashboard and Reports component, you can specify a user name, password, and location for the operational data store user account.
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
.
If you use the Dashboard and Reports component, your
B2B Data Exchange
and operational data store repositories are installed on Microsoft SQL Servers, and you use PowerCenter version 10, configure the repository connections in PowerCenter Workflow Manager.
If you want to change JMS broker communication settings, configure attributes to modify control of the JMS broker.
To use the Active MQ Web Console to troubleshoot JMS broker communications, access the Active MQ Web Console, then use the predefined username and password.
If you installed the Informatica Managed File Transfer component, perform the following procedures:
Configure the relevant
B2B Data Exchange
system properties and restart
B2B Data Exchange
before you try to access Informatica Managed File Transfer from the Operations Console.
You must enable SSO with Informatica Managed File Transfer before you try to access Informatica Managed File Transfer from the Operations Console. To enable SSO, copy the keystore from the Informatica Managed File Transfer server and the install an SSO key on the
B2B Data Exchange
server.
Share the
B2B Data Exchange
download directory and the Informatica Managed File Transfer Web User directories with both
B2B Data Exchange
and Informatica Managed File Transfer Web.
If you create a custom project in Informatica Managed File Transfer, ensure that you include specific variables to pass information from
B2B Data Exchange
system properties.
Before you create endpoints that run Informatica Intelligent Cloud Services tasks, ensure that you have an active account and license, and are assigned the appropriate user roles.