B2B Data Transformation Installation (for Windows)

Installing and configuring B2B Data Transformation (B2BDT) on new or existing hardware, either in conjunction with PowerCenter or co-existing with other host applications on the same server.

Note: B2B Data Transformation was formerly called Complex Data Exchange (CDE). Any references to PowerExchange Complex Data Exchange in this document are now referred to as B2B Data Transformation (B2BDT).

Consider the following questions when determining what type of hardware to use for B2BDT: If the hardware already exists:
1. Is the processor, operating system supported by B2BDT?
2. Are the necessary operating system and patches applied?
3. How many CPUs does the machine currently have? Can the CPU capacity be expanded?
4. How much memory does the machine have? How much is available to the B2BDT application?
5. Will B2BDT share the machine with other applications? If yes, what are the CPU and memory requirements of other applications?

If the hardware does not already exist:
1. Has the organization standardized on hardware or operating system vendor?
2. What type of operating system is preferred and supported?
Regardless of the hardware vendor chosen, the hardware must be configured and sized appropriately to support the complex data transformation requirements for B2BDT.
Among other factors, the hardware requirements for the B2BDT environment depend upon the data volumes, the number of concurrent users and the application server and operating system used. For exact sizing recommendations, contact Informatica Professional Services for a B2BDT Sizing and Baseline Architecture engagement.

Planning for the B2BDT Installation
There are several variations of the hosting environment from which B2BDT services will be invoked. This has implications on how B2BDT is installed and configured.
Host Software Environment

The most common configurations are:
1. B2BDT to be used in conjunction with PowerCenter
2. B2BDT as a stand alone configuration
3. B2BDT in conjunction with a non-PowerCenter integration using an adapter for other middleware software such as WebMethods or Oracle BPEL.

B2BDT 4.4 includes a mechanism for exposing B2BDT services through web services so that they can be called from applications capable of calling web services.
Depending on what host options are chosen, installation options may vary.

Installation of B2BDT for a PowerCenter Host Environment:-
Be sure to have the necessary licenses and the additional plug-in to make PowerCenter work. Refer to the appropriate installation guide or contact Informatica support for details on the installation of B2BDT in PowerCenter environments.

Installation of B2BDT for a Standalone Environment:-

When using B2BDT services in a standalone environment, it is expected that one of the invocation methods (e.g., Web Services, .Net, Java APIs, Command Line or CGI) will be used to invoke B2BDT services. Consult accompanying B2BDT documentation for use in these environments.

Non-PowerCenter Middleware Platform Integration:-
Be sure to plan for additional agents to be installed. Refer to the appropriate installation guide or contact Informatica support for details for installing B2BDT in nvironments other than PowerCenter.

Other Decision Points:-
Where will the B2BDT service repository be located?

The choices for the location of the service repository are i) a path on the local file system or ii) use of a shared network drive. The justification for using a shared network drive is typically to simplify service deployment if two separate B2BDT servers want to share the same repository. While the use of a shared repository is convenient for a
multi-server production environment it is not advisable for development as there could be a danger of multiple development teams potentially overwriting the same project files.

When a repository is shared between multiple machines, if a service is deployed via the B2BDT Studio, the Service Refresh Interval setting controls how fast other installations of B2BDT that are currently running detect the deployment of a service.

What are multi-user considerations?
If multiple users share a machine (but not at same time) the environment variable “IFConfigLocation4” can be used to set the location of the configuration file to point to a different configuration file for each user.

Security Considerations:-
As the B2BDT repository, workspace and logging locations are directory-based all directories to be used should be granted read and write permissions for the user identity under which the B2BDT service will run.

The identity associated with the caller of the B2BDT services will also need to have permissions to execute the files installed in B2BDT binary directory.
Special considerations should be given to environments such as web services where the user identify under which the B2BDT service runs is set to be different for the interactive user or the user associated with the calling application.

Log File and Tracing Locations:-
Log files and tracing options should be configured for appropriate recycling policies. The calling application must have permissions to read, write and delete files to the path that is set for storing these files.

B2BDT Pre-install Checklist:-
It is best to review the environment and record the information in a detailed checklist to facilitate the B2BDT install.

