Step 2. Install B2B Data Exchange on the First Node
Step 2. Install
B2B Data Exchange
on the First Node
Install
B2B Data Exchange
on the first node.
The installation of
B2B Data Exchange
on the first node is not identical to the installation on the second node. Do not perform this procedure on the second node.
Log in to the machine with the user account that you want to use to install
B2B Data Exchange
.
To prevent permission errors, use the same account to install
B2B Data Exchange
and PowerCenter.
Close all other applications.
Run the
Install.bin -i console
command.
The
Introduction
section appears.
Read the instructions, and then press
Enter
.
The
Install or Upgrade
section appears.
Select to install
B2B Data Exchange
, and then press
Enter
.
The
PowerCenter Version
section appears.
Select the PowerCenter version for which you want to install
B2B Data Exchange
, and then press
Enter
.
The
Installation Directory
section appears.
In the
Installation Directory
section, enter the absolute path to the installation directory or accept the default directory, and then press
Enter
.
The
Installation Components
section appears and displays a numbered list of the components to install.
Enter a comma-separated list of numbers for the components to install or accept the default components:
1-
B2B Data Exchange
Installs the core
B2B Data Exchange
application.
Selected by default.
2-
B2B Data Exchange
Partners Portal
Installs the
B2B Data Exchange
Partners Portal component. You must install
B2B Data Exchange
to install the Partners Portal component.
Selected by default.
3-
B2B Data Exchange
Dashboard and Reports
Installs the
B2B Data Exchange
Dashboard and Reports component. You must install
B2B Data Exchange
to install the Dashboard and Reports component.
Cleared by default.
The Dashboard using metadata directory is installed by default. Select this component to view the reports in the Dashboard using operational data store. After installation, you must ensure to set the
dx.dashboard.ods.page.show
system property to
true
to view the reports in the Dashboard using operational data store. For more information, see the
B2B Data Exchange
Administrator Guide
and
B2B Data Exchange
Operator Guide
.
If you install the Dashboard and Reports component, you must import the operational data store event loader after you install
B2B Data Exchange
.
If you install 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, you must configure the repository connections in PowerCenter Workflow Manager. For details, see
GUID-C2D5669F-F2EE-4BFB-8809-644202DB405B.
4-
B2B Data Exchange
Server Plug-in for PowerCenter
Installs the
B2B Data Exchange
PowerCenter server plug-in component. After the installation, register the plug-in to the PowerCenter repository.
Selected by default.
Press
Enter
.
The
Metadata Repository
section appears.
Select
1- Create a B2B Data Exchange repository
and press
Enter
.
The
Metadata Repository Connection
section appears.
Enter
1
to select Oracle as the
B2B Data Exchange
metadata repository database type.
Enter the number for the metadata repository database connection type:
1- Database URL
Location of the database. If you select this option, enter values in the following fields:
Database host name. Host name of the machine where the database server is installed.
Database port number. Port number for the database. Default port number is 1521.
Database SID. System identifier for the database. Enter either a fully qualified ServiceName or a fully qualified SID.
It is recommended that you enter a ServiceName in this field.
2- Custom Connection String
Connection string to the database. If you select this option, enter values in one of the following fields:
JDBC string. JDBC connection string to the database.
ODBC string. ODBC connection string to the database. Available if you install the PowerCenter client plug-in. The installer cannot verify the validity of the ODBC string.
3- Database username
Name of the database user account for the Oracle database.
4- Database user password
The password for the database account for the Oracle database.
B2B Data Exchange
stores the password as an encrypted string.
Press
Enter
.
If you selected to install the
B2B Data Exchange
Dashboard and Reports component, the
Operational Data Store
section appears. If you did not select to install the Dashboard and Reports component, go to step
17 to configure user authentication.
In the
Operational Data Store
section, enter
1- Create an operational data store repository
.
Enter values in the following fields:
1- Database URL
Location of the database. If you select this option, enter values in the following fields:
Database host name. Host name of the machine where the database server is installed.
Database port number. Port number for the database. The default port number is 1521.
Database SID. System identifier for the database. Enter either a fully qualified ServiceName or a fully qualified SID.
It is recommended that you enter a ServiceName in this field.
2- Custom Connection String
JDBC connection string to the operational data store.
3- Database username
Name of the database user account for the Oracle database.
4- Database user password
The password for the database account for the Oracle database.
B2B Data Exchange
stores the password as an encrypted string.
Press
Enter
.
The
User Authentication
section appears.
Choose the type of user authentication that you want to use.
Choose Informatica domain authentication to manage user credentials in the Informatica domain and synchronize user information with
B2B Data Exchange
.
Use Informatica domain authentication for production environments.
If you choose Informatica domain authentication, enter values in the following fields:
Gateway host
Host name of the Informatica security domain server.
B2B Data Exchange
stores the host name in the
pwc.domain.gateway
system property.
Gateway port
Port number for the Informatica security domain gateway.
B2B Data Exchange
stores the port number in the
pwc.domain.gateway
system property. Use the gateway HTTP port number to connect to the domain from the PowerCenter Client. You cannot use the HTTPS port number to connect to the domain.
Password
Password of the Informatica security domain user.
Username
User name to access the Administrator tool. You must create the user in the Administrator tool and assign the
manage roles/groups/user
privilege to the user.
Security domain
Name of the Informatica security domain where the user is defined.
Security group
Optional. Security group within the Informatica security domain where
B2B Data Exchange
users are defined in the following format:
<security group>@<domain>
If you leave the field empty, the Informatica security domain synchronizes only the
B2B Data Exchange
administrator user account.
B2B Data Exchange
stores the security group in the dx.authentication.groups system property in the following format:
uses this value for the user name and password when you log in to the Operation Console.
Press
Enter
.
The
Document Store
section appears.
Enter the directory where
B2B Data Exchange
stores documents and files during processing or accept the default directory, and then press
Enter
.
The document store directory must be accessible to
B2B Data Exchange
, PowerCenter services, and Data Transformation.
Press
Enter
.
The
Web Server
section appears.
Configure the Web Server connection.
Enter the number for the network communication protocol or accept the default protocol:
1- Enable HTTPS
Instructs
B2B Data Exchange
to use secure network communication when you open the Operation Console in the browser.
If you select HTTPS and HTTP, the Operation Console switches existing HTTP connections with HTTPS connections.
2- Enable HTTP
Instructs
B2B Data Exchange
to use regular HTTP network communication when you open the Operation Console in the browser.
If you selected
Enable HTTPS
, enter values in the following fields:
Connector port number
Port number for the Tomcat connector to use when you open the Operation Console with HTTPS.
The default value is 18443.
Use a keystore file generated by the installer
Instructs the installer to generate a keystore file with an unregistered certificate. If you select this option, ignore the security warning that you receive from the browser the first time you open the Operation Console.
Use an existing keystore file
Instructs the installer to load an existing keystore file. Enter values in the following fields:
Keystore password. Password for the keystore file.
Keystore file. Path to the keystore file.
The keystore file must be in the Public Key Cryptography Standard (PKCS) #12 format.
If you selected
Enable HTTP
, enter values in the following fields:
HTTP connector port number
Port number for the HTTP connector. If you clear this field, your browser must connect to the
B2B Data Exchange
server with HTTPS when you log in to the Operation Console.
The default value is 18080.
Server shutdown listener port number
Port number for the listener that controls the Tomcat server shutdown.
The default value is 18005.
Press
Enter
.
The
Port Numbers
section appears.
Enter the port number for the
B2B Data Exchange
JMS Broker JMX listener port or accept the default port, and then press
Enter
.
If you selected to install the
B2B Data Exchange
server plug-in for PowerCenter or the
B2B Data Exchange
client plug-in for PowerCenter components, the
PowerCenter Location
section appears. If you did not select to install the PowerCenter server or client components, go to step
26.
Enter the directory where you installed PowerCenter or accept the default directory, and then press
Enter
.
Enter
1
to connect to the PowerCenter Web Services Hub, and then press
Enter
.
Enter the URL that the PowerCenter Web Services Hub uses
when
B2B Data Exchange
transfers documents to PowerCenter for processing with batch workflows
or accept the default directory, and then press
Enter
.
The
PowerCenter Repository Service
section appears.
Enter the name of the PowerCenter repository service, and then press
Enter
.
Enter values in the following fields:
Node host name
Host name of the node that runs the PowerCenter Repository Service.
Node port number
Port number of the node that runs the PowerCenter Repository Service.
Username
Name of the PowerCenter Repository Service user.
Password
Password for the PowerCenter Repository Service user.
B2B Data Exchange
stores the password as an encrypted string.
Security domain
Optional. Name of the Informatica security domain in which the PowerCenter Repository Service user is stored.
Default is Native.
Press
Enter
.
If you selected to install the
B2B Data Exchange
server plug-in for PowerCenter component, the
Informatica Domain
section appears. If you did not select to install the PowerCenter server component, go to step
33.
Enter values in the following fields:
Domain name
Name of the Informatica domain that contains the PowerCenter Integration Service that runs
B2B Data Exchange
workflows.
Node name
Node in the Informatica domain on which the PowerCenter Integration Service runs.
Domain administrator user name
Name of the Informatica domain administrator.
Domain administrator password
Password for the Informatica domain administrator.
B2B Data Exchange
stores the password as an encrypted string.
Press
Enter
.
Enter the name of the PowerCenter Integration Service that
B2B Data Exchange
uses to run workflows, and then press
Enter
.
Verify that the installation information is correct, and then press
Enter
.
During the installation process, the installer displays progress information.
If you installed the
B2B Data Exchange
PowerCenter server plug-in, follow the on-screen instructions to register the plug-in to the PowerCenter repository, and then press
Enter
.
To view the log files that the installer generates, navigate to the following directory:
<
DX
InstallationDir>\logs
Perform the required post-installation tasks. For more information, see the section "Post-Installation Tasks" in the
B2B Data Exchange
Installation and Configuration Guide
.
Perform only the tasks that are relevant for your environment.
Optionally, perform additional configuration tasks. For more information, see the section "Optional