Installing and Configuring Microsoft BizTalk Adapters for Enterprise Applications

Installing and Configuring Microsof...

This document provides instructions for installing and configuring Microsoft® BizTalk® Adapters for Enterprise Applications for both BizTalk Server 2006 and BizTalk Server 2006 R2. As auxiliary information, it also provides instructions for installing and configuring Microsoft BizTalk Adapter v2.0 for mySAP™ Business Suite Service Pack 1.

Microsoft BizTalk Adapters for Enterprise Applications includes the following adapters:

Microsoft BizTalk Adapter for J.D. Edwards EnterpriseOne
Microsoft BizTalk Adapter for J.D. Edwards OneWorld XE
Microsoft BizTalk ODBC Adapter for Oracle Database
Microsoft BizTalk ODBC Adapter for Oracle E-Business Suite
Microsoft BizTalk Adapter for PeopleSoft Enterprise
Microsoft BizTalk Adapter for Siebel eBusiness Applications
Microsoft BizTalk Adapter for TIBCO Enterprise Message Service
Microsoft BizTalk Adapter for TIBCO Rendezvous

Important
You must be experienced with the specific enterprise application before you make any configuration changes to your enterprise applications.

Caution
You should back up all data before making any configuration changes.

This document has two parts. The first part describes the requirements before installing each adapter. The second part describes how to install each adapter. To make sure that you are reading the most up-to-date information, download the latest version of this document at http://go.microsoft.com/fwlink/?LinkId=56392.

Adapter Requirements

This section describes software requirements and preparation steps for each adapter. For installation information, see Installing BizTalk Adapters for Enterprise Applications later in this document.

Requirements for BizTalk Adapter for J.D. Edwards EnterpriseOne

BizTalk Adapter for J.D. Edwards EnterpriseOne enables you to use J.D. Edwards EnterpriseOne business functions within BizTalk Server. For more detailed information about the adapter, see the specific Help documentation for the adapter that is installed with BizTalk Adapters for Enterprise Applications. For information about J.D. Edwards EnterpriseOne, see the documentation for the application.

Supported Operating Systems

BizTalk Adapter for J.D. Edwards EnterpriseOne runs on the following operating systems:

Microsoft Windows Server® 2003 R2
Microsoft Windows Server 2003 with Service Pack 1
Microsoft Windows® 2000 with Service Pack 4
Microsoft Windows XP with Service Pack 2

Supported J.D. Edwards EnterpriseOne Versions

BizTalk Adapter for J.D. Edwards EnterpriseOne supports the following J.D. Edwards EnterpriseOne versions:

J.D. Edwards EnterpriseOne 8.10, 8.11, and 8.12
Tools Release 8.93, 8.94, 8.95, and 8.96

Required Servers

BizTalk Adapter for J.D. Edwards EnterpriseOne requires the following servers to install and configure the adapter:

BizTalk server
EnterpriseOne Server. It is needed for copying the .jar files to the BizTalk server.

Required Components

BizTalk Adapter for J.D. Edwards EnterpriseOne requires the following components on the server where the adapter is installed.

BizTalk Server 2006 or BizTalk Server 2006 R2
Sun Microsystems Java Development Kit (JDK) version 1.4.2 or later
JDBC drivers for J.D. Edwards EnterpriseOne databases

Required Files

BizTalk Adapter for J.D. Edwards EnterpriseOne uses the following .jar files at both runtime and design time:

Version	Required Files
8.10 with Tools Release version 8.93, 8.94, 8.95, and 8.96	Connector.jar Kernel.jar database.jar jdeutil.jar log4j.jar xerces.jar
8.11 with Tools Release version 8.94, 8.95, and 8.96	Connector.jar Kernel.jar database.jar jdeutil.jar log4j.jar xerces.jar
8.12 with Tools Release version 8.96	ApplicationAPIs_JAR.jar ApplicationLogic_JAR.jar Base_JAR.jar BizLogicContainer_JAR.jar BizLogicContainerClient_JAR.jar Connector.jar jdbj.ini JdbjBase_JAR.jar JdbjInterfaces_JAR.jar jdeinterop.ini jdelog.properties JdeNet_JAR.jar log4j.jar PMApi_JAR.jar Spec_JAR.jar System_JAR.jar xalan.jar xerces.jar
All versions	The JDBC files for the corresponding database (For Microsoft SQL Server™ 2000 JDBC driver, the adapter requires msbase.jar, mssqlserver.jar, and msutil.jar.)
All versions	JDEDynAccess.jar (installed with the adapter)

Prerequisites for Installing BizTalk Adapter for J.D. Edwards EnterpriseOne

Before installing BizTalk Adapter for J.D. Edwards EnterpriseOne, you must configure the BizTalk server for the adapter installation by following these basic steps:

Copy the J.D. Edwards .jar files from the EnterpriseOne server to the BizTalk server
Install the JDK 1.4.2 or later
Install the JDBC driver

Copying the J.D. Edwards .Jar Files from the EnterpriseOne Server to the BizTalk Server

The J.D. Edwards .jar files are listed in the previous Required Files section. As previously mentioned, you must copy the .jar files to the BizTalk server. They can be copied to any location on the BizTalk server. These files will be referenced from the Transport Properties dialog box while you create the send ports.

Installing the JDK 1.4.2 or Later

You can download the JDK 1.4.2 or later from the Sun Microsystems Web site. Follow the instructions on the site to install it on the BizTalk server.

Installing the JDBC Driver

BizTalk Adapter for J.D. Edwards EnterpriseOne calls the J.D. Edwards EnterpriseOne API that uses JDBC, which needs a driver for the database. If you install J.D. Edwards EnterpriseOne with a SQL Server database, you need MS-SQL drivers. Similarly, if you installed J.D. Edwards EnterpriseOne with an Oracle database, you will need Oracle drivers; or if you installed with a DB2 database, you will need DB2 drivers.

If you are using Oracle DatabaseType, you must add extra information to the jdeinterop.ini file. Specifically, you must add the database parameter to the [JDBj-ORACLE] section, which defines the Oracle tnsnames location. You must also ensure that Oracle’s SQLNET.ORA file is present on the BizTalk server. Using the information from the J.D. Edwards EnterpriseOne’s jde.ini file, add the following to the adapter’s jdeinterop.ini file:

[JDBj-ORACLE]
tns=c:\Oracle\ora92\network\Admin\tnsnames.ora
[JDBj-BOOTSTRAP DATA SOURCE]
Database=sys810

Understanding Jdeinterop.ini

The Connect.jar and Kernel.jar files use the jdeinterop.ini file to configure connection parameters to the J.D. Edwards OneWorld XE server. We recommend that you not edit this file manually because it interacts with the Transport Properties dialog box for the BizTalk send port. Specifically, you should not modify those fields marked as Configured_by_BizTalk in the following table.

The J.D. Edwards EnterpriseOne connector classes in Connector.jar and Kernel.jar require that you use a configuration file named jdeinterop.ini. This file is defined by the J.D. Edwards EnterpriseOne application and uses its terminology. For more information about the purpose and terminology of this file, see the J.D. Edwards Interoperability Guide. There is a sample jdeinterop.ini file in: C:\Program files\Program Files\Microsoft BizTalk Adapters for Enterprise Application\J.D. Edwards EnterpriseOne\config folder. The following table gives a short description of the entries in that file:

Parameters	Description
[SERVER] glossaryTextServer=Configured_by_BizTalk codePage=1252	glossaryTextServer: the enterprise server and port that provide glossary text information, for example, JDED:6010. This is the server that returns text descriptions for errors. This is often the same host and port as the J.D. Edwards EnterpriseOne application server. There may be more than one glossary server for different supported language encodings. codePage: the encoding scheme. Here is a list of commonly used code page numbers: 1252 English and Western European 932 Japanese 950 Traditional Chinese 936 Simplified Chinese 949 Korean
[JDENET] serviceNameConnect=Configured_by_BizTalk enterpriseServerTimeout=1200000 maxPoolSize=30 netTrace=false	enterpriseServerTimeout: the time-out value for a request to the enterprise server, for example, 90000. maxPoolSize: the JDENET socket connection pool size, for example, 30.
[JDBj-BOOTSTRAP SESSION] User=Configured_by_BizTalk Password=Configured_by_BizTalk Environment=Configured_by_BizTalk Role=*ALL	The information in this section should match the corresponding information specified in the [DB SYSTEM SETTINGS] section of this installation's jde.ini file.
[JDBj-BOOTSTRAP DATA SOURCE] name=Configured_by_BizTalk server=Configured_by_BizTalk databaseType=Configured_by_BizTalk physicalDatabase=Configured_by_BizTalk serverPort=Configured_by_BizTalk owner=Configured_by_BizTalk	The information in this section should match the corresponding information specified in the [DB SYSTEM SETTINGS] section of this installation's jde.ini file.

Requirements for BizTalk Adapter for J.D. Edwards OneWorld XE

BizTalk Adapter for J.D. Edwards OneWorld XE enables you to use J.D. Edwards OneWorld XE business functions within BizTalk Server. For more detailed information about the adapter, see the specific Help documentation for the adapter that is installed with BizTalk Adapters for Enterprise Applications. For information about J.D. Edwards OneWorld XE, see the documentation for the application.

Supported Operating Systems

BizTalk Adapter for J.D. Edwards OneWorld XE runs on the following operating systems:

Microsoft Windows Server 2003 R2
Microsoft Windows Server 2003 with Service Pack 1
Microsoft Windows 2000 with Service Pack 4
Microsoft Windows XP with Service Pack 2

Supported J.D. Edwards OneWorld XE Versions

BizTalk Adapter for J.D. Edwards OneWorld XE supports the following J.D. Edwards OneWorld XE versions:

B7.3.3.3 with Service Pack 23
B7.3.3.4 with Service Pack 23

Required Servers

BizTalk Adapter for J.D. Edwards OneWorld XE requires the following servers to install and configure the adapter:

J.D. Edwards enterprise server. This server can be on any of the operating systems supported by J.D. Edwards OneWorld XE.
J.D. Edwards Deployment server. This server is used for installing the BTSREL Application Software Update and creating BTSLIBInterop.jar. This server has to be on a Windows operating system.
BizTalk server. This is the server where the adapter is installed. The adapter can run on both BizTalk Server 2006 and BizTalk Server 2006 R2.

Note
The architecture of BizTalk Adapter J.D. Edwards OneWorld XE is documented in the BizTalk Server Help. For more information about the architecture, see http://go.microsoft.com/fwlink/?LinkId=95285.

Required Components

BizTalk Adapter for J.D. Edwards OneWorld XE requires the following components on the server where the adapter is installed:

BizTalk Server 2006 or BizTalk Server 2006 R2
Sun Microsystems Java Development Kit (JDK) version 1.4.2 or later. It is required on the deployment server in order to create BTSLIBInterop.jar.

BizTalk Adapter for J.D. Edwards OneWorld XE Installation Process Overview

The following figure shows the installation and configuration process for BizTalk Adapter for J.D. Edwards OneWorld XE.

Providing BTSREL.exe
Installing the planner update Electronic Software Update (ESU)
Installing the BTSREL application software update (ASU)
Applying the BTSREL ASU to J.D. Edwards OneWorld XE environments
Creating and building the BTSREL custom business function library manually
Creating and deploying a full package
Creating BTSLIBInterop.jar
Copying the J.D. Edwards .jar files and BTSLIBInterop.jar to the BizTalk server
Installing the JDK 1.4.2 or later
Installing BizTalk Adapter for J.D. Edwards OneWorld XE
Adding BizTalk Adapter for J.D. Edwards OneWorld XE to BizTalk Server
Creating send ports
Communication is established from the BizTalk server to the enterprise server

You must perform the following steps before installing BizTalk Adapter for J.D. Edwards OneWorld XE and after J.D. Edwards OneWorld XE has been installed and configured on the deployment server and the enterprise server. These steps must be performed by a J.D. Edwards Configurable Network Computing (CNC) specialist or administrator:

Installing planner update Electronic Software Update (ESU)
Installing the BTSREL application software update (ASU)
Applying the BTSREL ASU to J.D. Edwards OneWorld XE environments
Creating and building BTSREL custom business function library manually
Creating and deploying a full package
Creating BTSLIBInterop.jar
Copying the J.D. Edwards .jar files and the BTSLIBInterop.jar to the BizTalk server

You need to repeat step 3 through 5 on each environment that BizTalk Server will connect to.

In some of the procedures, we use the following names for common J.D. Edwards environments:

Environment Name	Description
JDEPLAN	Common name for the planning environment.
DV7333	Common name for the development environment.
PY7333	Common name for the prototype environment.
PD7333	Common for name for the production environment.
DEP7333	Common for name for the deployment environment.

Installing Planner Update Electronic Software Update (ESU)

You must perform this step on the deployment server. You can skip this step if the deployment server has got a planner update with SAR #4533357 already installed.

The planner update must be installed before installing the BTSREL application software update (ASU) provided by Microsoft. BizTalk Adapter for J.D. Edwards OneWorld XE requires SAR #4533357 in the planner update. The planner update gets superseded each time. You can install JD24819 or later that includes SAR #4533357.

To install the planner update ESU

Download the planner update that includes SAR #4533357 from J.D. Edwards - Update Center on the Oracle Web site.
Extract the planner update.
Run setup.exe, and follow the steps in the wizard.

