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. Migrating OEM Managed File Transfer Endpoint
  12. Installing and Configuring the B2B Data Exchange Accelerator for Data Archive
  13. Uninstallation

Installation and Configuration Guide

Installation and Configuration Guide

Verify the Database Requirements

Verify the Database Requirements

Verify that your database meets the requirements for running
B2B Data Exchange
.
The following table describes the database requirements for
B2B Data Exchange
:
Database Component
Description
Database System
Type of database on which to install the repositories. You can use one of the following database systems:
  • Oracle
  • Microsoft SQL Server
If you install the Dashboard and Reports component, you do not need to install the operational data store on the same machine on which 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 Configuring Repository Connections on PowerCenter Version 10.
Disk space
512 MB of disk space for the core application.
You also need additional space based on the number of
messages that you need to process and the type of processing required
.
The frequency of message archiving also affects the disk space requirement.
Database connections
One or more
database connections must always be available.
The number of required connections depends on the number of
endpoints and the number of documents processed
concurrently. Use the following formula to calculate the number of required database connections :
(
NumberOf
Endpoints + Maximum number of concurrent processes + 3)
X 3 + 2
If you do not have enough database connections available,
B2B Data Exchange
might fail or encounter database deadlocks.

Database Unicode Support

If you require Unicode support, create the
B2B Data Exchange
repository database with the following settings:
  • Oracle databases: use the AL32UTF8 Unicode character set.
  • Microsoft SQL Server: it is recommended that you use data types that support Unicode data: nchar, nvarachar, and ntext.

Microsoft SQL Server Collation

If you use Microsoft SQL Server, the collation for the
B2B Data Exchange
repository must not be case sensitive.

0 COMMENTS

We’d like to hear from you!