Minimum System Requirements:-
Verify that the minimum requirements for the Operating System, Disk Space, Processor Speed and RAM are met and record them the checklist.
B2BDT Studio requires Microsoft .NET Framework, version 2.0.
If this version is not already installed, the installer will prompt for and install the framework automatically.
B2BDT requires a Sun Java 2 Runtime Environment, version 1.5.X or above.
B2BDT bundles with the appropriate JRE version. The installer can be pointed to an existing JRE or a JRE can be downloaded from Sun.
To install the optional B2BDT libraries, reserve additional space (refer to documentation for additional information).

PowerCenter Integration Requirements:-
Complete the checklist for integration if B2BDT will be integrated with PowerCenter. For an existing PowerCenter installation, the B2BDT client needs to be installed on at least one PC on which the PowerCenter client resides. B2BDT components also need to be installed on the PowerCenter server. If utilizing an existing PowerCenter installation ensure the following:

Which version of PowerCenter is being used (8.x required)?

Is the PowerCenter version 32 bit or 64 bit?

Are the PowerCenter client tools installed on the client PC?

Is the PowerCenter server installed on the server?

For new PowerCenter installations, the PowerCenter Pre-Install Checklist should be completed. Keep in mind that the same hardware will be utilized for PowerCenter and B2BDT.

For windows Server, verify the following:-

The login account used for the installation has local administrator rights.

500Mb or more of temporary workspace is available.

The Java 2 Runtime Environment version 1.5 or higher is installed and configured.

Microsoft .NET Framework, version 2.0 is installed.

Non-PowerCenter Integration Requirements:-

In addition to the general B2BDT requirements, non-PowerCenter agents require that additional components are installed.

B2BDT Agent for BizTalk – requires that Microsoft BizTalk Server (version 2004 or 2006) is installed on the same computer as B2BDT. If B2BDT Studio is installed on the same computer as BizTalk Server 2004, the Microsoft SP2 service pack for BizTalk Server must be installed.

B2BDT Translator for Oracle BPEL – requires that BPEL 10.1.2 or above is installed.

B2BDT Agent for WebMethods – requires that WebMethods 6.5 or above is installed.

B2BDT Agent for WebSphere Business Integration Message Broker – requires that WBIMB 5.0 with CSD06 (or

WBIMB 6.0) are installed. Also ensure that the Windows platform supports both the B2BDT Engine and WBIMB.

A valid license key is needed to run a B2BDT project and must be installed before B2BDT services will run on the computer. Contact Informatica support to obtain a B2BDT license file (B2BDTLicense.cfg). B2BDT Studio can be used without installing a license file.

B2BDT Installation and Configuration:-
The B2BDT installation consists of two main components – the B2BDT development workbench (Studio) and the B2BDT Server (which is an application deployed on a server). The installation tips apply to Windows environments.

This section should be used as a supplement to the B2B Data Transformation Installation Guide.

Before installing B2BDT complete the following steps:

Verify that the hardware meets the minimum system requirements for B2BDT.

Ensure that the combination of hardware and operating system are supported by B2BDT.

Ensure that sufficient space has been allocated for the B2BDT serviceDB.

Ensure that all necessary patches have been applied to the operating system.

Ensure that the B2BDT license file has been obtained from technical support.

Be sure to have administrative privileges for the installation user id.

Adhere to the following sequence of steps to successfully install B2BDT.

1. Complete the B2BDT pre-install checklist and obtain valid license keys.

2. Install B2BDT development workbench (studio) on the windows platform.

3. Install the B2BDT server on a server machine. When used in conjunction with PowerCenter, the server component must be installed on the same physical machine where PowerCenter resides.

4. Install necessary client agents when used in conjunction with WebSphere, WebMethods and BizTalk. In addition to the standard B2BDT components that are installed by default additional libraries can be installed. Refer to the B2BDT documentation for detailed information on these library components.

B2BDT Install Components:-

The install package includes the following components.

* B2B Data Transformation Studio

B2B Data Transformation Engine

*  Document Processors

* Documentation

* Optional agents

* Optional libraries

Install the B2BDT Studio and Engine

Step 1:
Run the Windows installation file from the software folder on the installation CD and follow the prompts. Follow the wizard to complete the install.







During the installation a language must be selected. If there are plans to change the language at a later point in time in the Configuration Editor, Informatica recommends that a non-English language is chosen for the initial setup.

If English is selected and then later changed to another language some of the services that are required for other languages might not be installed.

The default installation path is C:InformaticaComplexDataExchange.

The default Service Repository Path is <INSTALL_DIR>/ServiceDB. This is the storage location for data transformations that are deployed as B2BDT services.