After the planner update is installed, you need to complete the following steps:

Creating/updating the Internet Code Change ODBC data source
Copying the new Object Configuration Mappings to the Planner ODBC data source and the System ODBC data source
Copying control table information to the planner update Access database
Copying bitmaps to the planner update directory

Creating/Updating the Internet Code Change ODBC Data Source

This step needs to be performed every time you install a new planner update on the deployment server.

Each planner update includes a Microsoft Office Access database. The database is in the <J.D. Edwards OneWorld XE installation folder>\<OneWorld XE version>\PLANNER\DATA directory. It is a requirement to have an ODBC data source called "Internet Code Change" pointing to the Access database on the deployment server. When the planner update is installed for the first time, you need to make sure that there is an ODBC data source with the name. Otherwise, you must create one through the ODBC Data Source Administrator from Administrative Tools. When you create the data source, you must choose Microsoft Access Driver (.mdb). For the subsequent planner update installations, you just need to re-map the data source to the appropriate Access database.

Copying New Object Configuration Mappings to the Planner ODBC Data Source and the System ODBC Data Source

This step needs to be performed every time you install a new planner update on the deployment server.

This step copies the new object configuration mappings (OCM) into the Planner ODBC data source and the System ODBC data source.

To copy new OCM mappings into the Planner ODBC data source and the System ODBC data source

Click Start, point to Programs, and click JDEdwards OneWorld to open J.D. Edwards OneWorld Explorer.
Log on to the JDEPLAN environment as user JDE, the default administrator account.
In the fast path box, enter P98305 (batch version), and then press Enter.
In Batch Application, enter R98403 (report), and press Enter.
Highlight version XJDE0029, and then click Processing Options on the left panel to open the Processing Options dialog box.
In the Processing Options dialog box, click the Environment tab, and then enter the following values:

Processing Option Value

1

(The name of the planner environment, for example, JDEPLAN)

2

(Leave it blank)

3

2

4

Internet Code Change

5

(Leave it blank)
In the Processing Options dialog box, click the Update tab, and then enter the following values:

Processing Options Value

6

1

7

(Leave it blank)

8

(Leave it blank)

9

Y
In the Processing Options dialog box, click the Print tab, and then verify that option 10 is blank.
In the Processing Options dialog box, click the Licensing tab, and then verify that options 11 and 12 are blank.
In the Processing Options dialog box, click OK to close the dialog box.
Double-click XJDE0029 to run the version.
Select the Data Selection check box, and click OK to submit.
Double-click XJE0029.
Select the Data Selection check box, and then click Submit menu button.
In the Data Selection dialog box, change Data Selection to:
```
Where ‘BC Object Name’ = F986101
```
Click OK to close the Data Selection dialog box. The Processing Options dialog box opens.
Click OK to close the Processing Options.
Double-click XJDE0029 to run the version again.
Highlight XJDE0029, and then click Processing Options on the left panel to open the Processing Options dialog box.
In the Processing Options dialog box, click the Environment tab, and then enter the following value:

Processing Option Value

1

(The name of the deployment environment, for example, DEP7333.)
In the Processing Options dialog box, click OK to close the dialog box.
Double-click XJDE0029 to run the version.
Select the Data Selection check box, and then click OK to submit.
Double-click XJE0029.
Select the Data Selection check box, and then click Submit menu button.
In the Data Selection dialog box, change Data Selection to:
```
Where ‘BC Object Name’ = F986101
```
Click OK to close the Data Selection dialog box. The Processing Options dialog box opens.
Click OK to close the Processing Options dialog box.
Double-click XJDE0029 to run the version again.

Processing Option	Value
1	(The name of the planner environment, for example, JDEPLAN)
2	(Leave it blank)
3	2
4	Internet Code Change
5	(Leave it blank)

Processing Options	Value
6	1
7	(Leave it blank)
8	(Leave it blank)
9	Y

Processing Option	Value
1	(The name of the deployment environment, for example, DEP7333.)

Copying Control Table Information to the Planner Update Access Database

This step only needs to be performed once on the deployment server. You can skip it if you have already performed it during a previous planner update installation.

This step copies new Data Dictionary items and new Universal Data Connection (UDC) codes into the planner update Access database.

Note
When you apply the planner update after installing J.D. Edwards OneWorld XE, you will see errors in jde.log indicating that you are trying to insert duplicate values into F0004 and F0005. This is expected behavior, since you have already copied the new UDC values in this step.

To copy control table information to the planner update Access database

Double-click version XJDE0029.
Select the Data Selection check box, and then click the Submit menu button.

In the Data Selection dialog box, change Data Selection to:

Where BC Object Type = TBLE and BC Object Name = F0004 F0005 F9200 F9202 F9203 F9207 F9210

Click OK to close the Data Selection dialog box. The Processing Options dialog box opens.
In the Processing Options dialog box, click the Environment tab, and then enter the following values:

Processing Option Value

1

JDEPLAN

2

(Leave it blank)

3

2

4

Internet Code Change

5

(Leave it blank)
In the Processing Options dialog box, click the Update tab, and then enter the following values:

Processing Options Value

6

1

7

(Leave it blank)

8

(Leave it blank)

9

Y
In the Processing Options dialog box, click the Print tab, and then verify that option 10 is blank.
In the Processing Options dialog box, click the Licensing tab, and then verify that option 11 and option 12 are blank.
In the Processing Options dialog box, click OK to close the dialog box.
Click OK to run the report.

Processing Option	Value
1	JDEPLAN
2	(Leave it blank)
3	2
4	Internet Code Change
5	(Leave it blank)

Processing Options	Value
6	1
7	(Leave it blank)
8	(Leave it blank)
9	Y

Copying Bitmaps to Planner

You perform this step only once using the deployment server. You can skip it if you have already performed it during a previous planner update installation.

You need to copy all the bitmaps from the following folder: <J.D. Edwards OneWorld XE installation folder>\<OneWorld XE version>\PLANNER\Package\<current ESU version>\res folder to <J.D. Edwards OneWorld XE installation folder>\<OneWorld XE version>\PLANNER\res.

Installing BTSREL Application Software Update (ASU)

You must perform this step needs on the deployment server.

BTSREL is a custom package, or an Application Software Update (ASU) in J.D. Edward terms. An ASU is a post-release update that provides software changes for specific purposes, such as regulatory changes or enhancements. It contains business functions to extract metadata and custom functions within J.D. Edward environments.

These ASUs are created for specific functionality. For example, BTSREL is created to extract metadata. When the BTSREL ASU is installed, it updates selected modules in the J.D. Edwards OneWorld XE environment. To update, BTSREL objects must be merged into the appropriate J.D. Edwards OneWorld XE environment.

You can download BTSREL from http://go.microsoft.com/fwlink/?LinkId=93673. You must install it on the deployment server which runs on a Windows operating system, and then deployed it to the enterprise server.

Note
When applying the ASU to the deployment server, check the processing option to verify that you are in Update mode. The Proof mode verifies that there are no bugs in the ASU, whereas Update mode is for when you apply the ASU.

To install BTSREL on the deployment server

Log on to Windows on the deployment server as user JDE.
Create a new folder named BTSREL in the <J.D. Edwards OneWorld XE installation folder>\<OneWorld XE version> folder.
Copy BTSREL.exe to the newly created folder.
Run BTSREL.exe to start the J.D. Edwards OneWorld XE Installation Manager.
Click Next.
Click Finish. After the installation finishes, a dialog box informs you if the installation was successful.

Applying BTSREL ASU to J.D. Edwards OneWorld XE Environments

This step needs to be performed on the deployment server.

After BTSREL is installed on the deployment server, you must apply it to the environments where you want the update installed.

To apply BTRREL ASU to a J.D. Edwards OneWorld XE environment

Log on to the JDEPLAN environment as user JDE on the deployment server.
In the fast path box, enter GH9612, and then press Enter.
Double-click Application Software Update.
On the Work with Software Updates screen, double-click the BTSREL ASU to select BTSREL ASU, and then click Next menu button.
Double-click the environments where you want the update installed, and then click Next menu button.
1. If you want the software update to run in unattended mode, select the Unattended Workbench check box.
2. If you want the backup of the specifications (so that the original specifications can be restored), select the Backup check box.
Click Next to apply it to the environment. See the automatically generated PDFs for any errors that may occur after the installation is finished.

Note
If errors occur, refer to the J.D. Edwards OneWorld XE Software Update Guide for troubleshooting tips, or contact J.D. Edwards OneWorld XE directly.

Note
If errors occur, refer to the J.D. Edwards OneWorld XE Software Update Guide for troubleshooting tips, or contact J.D. Edwards OneWorld XE directly.

Creating and Building the BTSREL Custom Business Function Library Manually

This step needs to be performed on the deployment server.

Because of a limitation of the J.D. Edwards OneWorld XE product packaging process, you must manually register the custom Business Function Library DLL created by BTSREL with J.D. Edwards OneWorld XE. This process consists of the following three steps:

Creating the Custom Business Function Library
Building the library to create the DLL
Copying the Custom Business Function Library DLL

Step 1: Creating the BTSREL Custom Business Function Library

Using J.D. Edwards OneWorld XE Object Management Workbench (OMW), create the Custom Business Function Library. You must perform the following procedure on the initial setup.

To create the BTSREL custom business function library

Click Start, point to Programs, and then click JDEdwards OneWorld to open J.D. Edwards OneWorld Explorer.
Log on to the environment with which the BizTalk server will communicate, for example, DV7333, as user JDE.
In the fast path box, enter P98220 (OMW), and then press Enter.
Click the Add menu button.
In the Object Librarian Objects area, click Business Function.
Enter the following information for the New Business Function Library Object:

Name Value

Name

BTSLIB

Description

Microsoft BizTalk JDE Adapter DLL

Product Code

55

Product System Code

55
Click OK.

Name	Value
Name	BTSLIB
Description	Microsoft BizTalk JDE Adapter DLL
Product Code	55
Product System Code	55

Step 2: Building the Library to Create the DLL

You must perform the following procedure on the initial setup.

To create the dll

Click Start, and then click Run.
From the Run window, enter busbuild.exe, and then click OK. You are prompted to log on to J.D. Edwards OneWorld XE.
Log on to the J.D. Edwards environment where the BizTalk server will talk as user JDE.
Right-click BTSLIB from the function list, and then select Build.
In the output screen, verify that all DLLs have been built successfully.

Step 3: Copying the Custom Business Function Library DLL

Copy the custom DLL from the path code directory to the parent package directories on the deployment server and on the enterprise server as follows:

To copy the custom DLLs by using the deployment server

Copy BTSLIB.dll from <J.D. Edwards OneWorld XE installation folder>\<OneWorld XE version>\<environment>\BIN32 to <J.D. Edwards OneWorld XE installation folder>\<OneWorld XE version>\<environment>\PACKAGE\<environment>FA\BIN32.
Copy BTSLIB.def, BTSLIB.dmp, and BTSLIB.mak from <J.D. Edwards OneWorld XE installation folder>\<OneWorld XE version>\<environment>\obj folder to <J.D. Edwards OneWorld XE installation folder>\< OneWorld XE version>\<environment>\PACKAGE\<environment>FA\obj folder.
Copy BTSLIB.exp, BTSLIB.lib, and sBTSLIB.lib from <J.D. Edwards OneWorld XE installation folder>\< OneWorld XE version>\<environment>\lib32 folder to <J.D. Edwards OneWorld XE installation folder>\< OneWorld XE version>\<environment>\PACKAGE\<environment>FA\lib32 folder.
On the enterprise server, create a folder called BTSLIB under <J.D. Edwards OneWorld XE installation folder\<OneWorld XE version>\packages\DV7333FA\source folder. After the folder is created, verify the folder access authorization.
Copy b5500901.c from the <J.D. Edwards OneWorld XE installation folder\<OneWorld XE version>\DV7333\source directory on the deployment server to the <J.D. Edwards OneWorld XE installation folder\<OneWorld XE version>\packages\DV7333FA\source\BTSLIB directory on the enterprise server.
Copy b5500901.h from the <J.D. Edwards OneWorld XE installation folder\<OneWorld XE version>\DV7333\include directory on the deployment server to the <J.D. Edwards OneWorld XE installation folder\<OneWorld XE version>\packages\DV7333FA\include directory on the enterprise server.

Building and Deploying the Full Package

This step needs to be performed on the deployment server.

The full package is mandatory to get the latest specifications of BTSREL ASU.

Because of a limitation of the J.D. Edwards package-build process, you must build a full package for each of the J.D. Edwards environments to which you applied the BTSREL ASU. Otherwise the update package build will not work correctly. For more information about building a full package, see the J.D. Edwards OneWorld XE documentation.

To build a full package

Log on to the J.D. Edwards deployment environment, for example, DEP7333, as user JDE on the deployment server.
In the fast path box, enter P9601, and then press Enter.
In the Work With Packages screen, click Add.
In the Package Assembly Director screen, click Next.
In the Package Information screen, enter the Package Name, Description, and Path Code, and click Next.

Field Name Value

Package Name

DV7333FC

Description

DV7333 full package

Path Code

DV7333
In the Package Type Selection screen, click Full, and then click Next.
In the Foundation Component screen, click Next.
In the Help Component screen, click Next.
In the Database Component screen, click Next.
In the Default Object Component screen, click Next.
In the Features Component screen, click Next.
In the Language Component screen, click Next.
In the Package Component Revisions screen, click End.
In the Work with Packages screen, highlight the package, for example, DV7333FC, and then click Active/Inactive. The box icon in front of the package will change from an opened box icon to a closed box icon.
In the Work with Packages screen, highlight the package, for example, DV7333FC, and then click Define Build.
In the Package Build Definition Director screen, click Next.
In the Package Build Location screen, select the Client check box and the Server check box, and then click Next.
In the Server Selection screen, select the enterprise server that you would like to build the package for, and then click Next
In the Build Specification Options screen, click Next.
In the Business Function Options screen, clear the Clear Output Destination First check box, and then click Next.
In the Compression Options screen, click Next.
In the Package Build Revisions screen, click End.
In the Work With Package Build Definition screen, highlight the package, for example, DV7333FC, and then click Active/Inactive.
In the Work With Package Build Definition screen, highlight the package, for example, DV7333FC, and then click Submit Build.
In the Report Output Destination screen, click On Screen, and then click OK. Two automatically generated PDFs (R9621 and R9622) appear on the screen. If there are any errors, you can check the jde.log build logs.
In the fast path box, enter GH9083, and then press Enter.
Double-click Package Deployment.
Enter the package name, and then click Find to find the package that you build.
Highlight the package, and then click Add menu button.
In the Package Deployment Director screen, click Next.
Select the package, and then click Next.
In the Package Deployment Targets screen, select both Client Workstation and Enterprise Server, and then click Next.
In the Package Deployment Attributes screen, select the Mandatory Installation check box, and then click Next.
In the Enterprise Server Selection screen, select the enterprise server name, and click Next.
In the Work with Package Deployment screen, click End.
Click Close.
In the fast path box, enter P9631, and then press Enter.
Enter the package name, for example, DV7333FC, and then click Find to find the package.
Expand the package, expand the enterprise server, select the build, and then click Active/Inactive.
Click Deploy to deploy the package on the enterprise server. A PDF file with the deployment status will open. You can check the PDF output to see whether the package installed successfully.

Field Name	Value
Package Name	DV7333FC
Description	DV7333 full package
Path Code	DV7333

Creating BTSLIBInterop.jar

Once the BTSREL is installed, you need to generate the BTSLIBInterop.jar file on the deployment server, and copy this .jar file along with Kernel.jar and Connector.jar to the BizTalk server.

To generate BTSLIBInterop.jar

From a Command Prompt, change the directory to C root.
Include the path to javac by executing the following command with the appropriate path on the command prompt:
```
path=%path%;[Path to the JDK installation folder]\bin
```
Set the CLASSPATH environment variable to point to the Kernel.jar and Connector.jar files by executing the following command with the appropriate path on the command prompt:
```
Set CLASSPATH=[path to Kernel.jar]\Kernel.jar;[path to Connector.jar]\Connector.jar
```
Important
Do NOT include any spaces - especially around the equal sign and after the semicolon.

Important
Do NOT include any spaces - especially around the equal sign and after the semicolon.

Create a text file named MSBTSLIB.cmd on the C root folder with the following text:

define library JDEJAVA_BTSLIB
login
library %library%
  interface B5500901
    import B5500901
build
logout

Generate the BTSLIBInterop.jar by executing the following command:

C:\>genjava  /Cmd MSBTSLIB.cmd /Out C:\MSGENJAVA /TempOut C:\MSGENJAVA /ErrFile c:\MSGENJAVA\comerror.log

Enter UserID, password, and environment when prompt. The output should resemble the following:

MSGENJAVA\comerror.log
J.D.Edwards OneWorld XE(tm) Interoperability Interface Generator
Copyright (C) 1996-2000 J.D. Edwards World Source Company
All Rights Reserved.
BTSGetFunctionDefinition [D5500901A]
BTSGetFunctionList
BTSGetLibraryList
BTSGetObjectList
javac C:\MSGENJAVA\com\jdedwards\application\interop\btslib\*.java
javadoc -d C:\MSGENJAVA\com\jdedwards\application\interop\btslib\doc -sourcepath 
C:\MSGENJAVA com.jdedwa
rds.application.interop.btslib > 
C:\MSGENJAVA\com\jdedwards\application\interop\btslib\javadocoutput
see C:\MSGENJAVA\com\jdedwards\application\interop\btslib\javadocoutput for any 
javadoc warning/error messages.
jar -cf C:\MSGENJAVA\JDEJAVA_BTSLIBInteropDoc.jar *
jar -cf C:\MSGENJAVA\JDEJAVA_BTSLIBInterop.jar BTSLIB.xml 
com\jdedwards\application\interop\btslib\*.class.

You need to move the generated .jar file to the BizTalk server. The detailed steps are described in the next section.

Copying the BTSLIBInterop.jar File and the J.D. Edwards .JAR Files

You must copy BTSLIBInterop.jar, Connector.jar and Kernel.jar to the BizTalk server. BTSLIBInterop.jar is created in the last step of the previous procedure with the following name: JDEJAVA_BTSLIBInterop.jar. It is located in the C:\MSGENJAVA\ folder on the deployment server. The other two J.D. Edwards .jar files are located in the <J.D. Edwards OneWorld XE installation folder>\System\classes\ folder of the deployment server.

You can copy these files to any location on the BizTalk server. You need to point to these files while creating send ports.

Installing the JDK 1.4.2 or Later on the BizTalk Server

Download the JDK 1.4.2 or later from the Sun Microsystems Web site, and follow the instructions to install it on the BizTalk server.

Requirements for BizTalk ODBC Adapter for Oracle Database

With BizTalk ODBC Adapter for Oracle Database, you can access stored procedures, tables, and views for Oracle databases that run on Oracle 8i or 9i or 10g databases. The interfaces are made available as schemas that you can use when Oracle database items are imported into BizTalk Server projects. For more detailed information about the adapter, see the specific Help documentation for the adapter that is installed with BizTalk Adapters for Enterprise Applications. For information about Oracle database, see the documentation for the application.

Supported Operating Systems

BizTalk ODBC Adapter for Oracle Database runs on the following operating systems:

Microsoft Windows Server 2003 R2
Microsoft Windows Server 2003 with Service Pack 1
Microsoft Windows 2000 with Service Pack 4
Microsoft Windows XP with Service Pack 2

Supported Oracle Database Versions

BizTalk ODBC Adapter for Oracle Database supports the following Oracle Database versions:

Oracle Database 8i, 9i, 10g

Required Servers

BizTalk ODBC Adapter for Oracle Database supports the following servers to install and configure the adapter:

BizTalk server

Required Components

BizTalk Server 2006 or BizTalk Server 2006 R2
Oracle Client 9, 10
Oracle Driver 9.02.00.65

Prerequisites for Installing BizTalk ODBC Adapter for Oracle Database

Before installing the adapter on the BizTalk server, you must perform the following steps:

Installing the Oracle Client
Configuring a database connection
Upgrading the Oracle driver

Installing the Oracle Client

You must have an Oracle Client installed on the BizTalk server to use BizTalk ODBC Adapter for Oracle Database. The adapter uses databases registered through the ODBC Data Source Administrator. The Oracle Client installation includes the Oracle ODBC driver, which must be updated to Oracle ODBC driver 9.02.00.65 after you install the client.

Note
Oracle Client 9.2 only - The ODBC driver that is installed with the Oracle Client 9.2 contains a bug that prevents the enumeration of items that contain Japanese characters.

For the instructions on installing Oracle Client, see http://go.microsoft.com/fwlink/?LinkId=96008.

Configuring a Database Connection

You must set several ODBC variables before you can configure BizTalk ODBC Adapter for Oracle Database. For the instructions of configuring the database connection, see http://go.microsoft.com/fwlink/?LinkId=96012.

Upgrading Oracle Driver

The Oracle Client installation includes the Oracle ODBC driver, which must be updated to Oracle ODBC driver 9.02.00.65 after you install the client. For instructions on how to upgrade the Oracle driver, see http://go.microsoft.com/fwlink/?LinkId=96009.

Requirements for BizTalk ODBC Adapter for Oracle E-Business Suite

BizTalk ODBC Adapter for Oracle E-Business Suite is a development and run-time environment for line-of-business process management and automation that enables you to reuse your existing Oracle E-Business Suite procedures and applications with other applications. For more detailed information about the adapter, see the specific Help documentation for the adapter that is installed with BizTalk Adapters for Enterprise Applications. For information about Oracle E-Business Suite, see the documentation for the application.

Supported Operating Systems

BizTalk ODBC Adapter for Oracle E-Business Suite runs on the following operating systems:

Microsoft Windows Server 2003 R2
Microsoft Windows Server 2003 with Service Pack 1
Microsoft Windows 2000 with Service Pack 4
Microsoft Windows XP with Service Pack 2

Supported Oracle E-Business Suite Versions

BizTalk ODBC Adapter for Oracle E-Business Suite supports the following Oracle E-Business Suite versions:

Oracle E-Business Suite Application 11.5.10.2

Required Servers

BizTalk ODBC Adapter for Oracle E-Business Suite requires the following servers to install and configure the adapter

BizTalk server

Required Components

BizTalk Server 2006 or BizTalk Server 2006 R2
Oracle Client version 9 or 10
Oracle ODBC Driver version 9.02.00.65

Prerequisites for Installing BizTalk ODBC Adapter for Oracle E-Business Suite

Before installing the adapter on the BizTalk server, you must perform the following steps on the BizTalk server:

Installing the Oracle Client
Configuring a database connection
Upgrading the Oracle driver

Installing the Oracle Client

You must have an Oracle Client installed on the BizTalk server to use BizTalk ODBC Adapter for Oracle E-Business Suite. The adapter uses databases registered through the ODBC Data Source Administrator. The Oracle Client installation includes the Oracle ODBC driver, which must be updated to Oracle ODBC driver 9.02.00.65 after you install the client.

Note
Oracle Client 9.2 only - The ODBC driver that is installed with the Oracle 9.2 client contains a bug that prevents the enumeration of items that contain Japanese characters.

For the instructions on installing Oracle Client, see http://go.microsoft.com/fwlink/?LinkId=96026.

Configuring a Database Connection

You must set several ODBC variables before you can configure BizTalk ODBC Adapter for Oracle E-Business Suite. For the instructions on configuring the database connection, see http://go.microsoft.com/fwlink/?LinkId=96029.

Upgrading Oracle Driver

The Oracle Client installation includes the Oracle ODBC driver, which must be updated to Oracle ODBC driver 9.02.00.65 after you install the client. For the instructions on upgrading Oracle driver, see http://go.microsoft.com/fwlink/?LinkId=96031.

Requirements for BizTalk Adapter for PeopleSoft Enterprise

BizTalk Adapter for PeopleSoft Enterprise enables you to communicate with PeopleSoft via the PeopleSoft JOLT protocol (over TCP/IP). This adapter is a send adapter. If you need to have PeopleSoft Enterprise to initiate the call to BizTalk Server, we recommend using the HTTP adapter. You must install a custom component interface (CI) on the PeopleSoft system in order for the BizTalk Adapter for PeopleSoft Enterprise to browse the component interfaces available and get the metadata to call into the existing component interfaces.

This section describes how to prepare the server before installing the adapter. For more detailed information about the adapter, see the specific Help documentation for the adapter that is installed with BizTalk Adapters for Enterprise Applications. For information about PeopleSoft Enterprise, see the documentation for the application.

Supported Operating Systems

BizTalk Adapter for PeopleSoft Enterprise runs on the following operating systems:
Microsoft Windows Server 2003 R2
Microsoft Windows Server 2003 with Service Pack 1
Microsoft Windows 2000 with Service Pack 4
Microsoft Windows XP with Service Pack 2

Supported PeopleSoft PeopleTools Versions

BizTalk Adapter for PeopleSoft Enterprise supports the following PeopleSoft PeopleTools versions:

PeopleTools 8.17.02, 8.43, 8.45, 8.46, 8.48

Required Server

BizTalk Adapter for PeopleSoft Enterprise requires the following servers to install and configure the adapter:

BizTalk Server

Required Components

BizTalk Adapter for PeopleSoft Enterprise requires the following components on the server where the adapter is installed:

BizTalk Server 2006 or BizTalk Server 2006 R2
Sun Microsystems Java Development Kit (JDK) 1.4.2 or later

Prerequisites for Installing BizTalk Adapter for PeopleSoft Enterprise

Before installing BizTalk Adapter for PeopleSoft Enterprise, you must perform following steps:

For the instructions about how to use PeopleTools 8.17.02, see "Uploading a Custom Component Interface into PeopleSoft," later in this document.
For the instructions about how to use PeopleTools versions other than 8.17.02, see "Creating a New Component Interface," later in this document

Send Handler PeopleSoft Requirements

BizTalk Adapter for PeopleSoft Enterprise provides a GET_CI_INFO.pc. It is a custom component interface (CI) that you must upload to PeopleSoft system. It can provide metadata information that is required by BizTalk Adapter for PeopleSoft Enterprise. You must have access to the PeopleSoft Application Designer to deploy GET_CI_INFO.pc; however, the PeopleSoft Application Designer does not have to be on the BizTalk server.

Receive Handler PeopleSoft Requirements