The default Log path is <INSTALL_DIR>/CMReports. The Log Path is the location where the B2BDT Engine stores its log files. The log path is also known as the reports path.











The repository location, JRE path and Log path can be changed subsequent to the installation using environment variables.












Step 2:
Install the license file. Verify the validity of the license file with the following command:
CM_console –v

The system displays information such as the location and validity of the license file.

Step 3:
Configure the Environment Variables.
The B2BDT setup assigns several environment variables which point to the installation directory and to other locations that the system needs.

On Windows, the B2BDT setup creates or modifies the following environment variables: ??

Step 4:
Configuration settings.
The configuration application allows for the setting of properties such as JVM parameters, thread pool settings, memory available to the studio environment and many others. Consult the administrators guide for a full list of settings and their effects.

Properties set using the B2BDT configuration application affect both the operation of the standalone B2BDT runtime environment and the behavior of the B2BDT studio environment.

To open the Configuration Editor in Windows, from the Start menu choose –
Informatica > B2BDT > Configuration










Some of the Configuration Editor settings are available for all B2BDT installations. Additional settings vary depending on the B2BDT version and the optional components installed. The Configuration Editor saves the configuration in an XML file. By default, the file is <INSTALL_DIR/CMConfig.xml>.

The B2BDT studio environment should be installed on each developers machine or environment. While advances in virtualization technologies and technologies such as Windows remote desktop connections theoretically allow for multiple users to share the same B2BDT installation, the B2BDT studio environment does not implement
mechanisms such as file locking during the authoring of transformations that are needed to secure multiple users from overwriting each others work.

An environment variable can be defined called IFConfigLocation4. The value of the variable must be the path for a
valid configuration file (i.e., c:MyIFConfigLocation4CMConfig1.xml).

For example, if two users want to run B2BDT Engine with different configurations on the same platform, store their respective configuration files in their home directories. Both files must have the name CMConfig.xml.

Alternately store a CMConfig.xml file in the home directory for one of the users. The other user will use the default
configuration file (e.g., <INSTALL_DIR>/CMConfig.xml).

Always save a backup copy of CMConfig.xml prior to editing. In the event of a problem the last known backup can be restored. The file <INSTALL_DIR>/CMConfig.bak is a backup of the original <INSTALL_DIR/CMConfig.xml> which the setup program created when B2BDT was installed. Restoring CMConfig.bak reverts B2BDT to its original

OS environment variables are used to set aspects of the system such as the Java classpath to be used, location of the configuration file for a specific user, home location for the installed B2BDT instance to be used, library paths, etc.

In-Process or Out-of-Process Invocation:-
Out-of-process invocation requires the use of the B2BDT Server application (which is already installed by the install process). The distinction is that running under server mode causes transformations to potentially run slower, but errors will be isolated from the calling process.

For Web Services, sometime the use of Server mode is recommended as the lifetime of the host process then becomes independent of the life time of the process space allocated to run the web service.

For example IIS can run web services in a mode where a process dies or is recycled after a call to web services. For B2BDT the first call after a process startup can take up to 3 seconds (subsequent calls are usually milliseconds) – hence it is not optimal to start host process on each invocation. Running in server mode keeps process lifetimes independent.

B2BDT Studio or the CM_console command, always runs data transformations in-process.

Running out-of-process has the following advantages:
Allows 64-bit processes to activate 32-bit versions of B2BDT Engine
An Engine failure is less likely to disrupt the calling application Help prevent binary collisions with other modules that run in the process of the calling application.

In-process invocation has the following advantage:

Thread pool settings











Step 5:
Configure ODBC connectivity:-
Note: this step is only needed if the ODBC database support features of B2BDT will be used. In such case, an ODBC driver may need to be configured.

Step 6:
Test the installation to confirm that B2BDT operates properly

Note: Tests are available to test the engine and document processor installation. Refer the directory
<INSTALL_DIR>setupTests for B2BDT test projects testCME and testCMDP.











B2BDT Integration With PowerCenter:-

B2BDT does support using the runtime as a “server” process to be invoked from PowerCenter on the same physical machine (in addition to offering the ability to invoke the B2BDT runtime engine in-process with the calling environment). While this does constitute a “server” process in developer terminology, it does not provide full server
administration or monitoring capabilities that are typical of enterprise server products. It is the responsibility of the calling environment to provide these features. Part of the overall solution architecture is to define how these facilities are mapped to a specific B2BDT implementation.


Your comments are always welcome here ….                                                                                                                  Skip to top