The BizTalk Adapter for PeopleSoft Enterprise is a send adapter only. To be able to receive calls from PeopleSoft Enterprise, you must use the BizTalk Server default HTTP adapter.

Uploading a Custom Component Interface into PeopleSoft

BizTalk Adapter for PeopleSoft Enterprise requires a modification to the PeopleSoft application. To use component interfaces, you must upload GET_CI_INFO into PeopleSoft. GET_CI_INFO.pc is located in C:\Program Files\Microsoft BizTalk Adapters for Enterprise Applications\PeopleSoft Enterprise(r)\Config\. The adapter uses GET_CI_INFO to obtain information about other existing component interfaces in PeopleSoft.

To import the custom component interface, you can use one of the following methods:

Creating a new component to import the custom methods.
Using an existing component that contains no keys, for example, INSTALLATION_RS.

Creating a New Component Interface

The following steps are performed on PeopleSoft Application Designer 8.1 and 8.4.

To create a component interface on Application Designer 8.1

Click Start, point to All Programs, point to PeopleSoft, and then select Application Designer.
Enter a three-tier connection type, and then click OK.

For example, select Application Server from the list.
On the File menu, click New.

In the New dialog box, select Component Interface, and then click OK.

In the Select Source Component for Component Interface window, select the component to use as a basis for the component interface, and then click Select.

Note
The custom methods do not use or modify any properties of the component interface that they are installed in.

Note
This simple component interface must not contain keys. If you are not sure whether a particular component interface contains keys, you can run the following simple SQL statement using your SQL Query tool. It will give you a list of all the component interfaces in your application that have no keys. To verify that your GET_CI_INFO has no keys, run the PeopleTools Application Designer Component Interface Test tool.

Note

This simple component interface must not contain keys. If you are not sure whether a particular component interface contains keys, you can run the following simple SQL statement using your SQL Query tool. It will give you a list of all the component interfaces in your application that have no keys. To verify that your GET_CI_INFO has no keys, run the PeopleTools Application Designer Component Interface Test tool.

select distinct BCNAME
  from PSBCITEM bc1
  where not exists
    (select 1
      from PSBCITEM bc2
      where bc1.BCNAME = bc2.BCNAME
      and bc2.BCTYPE in (1, 2))

Note
You can also follow PeopleSoft documentation to create a unique simple component for storing custom methods for BizTalk Adapter for PeopleSoft Enterprise.

On the File menu, click Save As.
In File Name, enter GET_CI_INFO, and then click OK.
Right-click any method of your new component interfaces, and then click View PeopleCode.
Copy and paste the contents of <PeopleSoft installation directory>\PeopleSoft Enterprise\config\get_ci_info.pc into the window.
On the File menu, click Save. You now have a new component interface.

To create a component interface on Application Designer 8.4

Click Start, point to All Programs, point to PeopleSoft, and then select Application Designer.
Enter a three-tier connection type, and then click OK.

For example, select Application Server from the list.
On the File menu, click New.
In the New dialog box, select Component Interface.
Select the component on which this Component Interface will be based on.

After you select the appropriate component, you see a message asking if you want the fields exposed in the selected component to become the default properties of the Component Interface.

Note
Not all fields on the component interface can have automatic defaults created for them.

Note
Not all fields on the component interface can have automatic defaults created for them.

Click Yes to confirm the Default Property Definitions or No if you don’t want any properties initially created.

If you select to have the Property Definitions automatically defaulted by the system, then all properties that appear on the pages of the underlying component are added to the component interface. Even though the system adds the default properties, you may need to move other properties into the component view for the component to work.

An untitled Component Interface appears, showing the Get keys and Find keys. Create keys are produced only if the underlying component is able to run in Add mode (the example preceding this procedure does not have Create keys, because the search record of the underlying component cannot run in Add mode). PeopleSoft Application Designer generates the keys for you as you drag definitions.

The standard methods Cancel, Find, Get, and Save are automatically created. The Create method is not automatically created unless the component supports the Add mode.

Note
You can begin adding properties to a new component interface at any point. However, you cannot add any user-defined methods to the component interface until you have saved the component interface.

On the File menu, click Save As.
In File Name, enter GET_CI_INFO, and then click OK.
Right-click any method of your new Component Interfaces, and then click View PeopleCode.
Copy and paste the contents of <PeopleSoft installation directory>\PeopleSoft Enterprise\config\get_ci_info.pc into the window.
On the File menu, click Save. You now have a new Component Interface.

Note
Once you have saved the component interface, you can further define user-defined methods.

Checking the Component Interface

You have completed uploading the BizTalk Adapter for PeopleSoft GET_CI_INFO into your PeopleSoft System. The GET_CI_INFO is a user-defined custom component interface. It contains user-defined methods. The GET_CI_INFO component interface lets you browse component interfaces in your PeopleSoft system by using the BizTalk Add Adapter Wizard. You can locate and expand GET_CI_INFO to view its user-defined methods. For more information about user-defined methods, see http://go.microsoft.com/fwlink/?LinkId=96136.

Setting the Component Interface Security

After you install the custom GET_CI_INFO PeopleSoft component interface on PeopleSoft, set the security settings for GetCINamespace, GetDetails, and GetCollections methods for BizTalk Adapter for PeopleSoft Enterprise. This is standard practice when you create custom components or user-defined methods.

Note
The following procedure describes how to configure security for all supported releases of PeopleSoft in all supported modes.

To configure security for the component interface on Application Designer 8.1

Log on to the PeopleTools browser-based GUI.
From the menu, expand PeopleTools, and then click Security.
From the Permissions & Roles category, click Permission Lists.
Click Search.
In the Permission Lists Search pane, double-click the hyperlink of the relevant Permission List.
Click the right arrow next to the Sign-on Times tab to display the Component Interfaces tab.
Click the Component Interfaces tab.
Click the Find hyperlink.
In the Explorer User Prompt dialog box, enter GET_CI_INFO in the text box, and then click OK.
From the Component Interfaces panel, click the Edit hyperlink for the GET_CI_INFO component interface.
To give the full access to all the methods, click Full Access (All), and then click OK.
Click Save.

To configure security for the component interface on Application Designer 8.4

Log on to the PeopleTools browser-based GUI.
From the menu, expand People Tools, expand Security, expand Permissions & Roles, and click Permission Lists.
Select the Permission List for which you want to set security.

The Permission List component appears.
Access the Component Interfaces page.
Select GET_CI_INTO, the Component Interface for which you want to set security, and then click Edit.

The Component Interface Permissions page appears, showing all of the methods (both standard and user-defined) in the Component Interface and their method access.
Set the access permission for each method.

Select Full Access or No Access. You must grant full access to at least one method to make the Component Interface available for testing and other online use.
Click OK.
Click Save.

Testing the Component Interface

You have finished configuring security for the GET_CI_INFO component interface delivered with BizTalk Adapter for PeopleSoft Enterprise. Your PeopleSoft component interface is ready, and you can browse PeopleSoft component interfaces.

Follow these steps to test the component interface in the Application Designer.

To test the component interface

Start Application Designer.
On the File menu, point to Open, and then select Definition = Component Interface.
From the list of component interfaces, select GET_CI_INFO.
After you open GET_CI_INFO, right-click anywhere in the right pane of your component interface definition, and then select Test Component Interface.

The Component Interface Tester window appears.

There should be no keys listed. If your GET_CI_INFO contains keys or if there is another option for selection, return to the Application Designer and eliminate all keys from GET_CI_INFO.

Requirements for BizTalk Adapter for Siebel eBusiness Applications

BizTalk Adapter for Siebel eBusiness Applications is a development and run-time environment for line-of-business process management and automation. For more detailed information about the adapter, see the specific Help documentation for the adapter that is installed with BizTalk Adapters for Enterprise Applications. For information about Siebel eBusiness Applications, see the documentation for the application.

Supported Operating Systems

BizTalk Adapter for Siebel eBusiness Applications runs on the following operating systems:

Microsoft Windows Server 2003 R2
Microsoft Windows Server 2003 with Service Pack 1
Microsoft Windows 2000 with Service Pack 4
Microsoft Windows XP with Service Pack 2

Supported Siebel Platforms

BizTalk Adapter for Siebel eBusiness Applications supports the following Siebel eBusiness Application versions:

Version 6.2.1 with patch 110 or later
Version 7.0.*
Version 7.5.*
Version 7.7
Version 7.8

Required Servers

BizTalk Adapter for Siebel eBusiness Applications requires the following servers to install and configure the adapter:

BizTalk server

Required Components

BizTalk Adapter for Siebel eBusiness Applications requires the following components on the server where the adapter is installed.

BizTalk Server 2006 or BizTalk Server 2006 R2
Siebel software:

Version

Components

Siebel, version 6.2.1 with patch 110 or later

Siebel Thin Client Enterprise Component

Siebel Java Data Bean using the JDK 1.1.8 or the JDK 1.3

Note

Patch 110 for version 6.2.1 resolves a memory leak on the Siebel server when you use any kind of remote client. You must follow all instructions in the patch 110 Maintenance Release Guide from Siebel Systems. Note that you can avoid the server side memory leak by specifying the Siebel server component parameter recyclefactor to a value greater than the default, zero. The guide recommends a value of 3. This improves server performance and memory usage. You must do this for all object managers that are being used.

Siebel, version 7.0.3

Siebel Java Data Bean (using the JDK 1.1.8, JDK 1.3, or JDK 1.4)

Siebel, version 7.5.2 and 7.7

Siebel Java Data Bean (JDK 1.4)

Required Files

BizTalk Adapter for Siebel eBusiness Applications uses Siebel Object Interface API as implemented in the Siebel Java Data Bean. The following Siebel .jar files must be available to support the adapter:

Version	Files
Siebel 6.2.1	SiebelTcOM.jar SiebelTcCommon.jar SiebelTC_%lang%.jar, where %lang% is the installed language pack; for example, SiebelJI_enu.jar is for English and SiebelJI_jpn.jar is for Japanese. You can install the .jar files through the Siebel Enterprise Server installation, or by installing Siebel Tools. For more information, see the Siebel documentation. SiebelDataBean.jar
Siebel 7.0.3 and 7.5.2	SiebelJI_%lang%.jar, where %lang% is the installed language pack; for example, SiebelJI_enu.jar is for English and SiebelJI_jpn.jar is for Japanese. You can install the .jar files through the Siebel Enterprise Server installation, or by installing Siebel Tools. For more information, see the Siebel documentation. SiebelJI_Common.jar SiebelJI.jar SBLJAccess.jar
Siebel 7.7 and Siebel 7.8	Siebel_%lang%.jar, where %lang% is the installed language pack; for example, SiebelJI_enu.jar is for English or SiebelJI_jpn.jar is for Japanese. You can install the .jar files through the Siebel Enterprise Server install, or by installing Siebel Tools. For more information, see the Siebel documentation. Siebel.jar SBLJAccess.jar

Note
Excerpt from Siebel Knowledge Base 38-683408651: If you receive an 8859_1 not supported error, you must set your Java Virtual Machine (JVM) environment. The JVM encoding must match the Siebel FileEncoding setting. You must add this setting in the Windows registry or systemsettings.txt file: Adapters/Siebel/Compatibility.FileEncoding: string = ISO8859_1

Requirements for BizTalk Adapter for TIBCO Enterprise Message Service

BizTalk Adapter for TIBCO Enterprise Message Service enables you to publish and subscribe to queues and topics managed by TIBCO EMS by using BizTalk Server 2006 or BizTalk Server 2006 R2. For more detailed information about the adapter, see the specific Help documentation for the adapter that is installed with BizTalk Adapters for Enterprise Applications. For information about TIBCO EMS, see the documentation for the application.

Supported Operating Systems

BizTalk Adapter for TIBCO Enterprise Message Service runs on the following operating systems:

Microsoft Windows Server 2003 R2
Microsoft Windows Server 2003 with Service Pack 1
Microsoft Windows 2000 with Service Pack 4
Microsoft Windows XP with Service Pack 2

Supported TIBCO Enterprise Message Service Versions

BizTalk Adapter for TIBCO Enterprise Message Service supports the following TIBCO Enterprise Message Service versions:

TIBCO Enterprise Message Service (EMS) version 4.2

Required Servers

BizTalk Adapter for TIBCO Enterprise Message Service requires the following servers to install and configure the adapter:

BizTalk server

Required Components

BizTalk Adapter for TIBCO Enterprise Message Service requires the following components on the server where the adapter is installed:

BizTalk Server 2006 or BizTalk Server 2006 R2
TIBCO Enterprise Message Service version 4.2 client SDK (using the TIBCO EMS C# API)

Requirements for BizTalk Adapter for TIBCO Rendezvous

BizTalk Adapter for TIBCO Rendezvous enables you to use TIBCO Rendezvous business functions within BizTalk Server. For more detailed information about the adapter, see the specific Help documentation for the adapter that is installed with BizTalk Adapters for Enterprise Applications. For information about TIBCO Rendezvous, see the documentation for the application.

Supported Operating Systems

BizTalk Adapter for TIBCO Rendezvous runs on the following operating systems:

Microsoft Windows Server 2003 R2
Microsoft Windows Server 2003 with Service Pack 1
Microsoft Windows 2000 with Service Pack 4
Microsoft Windows XP with Service Pack 2

Supported TIBCO Rendezvous Versions

BizTalk Adapter for TIBCO Rendezvous supports the following TIBCO Rendezvous versions:

TIBCO Rendezvous version 7.3

Required Servers

BizTalk Adapter for TIBCO Rendezvous requires the following servers to install and configure the adapter:

BizTalk server

Required Components

BizTalk Adapter for TIBCO Rendezvous requires the following components on the server where the adapter is installed:

BizTalk Server 2006 or BizTalk Server 2006 R2
TIBCO Rendezvous run-time component

Other Requirements

The TIBCO Rendezvous run-time component must be installed on the computer where BizTalk Adapter for TIBCO Rendezvous is running.
The TIBCO Rendezvous license must be configured on the computer where BizTalk Adapter for TIBCO Rendezvous is running.
The TIBCO Rendezvous binaries directory must be visible to the adapter: either in the Environment variables PATH value, or specified on each Rendezvous port in BizTalk Server. This is necessary for the Rendezvous assembly to find its libraries and executables.
The TIBCO.Rendezvous.dll assembly must be registered in the global assembly cache (GAC) so that the adapter can find the DLL.

Requirements for BizTalk Adapter v2.0 for mySAP™ Business Suite Service Pack 1

The Adapter requires that you install the following software on one computer, in the order listed:

Microsoft Windows Server 2003 R2, Microsoft Windows Server 2003 SP1 or Microsoft Windows 2000 Server SP4. You can also use Windows XP SP2 for your development environment only.
Microsoft Visual Studio 2005. This software is not required on your run-time computers.
BizTalk Server 2006 and all prerequisites. For more information about installing BizTalk Server 2006 and its prerequisites, see the BizTalk Server installation guide at http://go.microsoft.com/fwlink/?LinkId=46922.
SAP .NET Connector for Visual Studio, available from the SAP Service Marketplace Web site.
You must install the SAP .NET Connector 1.x RUNTIME before installing the Adapter. You can download the SAP .NET Connector from the SAP Marketplace Web site. To download the SAP .NET Connector, you must be an SAP customer with a valid user name and password.

Installing BizTalk Adapters for Enterprise Applications

Before running the Microsoft BizTalk Adapters for Enterprise Applications installation program, make sure that you install BizTalk Server 2006 or BizTalk Server 2006 R2, Microsoft .NET Framework 1.1 with Service Pack 1, and all the software prerequisites for the adapters that you want to install. We recommend that you close all applications before running Setup.

Note
The BizTalk Adapters for Enterprise Applications setup automatically detects previous versions of adapters and will upgrade the adapters, unless you specify otherwise.

To install Microsoft BizTalk Adapters for Enterprise Applications

Double-click setup.exe to run the installation program. The installation program extracts its files and the Introduction page appears.

Note
You can also run a silent installation using the following command: msiexec /i <msi> /qn /l* <logfile> -- where <logfile> is optional, but is useful in the event of a failed installation.

Note
The installation updates the PATH environment variable. To make sure that you are using the correct variables, close the installation command window to update your variables.

Note
You can also run a silent installation using the following command: *msiexec /i <msi> /qn /l <logfile> -- where <logfile>** is optional, but is useful in the event of a failed installation.

Note
The installation updates the PATH environment variable. To make sure that you are using the correct variables, close the installation command window to update your variables.

On the Introduction screen, click Next to continue. If you have a previous version of one or more adapters installed, confirm that you want to upgrade the adapter(s), and then click Next.

Note
If you do not confirm that you want to upgrade your previously installed adapter(s), a message that you must manually uninstall previous versions of the adapter(s) appears and you exit the installation program.

On the End-User License Agreement screen, choose I accept the terms in the License Agreement, and then click Next.

Note
If you select I do not accept the terms in the License Agreement, the installation program removes the extracted files and closes.
On the Customer Information screen, enter the User Name and the Organization, and then click Next.
On the Choose Setup Type screen, click Complete or Custom.
- Complete: installs all the Microsoft BizTalk Adapters for Enterprise Applications together with all the program features and is used for development and runtime.
- Custom: lets you choose the adapters and features that you want to install and where they will be installed.
On the Choose Destination Location screen, enter Location, and then click Next.
On the Ready to Install screen, click Install. The installer loads files to your selected location.
On the Install Complete page, click Finish.

Note
If you select I do not accept the terms in the License Agreement, the installation program removes the extracted files and closes.

After BizTalk Adapters for Enterprise Applications is installed, you must register each of the adapters to the BizTalk Management database. For information about how to add the adapters to BizTalk Server, see Adding the BizTalk Adapters for Enterprise Applications to BizTalk Server.

Installation Information for BizTalk Adapter for J.D. Edwards EnterpriseOne

BizTalk Adapter for J.D. Edwards EnterpriseOne contains a send adapter that connects supported databases and server systems to BizTalk Server. The send adapter enables you to invoke a server system’s call from BizTalk Server. For more information about the adapter, see the adapter documentation.

Installed Components

The BizTalk Adapter for J.D. Edwards EnterpriseOne installer installs and registers the following components in the global assembly cache (GAC):

Microsoft.BizTalk.Adapters.BizUtil.dll
Microsoft.BizTalk.Adapters.JDEProperties.dll
Microsoft.BizTalk.Adapters.CoreManagement.dll
Microsoft.BizTalk.Adapters.CoreReceiver.dll
Microsoft.BizTalk.Adapters.CoreTransmitter.dll
Microsoft.BizTalk.Adapters.JDEProperties.dll

You can verify the registration in the GAC by viewing the assembly folder in your explorer; for example, <%WINDIR%>\assembly, or use the following command from the Visual Studio command prompt:

gacutil /l

The adapter-specific files are installed in the Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\Bin folder. This folder contains the following files:

Jdecba.dll
Microsoft.BizTalk.Adapters.JDEProperties.dll

The following files are installed in Program Files\Microsoft BizTalk Adapters for Enterprise Applications\JDEEnterpriseOne.

Bin\BTAJDEEnterpriseOneTrace.cmd
Classes\JDEDynAccess.jar
Config\btaJDEEnterpriseOneTrace.mof
Config\jdearglist.txt
Config\jdeinterop.ini
Config\jdelog.properties
Sdk
BizTalk Adapter for J.D. Edwards EnterpriseOne installation includes samples in the \Sdk directory.

Registering BizTalk Adapter for J.D. Edwards EnterpriseOne to the BizTalk Server

After the adapter is installed, you must register it to the BizTalk Management database before you can use it in send ports or receive ports. Registration needs to be performed only once on the BizTalk server or a server in the same BizTalk group with the BizTalk Server Administration console installed. For the detailed steps, see http://go.microsoft.com/fwlink/?LinkId=96111 or Adding the BizTalk Adapters for Enterprise Applications to BizTalk Server.

Enterprise Single Sign-On

BizTalk Adapter for J.D. Edwards EnterpriseOne provides Enterprise Single Sign-On (SSO) support. When you use SSO with the adapter, the adapter obtains the credentials from the SSO Credentials database; therefore, you do not have to enter the logon credentials for the server system in the Transport Properties dialog box. For more information, see http://go.microsoft.com/fwlink/?LinkId=96112.

Creating Send Ports to Communicate with J.D. Edwards EnterpriseOne Servers

The adapter accepts XML messages to enable BizTalk applications to communicate and exchange transactions with J.D. Edwards EnterpriseOne by using static solicit-response send ports or static one-way send ports.

Prior to configuring the send ports, a J.D. Edwards CNC specialist or administrator needs to give BizTalk Server developer or administrator the following information:

J.D. Edwards Server name or IP address
J.D. Edwards environment information
TCP port
User name
Password

A BizTalk Server developer or administrator can set the connection and credential parameters that are specific to the J.D. Edwards server and the J.D. Edwards objects in the Transport Properties dialog box:

To create a static solicit response send port using the adapter

Click Start, point to Programs, point to Microsoft Visual Studio 2005, and then click Microsoft Visual Studio 2005.
On the View menu, click BizTalk Explorer.
From BizTalk Explorer, navigate to BizTalk Configuration Database|<server>.BizTalkMgmtDb.dbo|Send Ports.
Right-click Send Ports, and select Add Send Port.
From the Create New Send Port dialog box, select Static Solicit-Response Port, and then click OK. The Send Port Properties window opens.
In the Name box, enter a send port name, for example, SendToJDE.
On the Transport Type list, select the BizTalk Adapter for J.D. Edwards EnterpriseOne adapter by the name you entered in the last procedure, for example, JDE EnterpriseOne.
On the Address(URI) property, click … to open the JDE EnterpriseOne Transport Properties dialog box.

Expand the Adapter Required Properties category, and then fill in all required information for connection to the J.D. Edwards EnterpriseOne server.

Mandatory settings are:

JAVA_HOME (if not set in the system environment); and
JDE environment.

Parameter

Description

Host

The name or the IP address of the J.D. Edwards server host.

JAVA_HOME

The complete path to the JDK installation folder.

JDEdwards Environment

The name of a J.D. Edwards EnterpriseOne environment, for example, DV810.

JDEdwards .jar files

The complete path and the file name for each of the .jar files:

From Tools Release 8.93 to 8.95: Connector.jar, Kernel.jar, database.jar, jdeutil.jar, log4j.jar, and xerces.jar
Tools Release 8.96: ApplicationAPIs_JAR.jar, ApplicationLogic_JAR.jar, Base_JAR.jar, BizLogicContainer_JAR.jar, BizLogicContainerClient_JAR.jar, Connector.jar, jdbj.ini, JdbjBase_JAR.jar, JdbjInterfaces_JAR.jar, jdeinterop.ini, jdelog.properties, JdeNet_JAR.jar, log4j.jar, PMApi_JAR.jar, Spec_JAR.jar, System_JAR.jar, xalan.jar, xerces.jar.
JDBC driver .jar files for the specific database, for example, msbase.jar, mssqlserver.jar, and msutil.jar for the Microsoft SQL Server 2000 JDBC driver.
JDEDynAccess.jar - installed with the product.

Each .jar file must be separated with a semi-colon (;) and no space. For example:

Tools Release Version	Files
JDE 8.94	C:\JDEJARS\895\database.jar C:\JDEJARS\895\msbase.jar C:\JDEJARS\895\mssqlserver.jar C:\JDEJARS\895\msutil.jar C:\JDEJARS\895\Connector.jar C:\JDEJARS\895\kernel.jar C:\JDEJARS\895\jdeutil.jar C:\JDEJARS\895\log4j.jar C:\JDEJARS\895\xerces.jar C:\Program Files\Microsoft BizTalk Adapters for Enterprise Applications\J.D. Edwards EnterpriseOne(r)\Classes\JDEDynAccess.jar
JDE 8.95	C:\JDEJARS\894\database.jar C:\JDEJARS\894\msbase.jar C:\JDEJARS\894\mssqlserver.jar C:\JDEJARS\894\msutil.jar C:\JDEJARS\894\Connector.jar C:\JDEJARS\894\kernel.jar C:\JDEJARS\894\jdeutil.jar C:\JDEJARS\894\log4j.jar C:\JDEJARS\894\xerces.jar C:\Program Files\Microsoft BizTalk Adapters for Enterprise Applications\J.D. Edwards EnterpriseOne(r)\Classes\JDEDynAccess.jar
JDE 8.96	C:\JDEJARS\896\ApplicationAPIs_JAR.jar C:\JDEJARS\896\ApplicationLogic_JAR.jar C:\JDEJARS\896\Base_JAR.jar C:\JDEJARS\896\BizLogicContainer_JAR.jar C:\JDEJARS\896\BizLogicContainerClient_JAR.jar C:\JDEJARS\896\Connector.jar C:\JDEJARS\896\jdbj.ini C:\JDEJARS\896\JdbjBase_JAR.jar C:\JDEJARS\896\JdbjInterfaces_JAR.jar C:\JDEJARS\896\jdeinterop.ini C:\JDEJARS\896\jdelog.properties C:\JDEJARS\896\JdeNet_JAR.jar C:\JDEJARS\896\log4j.jar C:\JDEJARS\896\msbase.jar C:\JDEJARS\896\mssqlserver.jar C:\JDEJARS\896\msutil.jar C:\JDEJARS\896\PMApi_JAR.jar C:\JDEJARS\896\Spec_JAR.jar C:\JDEJARS\896\System_JAR.jar C:\JDEJARS\896\xalan.jar C:\JDEJARS\896\xerces.jar C:\Program Files\Microsoft BizTalk Adapters for Enterprise Applications\J.D. Edwards EnterpriseOne(r)\Classes\JDEDynAccess.jar

Password

The password of the specified J.D. Edwards user in the User name field. If you choose not to use SSO, you must set this parameter along with the User name parameter for the adapter to access the server.

Port

The port number that is used to exchange data, for example, 6012.

User name

The user name of the specified J.D. Edwards user. If you choose not to use SSO, you must set this parameter along with the Password parameter for the adapter to access the server.

When a connection is made to J.D. Edwards EnterpriseOne, parameters are passed to the connection object (User, Password, and Environment) and the connection object returns an instance of the J.D. Edwards EnterpriseOne Application business function. The credentials are further defined by the name of the enterprise application server, and the defined TCP/IP port on which BizTalk Server listens.

Note
The default values for the enterprise server name and port are configured by BizTalk Server. They are also read from a file called jdeinterop.ini. If you receive logon errors, carefully check the credentials and values.

Important
All entries are case-sensitive.

Expand the Bootstrap Data Source Required Properties category, and fill in all required information for connection to the J.D. Edwards EnterpriseOne server.

Bootstrap section information is used for sign-on to provide access to System tables. Bootstrap Data source information defines the data source where the Object Configuration Mapping (OCM) resides.

For the Bootstrap Data Source parameters, not all settings are needed for all platforms. If you are using an uncommon database, you might have to update the [JDBj-JDBC DRIVERS] section of the jdeinterop.ini file to declare your JDBC driver. The following identifies the required settings by platform:

iSeries: Data Source Name, Database Type, Database Server Name, Physical Database Name
Oracle: Data Source Name, Database Type, Database, Database Owner
SQL Server: Data Source Name, Database Type, Database Server Name, Database Server Port, Physical Database Name, Database Owner
SQL Server OLEDB: Data Source Name, Database Type, Database Server Name, Database Server Port, Physical Database Name, Database Owner
UDB: Data Source Name, Database Type, Database, Database Owner

Parameter

Description

Data Source Name

The database source name is in the jde.ini file located on the enterprise server. The .ini file is usually in the \\Machine_name\PeopleSoft\ddp\e810\System\Bin32 folder:

[SECURITY]
SecurityServer=BVISION02
User=PSFT
Password=PSFT
DefaultEnvironment=DV810
DataSource=System - 810
Default Role=*ALL
History=0

Database Owner

The database owner is in the jde.ini file located on the enterprise server.

[DB SYSTEM SETTINGS]
Version=43
Default User=PSFT
Default Pwd=PSFT
Default Role=*ALL
Default Env=DV810
Default PathCode=DV810
Base Datasource=BVISION02 - 810 Server Map
Object Owner=SVM810 — (Data Base Owner) 
Server=BVISION02
Database=
Load Library=
Decimal Shift=Y
Julian Dates=Y
Use Owner=Y
Secured=Y
Type=L
Library=
Library List=
DatabaseName2=PS810
DatabaseInstance=
ServerPort=1433
JDBNETUse=N
UnicodeFlag=Y
LOBFlag=N

Database Server Name

The database server name.

Database Server Port

The database server port, for example, 1433.

Database Type

The database type determines which kind of database is used:

Database Name	Database Type
iSeries	I
Oracle	O
SQL Server	S
SQL Server OLEDB	L
UDB (for example, DB2)	W

Physical Database Name

The physical database name is in the jde.ini file located on the enterprise server:

[DB SYSTEM SETTINGS]
Version=43
Default User=PSFT
Default Pwd=PSFT
Default Role=*ALL
Default Env=DV810
Default PathCode=DV810
Base Datasource=BVISION02 - 810 Server Map
Object Owner=SVM810
Server=BVISION02
Database=
Load Library=
Decimal Shift=Y
Julian Dates=Y
Use Owner=Y
Secured=Y
Type=L
Library=
Library List=
DatabaseName2=PS810 — (Physical Database) 
DatabaseInstance=
ServerPort=1433
JDBNETUse=N
UnicodeFlag=Y
LOBFlag=N

Expand the Concurrency control category, and enter a Concurrency Control value representing the number of calls in Max Concurrent Calls if required, for example, 200. The default value for this field is -1, meaning no protection occurs.

The Max Concurrent Calls parameter activates an overload protection if the back-end server cannot process the amount of data. A concurrent call means a request for which the adapter does not yet have a reply. Set Max Concurrent Calls in instances where the throughput exceeds back-end processing capabilities.

If BizTalk Server submits a request to the send adapter and the number of concurrent calls equals or exceeds the value set for Max Concurrent Calls, the thread submitting the request is saved until the concurrent calls number decreases to below the set value.

Changing this parameter takes effect within a minute as BizTalk Server must retrieve the changes to the adapter configuration saved in the SQL database.
Expand the Event Log category, and enter event log information. For the Event Log Level property, you can select Information, Error, or Warning. Logging at the Error or Warning levels captures important run-time information.

The Log provides information on the type of message: Error, Warning, or Information as well as a time stamp indicating when the action occurred. It also provides a brief description of the message and the process information indicating where the message originated.

Expand the Refresh Agent category. Select Yes for the Refresh Agent to force the runtimeagent.exe and the browsingagent.exe processes to restart themselves automatically when required. For example, you want the process to restart automatically if it loses connection with the server, or if you added something to the server and it does not appear in the BizTalk Add Adapter Wizard for selection.

Note
The browsingagent.exe does not refresh until you terminate the current browsing session. For example, you must exit the “add generated item” browsing session and re-enter to refresh the browsingagent.exe.

Expand the Security Server category, and then enter the values for the Security Server parameter:

Parameter	Description
Security Server - Security Server Name	The name of J.D. Edwards EnterpriseOne host. You can use either the host name or the IP address.
Security Server - Service Name Connect	The port number on which the J.D. Edwards EnterpriseOne is listening, for example, 6012.

Expand the Use Single Sign-On category, enter Affiliate Application, and then set Use SSO to yes or no.
In the <Adapter name> Transport Properties dialog box, click OK to save the changes.
From the Static Solicit-Response Send Port Properties - Configurations - Transport - Primary dialog box, click Send from the left panel to configure the send pipeline.
In the Send Pipeline list, select the Microsoft.BizTalk.DefaultPipelines.XMLTransmit default pipeline. The BizTalk Adapter for J.D. Edwards EnterpriseOne requires that you select the default XMLTransmit pipeline for the send pipelines.
In the Receive Pipeline list, select the Microsoft.BizTalk.DefaultPipelines.XMLReceive default pipeline. The BizTalk Adapter for J.D. Edwards EnterpriseOne requires that you select the default XMLReceive pipeline for the receive pipelines.
Click OK to save the configuration.

The following is a sample J.D. Edwards EnterpriseOne Port configuration:

Description	Sample Configuration
Host	bpi118719
JAVA_HOME	C:\Program Files\Java\jdk1.6.0
Environment	DV812
.jar files	C:\JDEJARS\896\ApplicationAPIs_JAR.jar C:\JDEJARS\896\ApplicationLogic_JAR.jar C:\JDEJARS\896\Base_JAR.jar C:\JDEJARS\896\BizLogicContainer_JAR.jar C:\JDEJARS\896\BizLogicContainerClient_JAR.jar C:\JDEJARS\896\Connector.jar C:\JDEJARS\896\jdbj.ini C:\JDEJARS\896\JdbjBase_JAR.jar C:\JDEJARS\896\JdbjInterfaces_JAR.jar C:\JDEJARS\896\jdeinterop.ini C:\JDEJARS\896\jdelog.properties C:\JDEJARS\896\JdeNet_JAR.jar C:\JDEJARS\896\log4j.jar C:\JDEJARS\896\msbase.jar C:\JDEJARS\896\mssqlserver.jar C:\JDEJARS\896\msutil.jar C:\JDEJARS\896\PMApi_JAR.jar C:\JDEJARS\896\Spec_JAR.jar C:\JDEJARS\896\System_JAR.jar C:\JDEJARS\896\xalan.jar C:\JDEJARS\896\xerces.jar C:\Program Files\Microsoft BizTalk Adapters for Enterprise Applications\J.D. Edwards EnterpriseOne(r)\Classes\JDEDynAccess.jar
Password	JDE
Port	6014
User Name	JDE
Data Source Name	System - 812
Database Owner	SY812
Database Server Name	bpi118719
Database Server Port	1433
Database Type	S
Physical Database Name	JDE812
Security Server Name	bpi118719
Service Name Connect	6014

Installation Information for BizTalk Adapter for J.D. Edwards OneWorld XE

BizTalk Adapter for J.D. Edwards OneWorld XE consists of a send adapter that connects supported databases and server systems to BizTalk Server. The send adapter enables you to invoke a server system's call from BizTalk Server. For more information about the adapter, see the adapter documentation.

Installed Components

The BizTalk Adapter for J.D. Edwards OneWorld XE installer installs and registers the following components in the global assembly cache (GAC):

Microsoft.BizTalk.Adapters.BizUtil.dll
Microsoft.BizTalk.Adapters.JDEProperties.dll
Microsoft.BizTalk.Adapters.CoreManagement.dll
Microsoft.BizTalk.Adapters.CoreReceiver.dll
Microsoft.BizTalk.Adapters.CoreTransmitter.dll

You can verify the registration in the GAC by viewing the assembly folder in your explorer; for example, <%WINDIR%>\assembly, or by using the following command from the Visual Studio command prompt:

gacutil /l

The adapter-specific files are installed in the Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\Bin folder. The folder contains the following files:

Microsoft.BizTalk.Adapters.JDEProperties.dll
jdecba.dll

The following files are installed in Program Files\Microsoft BizTalk Adapters for Enterprise Applications\JDEOneWorld:

Bin\BTAJDEOneWorldTrace.cmd
Classes\JDEJAccess.jar
Config\btaJDEOneWorldTrace.mof
Config\jdearglist.txt
Config\jdeinterop.ini
Sdk\

BizTalk Adapter for J.D. Edwards OneWorld XE installation includes samples in the \Sdk directory.

Registering BizTalk Adapter for J.D. Edwards OneWorld XE to the BizTalk Server

After the adapter is installed, you must register the adapter to the BizTalk Management database before you can use it in send ports or receive ports. This step only needs to be performed once on the BizTalk server or a server in the same BizTalk group with the BizTalk Server Administration console installed. For the detailed steps, see http://go.microsoft.com/fwlink/?LinkId=96113, or Adding the BizTalk Adapters for Enterprise Applications to BizTalk Server.

Enterprise Single Sign-On

BizTalk Adapter for J.D. Edwards OneWorld provides Enterprise Single Sign-On (SSO) support. When you use SSO with the adapter, the adapter obtains the credentials from the SSO Credentials database; therefore, you do not have to enter the logon credentials for the server system in the Transport Properties dialog box. For more information, see http://go.microsoft.com/fwlink/?LinkId=96114.

Creating Send Ports to Communicate with J.D. Edwards OneWorld XE Servers

The adapter accepts XML messages to enable BizTalk applications to communicate and exchange transactions with J.D. Edwards OneWorld XE by using static solicit-response send ports or static one-way send ports.

Prior to configuring the send ports, a J.D. Edwards CNC specialist or administrator needs to give the BizTalk Server developer or administrator the following information:

J.D. Edwards Server name or IP address
J.D. Edwards environment information
TCP port
User name
Password

The BizTalk developer or administrator can set the connection and credential parameters that are specific to the J.D. Edwards server and the J.D. Edwards objects in the Transport Properties dialog box:

To create a static solicit response send port by using the adapter

Click Start, point to Programs, point to Microsoft Visual Studio 2005, and then click Microsoft Visual Studio 2005.
On the View menu, click BizTalk Explorer.
From BizTalk Explorer, navigate to BizTalk Configuration Database|<server>.BizTalkMgmtDb.dbo|Send Ports.
Right-click Send Ports, and then select Add Send Port.
From the Create New Send Port dialog box, select Static Solicit-Response Port, and then click OK. The Send Port Properties window opens.
In the Name list, type a send port name, for example, SendToJDE.
In the Transport Type list, select the BizTalk Adapter for J.D. Edwards OneWorld XE adapter by the name you entered in the last procedure, for example, JDE OneWorld.
On the Address(URI) property, click … to open the JDE OneWorld Transport Properties dialog box.

Expand the Adapter Required Properties category, and then fill in all required information for connection to the J.D. Edwards OneWorld XE server.

Mandatory settings are:

JAVA_HOME (if not set in the system environment)
JDE environment.

Parameter	Description
Host	The name or the IP address of the J.D. Edwards server host.
JAVA_HOME	The complete path to the JDK installation folder.
JDEdwards Environment	The name of the J.D. Edwards OneWorld XE environment, for example, DV7333, PY7333, PD7333
JDEdwards .jar files	The complete path and the file name for each of the .jar files: Connector.jar, Kernel.jar, JDEJAccess.jar, BTSLIBInterop. Each .jar file must be separated with a semi-colon (;) and no space. For example: `C:\JDEJarFiles\Connector.jar;C:\JDEJarFiles\Kernel.jar; C:\Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\J.D. Edwards OneWorld\classes\JDEJAccess.jar;C:\JDEJarFiles BTSLIBInterop.jar.` BizTalk Adapter for J.D. Edwards OneWorld XE provides the JDEJAccess .jar file for use with J.D. Edwards OneWorld XE.
Password	The password of the specified J.D. Edwards OneWorld XE user specified in the User name field. If you choose not to use SSO, you must set this parameter along with the User name parameter for the adapter to access the server.
Port	The port number of J.D. Edwards OneWorld XE that will exchange data, for example, 6009.
User name	The user name of the specified J.D. Edwards OneWorld XE user. If you choose not to use SSO, you must set this parameter along with the Password parameter for the adapter to access the server.

When a connection is made to J.D. Edwards OneWorld XE, parameters are passed to the connection object (User, Password, and Environment) and the connection object returns an instance of the J.D. Edwards OneWorld XE Application business function. The credentials are further defined by the name of the enterprise application server, and the defined TCP/IP port on which BizTalk Server listens.

Note
The default values for the enterprise server name and port are configured by BizTalk Server. They are also read from a file called jdeinterop.ini. If you receive logon errors, carefully check the credentials and values in the .ini file.

Note
All entries are case-sensitive.

Expand the Concurrency control category, and enter a Concurrency Control value representing the number of calls in Max Concurrent Calls if required, for example, 200. The default value for this field is -1 meaning no protection occurs.

The Max Concurrent Calls parameter activates an overload protection if the back-end server cannot process the amount of data. A concurrent call means a request for which the adapter does not yet have a reply. Set Max Concurrent Calls in instances where the throughput exceeds back-end processing capabilities.

If BizTalk Server submits a request to the send adapter and the number of concurrent calls equals or exceeds the value set for Max Concurrent Calls, the thread submitting the request is saved until the concurrent calls number decreases to below the set value.

Changing this parameter takes effect within a minute as BizTalk Server must retrieve the changes to the adapter configuration saved in the SQL database.
Expand the Event Log category, and enter event log information. For the Event Log Level property, you can select Information, Error, or Warning. Logging at the Error or Warning levels captures important run-time information.

The log provides information on the type of message: Error, Warning, or Information as well as a time stamp indicating when the action occurred. It also provides a brief description of the message and the process information indicating where the message originated.

Expand the Refresh Agent category. Select Yes for the Refresh Agent to force the runtimeagent.exe and the browsingagent.exe processes to restart themselves automatically when required.

For example, you want the process to restart automatically if it loses connection with the server, or if you added something to the server and it does not appear in the BizTalk Add Adapter Wizard for selection.

Note
The browsingagent.exe does not refresh until you terminate the current browsing session. For example, you must exit the “add generated item” browsing session and re-enter to refresh the browsingagent.exe.

Expand the Use Single Sign-On category, enter Affiliate Application, and then set Use SSO to yes or no.
In the <Adapter name> Transport Properties dialog box, click OK to save the changes.
From the Static Solicit-Response Send Port Properties - Configurations - Transport - Primary dialog box, click Send from the left panel to configure send pipeline.
In the Send Pipeline list, select Microsoft.BizTalk.DefaultPipelines.XMLTransmit default pipeline. The BizTalk Adapter for J.D. Edwards OneWorld XE requires that you select the default XMLTransmit pipeline for the Send pipelines.
I n the Receive Pipeline list, select Microsoft.BizTalk.DefaultPipelines.XMLReceive default pipeline. The BizTalk Adapter for J.D. Edwards OneWorld XE requires that you select the default XMLReceive pipeline for the receive pipelines.
Click OK to save the configuration.

Handling String Values

The following section describes how to configure certain string arguments as right-justified (and left padded). J.D. Edwards OneWorld XE exposes two kinds of string values through its interoperability layer:

char: a single character
maximum length string

You will also notice that J.D. Edwards OneWorld XE uses Hungarian notation to name the arguments of these types in the business functions. For example, arguments of these types will begin with:

For a majority of sz type arguments, maximum length string or char array, J.D. Edwards OneWorld XE expects a left-justified value. For a street address line, which is of maximum length 40, J.D. Edwards OneWorld XE expects padding the length with blanks. For example:

"701 North Shoreline Blvd "

In the example, 40 blank spaces are padded. It is not necessary for you to enter the padding as the BizTalk Adapter for J.D. Edwards OneWorld XE provides this for you. For example, you only need to enter:

"701 North Shoreline Blvd"

For some subset of values for this type, J.D. Edwards OneWorld XE expects values that are right justified with padding on the left. For example, for business functions in the B4200310 source module, the argument szBusinessUnit is of length 12. This argument represents a Plant, such as a production facility. For a plant number of 30, J.D. Edwards OneWorld XE expects a value of:

" 30"

To enter a value that will be right-justified, you must enter the parameter into a file called jdearglist.txt. The jdearglist.txt is read at the time you generate the schema. Any value that is listed in this text file is automatically converted to a right-justified value and padded on the left with blanks. You must create jdearglist.txt, using a text editor, with entries describing these parameters. A sample of jdearglist.txt is available in the C:\Program Files\Microsoft BizTalk Adapters for Enterprise Applications\J.D. Edwards OneWorld(r)\config folder. If this file does not exist, or is empty, you will see an informational message in the BizTalk Adapter v1.0 for J.D. Edwards OneWorld XE log when the BizTalk Adapter for J.D. Edwards OneWorld XE first loads.

Note
If you change this file after generating your schema, you must re-generate the schema to refresh the data it contains. To verify that you are using the latest information in this file you can use Task Manager to stop the browsingagent.exe process before re-generating your schema, although this should not be necessary.

The following is an example of the format for entries in the jdearglist.txt file:

<SourceModule>.<BusinessFunction>.<Argument>

For example:

B4200310.F4211FSBeginDoc.szBusinessUnit

For a set of business functions belonging to the same business module, like-named arguments (of the same type) are shared across some or all of the business functions. You can use the wildcard character (*) instead of the business function name. For example:

B4200310.*.szBusinessUnit

Note
When importing a J.D. Edwards OneWorld XE business process to another computer you must copy jdearglist.txt manually.

Installation Information for BizTalk ODBC Adapter for Oracle Database

BizTalk ODBC Adapter for Oracle Database contains a receive adapter and a send adapter that connect supported databases and server systems to BizTalk Server. The receive adapter listens for calls that are outbound from the server system. For more information about the adapter, see the adapter documentation.

Installed Components

BizTalk ODBC Adapter for Oracle Database installer installs and registers the following components in the global assembly cache (GAC):

Microsoft.BizTalk.Adapters.BizUtil.dll
Microsoft.BizTalk.Adapters.CoreManagement.dll
Microsoft.BizTalk.Adapters.CoreReceiver.dll
Microsoft.BizTalk.Adapters.CoreTransmitter.dll

You can verify the registration in the GAC by viewing the assembly folder in your explorer under <%WINDIR%>\assembly folder or use following command in the Visual Studio Command Prompt:

gacutil /l

The adapter specific files are installed in Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\Bin. The following files are installed in Program Files\Microsoft BizTalk Adapters for Enterprise Applications\Oracle Database.

Bin\BTAOracleDBTrace.cmd
Config\btaOracleDBTrace.mof
Sdk\

BizTalk ODBC Adapter for Oracle Database installation also includes samples in the \Sdk directory.

Registering BizTalk ODBC Adapter for Oracle Database to BizTalk Server

After the adapter is installed, you must register the adapter to the BizTalk Management database before you can use it in send ports or receive ports. This step only needs to be performed once on the BizTalk server or a server in the same BizTalk group with the BizTalk Server Administration console installed. For more information about registering an adapter, see http://go.microsoft.com/fwlink/?LinkId=96115.

Enterprise Single Sign-On

BizTalk ODBC Adapter for Oracle Database provides Enterprise Single Sign-On (SSO) support. When you use SSO with the adapter, the adapter obtains the credentials from the SSO Credentials database; therefore, you do not have to enter the logon credentials for the server system in the Transport Properties dialog box. For more information, see http://go.microsoft.com/fwlink/?LinkId=96116.

Creating Send Ports and Receive Ports Using BizTalk ODBC Adapter for Oracle Database

For more information about creating a send port with the adapter, see http://go.microsoft.com/fwlink/?LinkId=96117. For more information about creating receive ports with the adapter, see http://go.microsoft.com/fwlink/?LinkId=96118.

Installation Information for BizTalk ODBC Adapter for Oracle E-Business Suite

BizTalk ODBC Adapter for Oracle E-Business Suite contains a receive adapter and a send adapter that connect supported databases and server systems to BizTalk Server. The receive adapter listens for calls outbound from the server system. For more information about the adapter, see the adapter documentation.

Installed Components

BizTalk ODBC Adapter for Oracle E-Business Suite installer installs and registers the following components in the global assembly cache (GAC):

Microsoft.BizTalk.Adapters.BizUtil.dll
Microsoft.BizTalk.Adapters.CoreManagement.dll
Microsoft.BizTalk.Adapters.CoreReceiver.dll
Microsoft.BizTalk.Adapters.CoreTransmitter.dll

You can verify the registration in the GAC by viewing the assembly folder in your explorer under <%WINDIR%>\assembly folder or use following command in the Visual Studio command prompt:

gacutil /l

The adapter-specific files are installed in Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\Bin. The following files are installed in Program Files\Microsoft BizTalk Adapters for Enterprise Applications\Oracle E-Business Suite:

Bin\BTAOracleAppsTrace.cmd
Config\btaOracleAppsTrace.mof
Sdk\

BizTalk ODBC Adapter for Oracle E-Business Suite installation also includes samples in the \Sdk directory.

Registering BizTalk ODBC Adapter for Oracle E-Business Suite to BizTalk Server

After the adapter is installed, you must register the adapter to the BizTalk Management database before you can use it in send ports or receive ports. This step only needs to be performed once on the BizTalk server or a server in the same BizTalk group with the BizTalk Server Administration console installed. For more information about registering an adapter, see http://go.microsoft.com/fwlink/?LinkId=96119.

If you have already added the adapter to Microsoft BizTalk Server, you do not have to add the adapter again, and you do not have to connect to a database.

Enterprise Single Sign-On

BizTalk ODBC Adapter for Oracle E-Business Suite provides Enterprise Single Sign-On (SSO) support. When you use SSO with the adapter, the adapter obtains the credentials from the SSO Credentials database; therefore, you do not have to enter the logon credentials for the server system in the Transport Properties dialog box. For more information, see http://go.microsoft.com/fwlink/?LinkId=96120.

Creating Send Ports and Receive Ports by Using BizTalk ODBC Adapter for Oracle E-Business Suite

For more information about creating a send port with the adapter, see http://go.microsoft.com/fwlink/?LinkId=96121. For more information about creating a receive port with the adapter, see http://go.microsoft.com/fwlink/?LinkId=96122.

Installation Information for BizTalk Adapter for PeopleSoft Enterprise

BizTalk Adapter for PeopleSoft Enterprise contains a send adapter that connects supported databases and server systems to BizTalk Server. The send adapter enables you to invoke a server system’s call from BizTalk Server. The send adapter (the BizTalk Server Administration Send Handler) configuration specifies the location of the SQL Server database.

Installed Components

BizTalk Adapter for PeopleSoft Enterprise installer installs and registers the following components in the global assembly cache (GAC):

Microsoft.BizTalk.Adapters.BizUtil.dll
Microsoft.BizTalk.Adapters.CoreManagement.dll
Microsoft.BizTalk.Adapters.CoreReceiver.dll
Microsoft.BizTalk.Adapters.CoreTransmitter.dll

You can verify the registration in the GAC by viewing the assembly folder in your explorer under <%WINDIR%>\assembly folder or use following command in the Visual Studio Command Prompt:

gacutil /l.

The adapter-specific files are installed in Program Files\Common Files\ Microsoft BizTalk Adapters for Enterprise Applications\Bin. This folder contains the following files:

Microsoft.BizTalk.Adapters.CoreManagement.dll
Microsoft.BizTalk.Adapters.CoreReceiver.dll
Microsoft.BizTalk.Adapters.CoreTransmitter.dll
psosa.dll

The following files are installed in C:\Program Files\Microsoft BizTalk Adapters for Enterprise Applications\PeopleSoft:

Bin\BTAPeopleSoftTrace.cmd
Config\btaPeopleSoftTrace.mof
Config\GET_CI_INFO.pc
Sdk\

BizTalk Adapter for PeopleSoft installation includes samples in the \Sdk directory.

Registering BizTalk Adapter for PeopleSoft to BizTalk Server

After the adapter is installed, you must register the adapter to the BizTalk Management database before you can use it in send ports or receive ports. This step only needs to be performed once on the BizTalk server or a server in the same BizTalk group with BizTalk Server Administration console installed. For more information about registering an adapter, see Adding the BizTalk Adapters for Enterprise Applications to BizTalk Server.

Enterprise Single Sign-on

BizTalk Adapter for PeopleSoft provides Enterprise Single Sign-On (SSO) support. When you use SSO with the adapter, the adapter obtains the credentials from the SSO Credentials database; therefore, you do not have to enter the logon credentials for the server system in the Transport Properties dialog box. For more information, see http://go.microsoft.com/fwlink/?LinkId=96123.

Creating Send Ports and Receive Ports by Using BizTalk Adapter for PeopleSoft

For more information about creating a send port with the adapter, see http://go.microsoft.com/fwlink/?LinkId=96124. For more information about creating a receive port with the HTTP adapter, see http://go.microsoft.com/fwlink/?LinkId=96125.

Installation Information for BizTalk Adapter for Siebel eBusiness Applications

BizTalk Adapter for Siebel eBusiness Applications is a send adapter. You can use the adapter in a solicit-response send port to send a query and get a response back. If you only want to receive data from Siebel eBusiness Applications, you must follow these steps:

Create a custom receive pipeline using the Set Namespace pipeline component.
Create a receive port accessible from Siebel eBusiness Applications such as a port using the HTTP Adapter. You must configure the receive port to use the custom receive pipeline.

For more information about the adapter, see the adapter documentation.

Installed Components

BizTalk Adapter for Siebel eBusiness Applications installer installs and registers the following components in the global assembly cache (GAC):

Microsoft.BizTalk.Adapters.BizUtil.dll
Microsoft.BizTalk.Adapters.CoreManagement.dll
Microsoft.BizTalk.Adapters.CoreReceiver.dll
Microsoft.BizTalk.Adapters.CoreTransmitter.dll

You can verify the registration in the GAC by viewing the assembly folder in your explorer under <%WINDIR%>\assembly folder or by using following command in the command prompt:

gacutil /l

The adapter-specific files are installed in Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\Bin. This folder contains the following files:

Microsoft.BizTalk.Adapters.CoreManagement.dll
Microsoft.BizTalk.Adapters.CoreReceiver.dll
Microsoft.BizTalk.Adapters.CoreTransmitter.dll
sblcba.dll

The following files are installed under Program Files\Microsoft BizTalk Adapters for Enterprise Applications\Siebel eBusiness Applications:

Bin\btaSiebelTrace.cmd
Classes\SBLJAccess.jar
Config\Siebel\btaSiebelTrace.mof
Sdk\

BizTalk Adapter for Siebel eBusiness Applications installation includes samples in the \Sdk directory.

Registering BizTalk Adapter for Siebel eBusiness Applications to BizTalk Server

After the adapter is installed, you must register the adapter to the BizTalk Management database before you can use it in send ports or receive ports. This step only needs to be performed once on the BizTalk server or a server in the same BizTalk group with the BizTalk Server Administration console installed. For more information about registering an adapter, see http://go.microsoft.com/fwlink/?LinkId=96126.

Enterprise Single Sign-on

BizTalk Adapter for Siebel eBusiness Applications provides Enterprise Single Sign-On (SSO) support. When you use SSO with the adapter, the adapter obtains the credentials from the SSO Credentials database; therefore, you do not have to enter the logon credentials for the server system in the Transport Properties dialog box. For more information, see http://go.microsoft.com/fwlink/?LinkId=96127.

Creating Send Ports and Receive Ports by Using BizTalk Adapter for Siebel eBusiness Applications

For more information about creating a send port with the adapter, see http://go.microsoft.com/fwlink/?LinkId=96128. For more information about creating a receive port with the adapter, see http://go.microsoft.com/fwlink/?LinkId=96129.

Installation Information for BizTalk Adapter for TIBCO Enterprise Message Service

BizTalk Adapter for TIBCO Enterprise Message Service (EMS) contains receive and send functionality that connect supported databases and server systems to BizTalk Server.

The receive side listens for calls that are outbound from the server system.
The transmit side enables you to invoke a server system’s call from BizTalk Server.
For more information about the adapter, see the adapter documentation.

Installed Components

BizTalk Adapter for TIBCO EMS installer installs and registers the following components in the global assembly cache (GAC):

Microsoft.BizTalk.Adapters.TibcoEMS.dll
Microsoft.BizTalk.Adapters.TibcoEMS.Properties.dll

You can verify the registration in the GAC by viewing the assembly folder in your explorer under <%WINDIR%>\assembly folder or by using the following command in the Visual Studio Command Prompt:

gacutil /l.

The adapter-specific files are installed in C:\Program Files\Common Files\ Microsoft BizTalk Adapters for Enterprise Applications\Bin folder. This folder contains the following files:

Microsoft.BizTalk.Adapters.CoreManagement.dll
Microsoft.BizTalk.Adapters.CoreReceiver.dll
Microsoft.BizTalk.Adapters.CoreTransmitter.dll

The following files are installed under C:\Program Files\Microsoft BizTalk Adapters for Enterprise Applications\TIBCO(r) Enterprise Message Service(TM):

Bin\BTATibcoEMSTrace.cmd
Bin\Microsoft.BizTalk.Adapters.TibcoEMS.dll
Bin\Microsoft.BizTalk.Adatpers.TibcoEMS.Properties.dll
Config\btaTibcoEMSTrace.mof
Sdk\

BizTalk Adapter for TIBCO EMS installation includes samples in the \Sdk directory.

Registering BizTalk Adapter for TIBCO EMS to BizTalk Server

After the adapter is installed, you must register the adapter to the BizTalk Management database before you can use it in send ports or receive ports. This step only needs to be performed once on the BizTalk server or a server in the same BizTalk group with the BizTalk Server Administration console installed. For more information about registering an adapter, see Adding the BizTalk Adapters for Enterprise Applications to BizTalk Server.

Enterprise Single Sign-On

BizTalk Adapter for TIBCO EMS provides support for Enterprise Single Sign-On (SSO). When you use SSO with the adapter, the adapter obtains the credentials from the SSO Credentials database; therefore, you do not have to enter the logon credentials for the server system in the Transport Properties dialog box. For more information, see http://go.microsoft.com/fwlink/?LinkId=96130.

Creating Send Ports and Receive Ports by Using BizTalk Adapter for TIBCO EMS

For more information about creating a send port with the adapter, see http://go.microsoft.com/fwlink/?LinkId=96131. For more information about creating a receive port with using the adapter, see http://go.microsoft.com/fwlink/?LinkId=96132.

Limitations

BizTalk Adapter for TIBCO EMS uses TIBCO.EMS.dll to communicate with the server. The following are limitations when you use the TIBCO.EMS.dll:

Message compression, which enables the TIBCO EMS client to send messages in a compressed form to EMS, is not available.
Encryption of messages between the adapter and the server is not available. The TIBCO.EMS.dll does not allow for SSL encryption using the OpenSSL libraries.
Administration API for EMS is not supported.

Installation Information for BizTalk Adapter for TIBCO Rendezvous

BizTalk Adapter for TIBCO Rendezvous contains receive and send functionality that connects supported databases and server systems to BizTalk Server.

The receive side listens for calls that are outbound from the server system.
The transmit side enables you to invoke a server system’s call from BizTalk Server.
For more information about the adapter, see the adapter documentation.

Installed Components

BizTalk Adapter for TIBCO Rendezvous installer installs and registers the following components in the global assembly cache (GAC):

Microsoft.BizTalk.Adapters.TibcoRV
Microsoft.BizTalk.Adapters.TibcoRV.Common
Microsoft.BizTalk.Adapters.TibcoRV.Service
Microsoft.BizTalk.Adapters.TibcoRVManagement
Microsoft.BizTalk.Adapters.TibcoRVReceiver
Microsoft.BizTalk.Adapters.TibcoRVTransmitter
Microsoft.BizTalk.Adapters.TibRV.Properties

You can verify the registration in the GAC by viewing the assembly folder in your explorer; for example, <%WINDIR%>\assembly, or by using the following command from the Visual Studio command prompt:

gacutil /l

The adapter-specific files are installed in Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\Bin. This folder contains the following files:

Microsoft.BizTalk.Adapters.CoreManagement.dll
Microsoft.BizTalk.Adapters.CoreReceiver.dll
Microsoft.BizTalk.Adapters.CoreTransmitter.dll

The following files are installed in Program Files\Microsoft BizTalk Adapters for Enterprise Applications\TIBCO Rendezvous:

Bin\BTATibcoRVTrace.cmd
Bin\mbaRV.exe
Bin\Microsoft.BizTalk.Adapters.TibcoRV.Common.dll
Bin\Microsoft.BizTalk.Adapters.TibcoRV.dll
Bin\Microsoft.BizTalk.Adapters.TibcoRV.Service.dll
Bin\Microsoft.BizTalk.Adapters.BizUtil.dll
Bin\Microsoft.BizTalk.Adapters.TibcoManagement.dll
Bin\Microsoft.BizTalk.Adapters.TibcoReceiver.dll
Bin\Microsoft.BizTalk.Adapters.TibcoTransmitter.dll
Bin\Microsoft.BizTalk.Adapters.TibRV.Properties.dll
Config\btaTibcoRVTrace.mof
Sdk\

BizTalk Adapter for TIBCO Rendezvous installation includes samples in the \Sdk directory.

Registering BizTalk Adapter for TIBCO Rendezvous to BizTalk Server

After the adapter is installed, you must register the adapter to the BizTalk Management database before you can use it in send ports or receive ports. This step only needs to be performed once on the BizTalk server or a server in the same BizTalk group with the BizTalk Server Administration console installed. For more information about registering an adapter, see Adding the BizTalk Adapters for Enterprise Applications to BizTalk Server.

Enterprise Single Sign-On

BizTalk Adapter for TIBCO Rendezvous provides Enterprise Single Sign-On (SSO) support. When you use SSO with the adapter, the adapter obtains the credentials from the SSO Credentials database; therefore, you do not have to enter the logon credentials for the server system in the Transport Properties dialog box. For more information, see http://go.microsoft.com/fwlink/?LinkId=96133.

Creating Send Ports and Receive Ports by Using BizTalk Adapter for TIBCO Rendezvous

For more information about creating a send port with the adapter, see http://go.microsoft.com/fwlink/?LinkId=96134. For more information about creating a receive port with the adapter, see http://go.microsoft.com/fwlink/?LinkId=96135.

Activating Tracing for all the Adapters

The file name used with Windows tracing is up to the administrator. The application writes to the operating system, which ignores all logs until you want the logs for a particular back-end system. You do this by running a separate BizTalk Adapters for Enterprise Applications command file. One of the arguments for that command is the name of the file that will be used to capture the trace information. For more information, see the following section, "Using Windows Trace Event."

Trace files are installed in C:\Program Files\Microsoft BizTalk Adapters for Enterprise Applications\<adapter name>\, as follows:

Bin\BTA<adapter name>Trace.cmd
Config\bta<adapter name>Trace.mof

Using Windows Trace Event

The adapters log error, warning, and information messages to Windows Event Viewer. You can view additional tracing messages by using the Event Tracing for Windows (ETW) tool. When ETW is enabled, it creates an *.etl file to receive the messages. This file is in binary format and must be converted to be read. To do this, you must have a consumer application available to interpret the *.etl file, for example, Windows tracerpt.exe or tracedmp.exe.

ETW Components

Event Tracing for Windows has three components:

Controller application: Activates and deactivates a provider, for example, tracelog.exe or logman.exe. You set your PATH environment variable to point to the location of tracelog.exe. This ensures that BTA<Adapter Name>Trace calls can locate tracelog.exe in the system. By default, BTA<Adapter Name>Trace searches the current path.

Note
Tracelog.exe is available from the Windows 2000 Server Resource Kit Tools for Administrative Tasks and is compatible with the commands provided by Microsoft BizTalk Adapters for Enterprise Applications. To use logman.exe, see the logman documentation.

Consumer application: Reads logged events. For the consumer application to be able to read the event in the .etl file, Event Tracing for Windows must dump them into that file. Typically this is done when the controller deactivates the tracing.
To use the consumer application without deactivating the trace, the controller must activate the trace with the real-time option, <Real time> = -rt.
Provider: Used to provide the event. Each adapter includes five different providers. They are registered in Windows Management Instrumentation (WMI). To find the registered providers in the root\WMI\EventTrace path, you can use tools such as WMI CIM Studio.
The five providers enable you to log different kinds of messages:
- Receiver Logging Provider: The <Trace element> switch is - receiver.
- Receiver CastDetails Provider: The <Trace element> switch is - castDetailsReceive.
- Transmitter Logging Provider: The <Trace element> switch is - transmitter.
- Transmitter CastDetails Provider: The <Trace element> switch is - castDetailsTransmit.
- Management Logging Provider: The <Trace element> switch is - management.

To use ETW, run the command for the specific adapter, BTA<Adapter Name>Trace.cmd. You use this command as follows:

BTA<Adapter Name>Trace <Trace element> -start [-cir <MB>| 
    -seq <MB>] [-rt] logfile
BTA<Adapter Name>Trace <Trace element> -stop

Where:

<Trace element> (required) is the kind of provider. The options are as follows:

-castDetailsTransmit

-transmitter

-castDetailsReceive

-receiver

-management

-start, -stop: Activate or deactivate the provider.

-cir <MB>: Size and kind of file. -cir is a circular file. <MB>: Size in megabytes.

-seq <MB>: Size and kind of file. -seq is a sequential file. <MB>: Size in megabytes.

-rt: Set the real-time mode on.

Logfile: Name of the log file (c:\rtlog.etl is the default).

For example:

BTA<adapter name>Trace -transmitter -start -cir 10 -rt c:\log\mylog.etl
BTA<adapter name>Trace -transmitter -stop

You use the tracerpt.exe command to format the .etl files.

Adding the BizTalk Adapters for Enterprise Applications to BizTalk Server

Follow these steps to add the Microsoft BizTalk Adapters for Enterprise Applications to BizTalk Server.

To register a new adapter

Click Start, point to Programs, point to Microsoft BizTalk Server 2006, and then click BizTalk Server Administration.
Expand BizTalk Server Administration, expand BizTalk Group, expand Platform Settings, and then expand Adapters.
Right-click Adapters, point to New, and then click Adapter.
Enter a Name for the adapter. For example, PeopleSoft.
From the Adapter list, select the adapter, and then click OK.
The prompt reads “This configuration changes requires host instance restart. Please restart the associated host instances for the changes to take effect." Click OK to finish the configuration.
From the BizTalk Server 2006 Administration console, navigate to BizTalk Server 2006 Administration -> BizTalk Group -> Platform Settings-> Host Instance.
Right-click BizTalkServerApplication, and then click Restart. BizTalkServerApplication is the default in-process host instance. If you assigned the adapter to a different host instance, you must restart that host instance instead.

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

Microsoft, BizTalk, Excel, Windows, Windows Server, Windows Vista, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

All other trademarks are property of their respective owners.