Changes in This Release of the Adapters

Requirements for BizTalk Adapter for JD Edwards OneWorld XE

Preparing to Use JD Edwards OneWorld

Creating and Installing the Custom Package

File settings for jdeinterop.ini

Requirements for BizTalk Adapter for JD Edwards EnterpriseOne

Executing a JD Edwards EnterpriseOne Master Business Function

Interoperability Framework

Setting String Justification in Jdearglist

Understanding the jdeinterop.ini File

Requirements for BizTalk Adapter for PeopleSoft Enterprise

Receive Handler PeopleSoft Requirements

Send Handler PeopleSoft Requirements

Preparing to Use PeopleSoft

Requirements for BizTalk Adapter for TIBCO Rendezvous

Requirements for BizTalk Adapter for TIBCO Enterprise Message Service

Installing BizTalk Adapters for Enterprise Applications

Installation Information for BizTalk Adapter for JD Edwards OneWorld

Single Sign-On

Installed Components

Installation Information for BizTalk Adapter for JD Edwards EnterpriseOne

Installed Components

Installation Information for BizTalk Adapter for PeopleSoft Enterprise

Installed Components

Installation Information for BizTalk Adapter for TIBCO Rendezvous

Installed Components

Adding TIBCO.Rendezvous.dll to the GAC

Installation Information for BizTalk Adapter for TIBCO Enterprise Message Service

Installed Components

Adding TIBCO.EMS.dll API to the GAC

Activating Tracing for all the Adapters

Using Windows Trace Event

Adding the BizTalk Adapters for Enterprise Applications to BizTalk Server

Copyright

This document lists the steps to install and configure the Microsoft BizTalk Adapters for Enterprise Applications on BizTalk Server 2013 and BizTalk Server 2013 R2.

Microsoft BizTalk Adapters for Enterprise Applications includes the following adapters:

  • Microsoft BizTalk Adapter for JD Edwards OneWorld

  • Microsoft BizTalk Adapter for JD Edwards EnterpriseOne

  • Microsoft BizTalk Adapter for PeopleSoft Enterprise

  • Microsoft BizTalk Adapter for TIBCO Rendezvous

  • Microsoft BizTalk Adapter for TIBCO Enterprise Message Service

Important

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

Caution

It is highly recommended that you back-up all data before you make any configuration changes.

Note

For more detailed information, see the specific Help documentation for each adapter. For information about specific enterprise applications, see the enterprise application-specific Help.

Changes in This Release of the Adapters

In the release of adapters, the changes are mostly related to version support for enterprise applications and supporting the new Windows OS versions. Supported Line-of-Business (LOB) and Enterprise systems lists the supported versions.

Top of page

Requirements for BizTalk Adapter for JD Edwards OneWorld XE

Microsoft BizTalk Adapter for JD Edwards OneWorld XE requires the following:

BizTalk Server 2013 R2 BizTalk Server 2013

Operating System

  • Windows 8.1

  • Windows 7 SP1

  • Windows Server 2012

  • Windows Server 2012 R2

  • Windows 8

  • Windows 7 SP1

  • Windows Server 2012

  • Windows Server 2008 R2 SP1

JD Edwards OneWorld XE

Supported Line-of-Business (LOB) and Enterprise systems lists the supported versions.

Supported Line-of-Business (LOB) and Enterprise systems lists the supported versions.

JD Edwards Enterprise server

Windows

Windows

JD Edwards Deployment server

Windows

Windows

Preparing to Use JD Edwards OneWorld

This section describes the requirements for JD Edwards OneWorld to work with Microsoft BizTalk Adapter for JD Edwards OneWorld.

JAR Files and the CLASSPATH

JD Edwards OneWorld JAR files must be available to the adapter:

For instance, to connect to B7.3.3.3 Version, the below jar files are required. Depending on the server you connect, the jar file list may change.

  • Connector.jar

  • Kernel.jar

These files are located on a computer running JD Edwards OneWorld, at the following locations:

  • JD Edwards OneWorld XE_install_Directory\System\classes\Connector.jar

  • JD Edwards OneWorld XE_install_Directory\System\classes\Kernel.jar

You can copy these files to any location; however, you must specify the location of the JAR files in the CLASSPATH. The CLASSPATH must include both the full path of the file and the name of the JAR file (separated by a semicolon).

BizTalk Adapter for JD Edwards OneWorld provides the JDEJAccess JAR file for use with JD Edwards OneWorld. By default, the JDEJAccess.jar file is referenced from the <Adapter_Installation>\classes folder:

  • Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\ J.D. Edwards OneWorld(r)\classes\JDEJAccess.jar

Note

You must verify the registration of the jdeinterop.ini file before you can use BizTalk Adapter for JD Edwards OneWorld. Make sure that you include a path to this file in the JDE Transport Property page when you create the send port in BizTalk Server. For a complete explanation, see "Customizing the jdeinterop.ini File."

Creating the BTSLIBinterop.jar File

You must create the BTSLIBinterop.jar file, and make sure that it can be accessed by the adapter. You can use the following sample as a guide:

  1. Create the BTSLIB.cmd file that contains the following code:

    define library BTSLIB
    login
    library BTSLIB
    interface JDEAdapter
    import B5500900
    build
    logout
  2. Run the following command:

    GenJava  /cmd  .\BTSLIB.cmd

Verifying Your Setup

Follow this checklist to verify the setup of JD Edwards OneWorld:

  1. Use a supported version, including service pack number (Supported Line-of-Business (LOB) and Enterprise systems). Service packs (ESUs and ASUs) update the system binaries. The prerequisite service pack provides the ASU/ESU menu choice for import.

  2. Configure the jdeinterop.ini file to use the correct drive for logging, if it differs from drive C. For example, your JD Edwards OneWorld update could fail if the TEMP directory is out of space.

  3. Determine whether you must add a configuration file for the left/right padding of the JD Edwards OneWorld fields.

  4. Verify that your JAVA_HOME environment variable is pointing to your Java Development Kit (JDK) installation to enable the javac and java commands from any program on the computer.

  5. Verify that the CLASSPATH environment variable is set; this enables BizTalk Adapter for JD Edwards OneWorld to locate the Kernel.jar and Connect.jar files.

    The path of the JAR files is case sensitive.

  6. Test the environment by typing the following command, which is case sensitive.

    javap -s -p com.microsoft.jde.JDEJAccess
  7. The command you give, javap, is the Java Class File Disassembler:

    http://java.sun.com/j2se/1.3/docs/tooldocs/solaris/javap.html
  8. The javap command disassembles a class file. Its output depends on the options used. If no options are used, javap prints out the package, protected, and public fields and methods of the classes passed to it. javap prints its output to stdout.

    If there are no errors, all the Java files and their dependencies are in the CLASSPATH.

  9. Set up the DNS resolution by configuring the local host file, C:\WINNT\system32\drivers\etc\hosts, with the server name of the JD Edwards OneWorld system.

Creating and Installing the Custom Package

You must install the BTSREL custom package to use BizTalk Adapter for JD Edwards OneWorld.

This section describes:

  • The JD Edwards OneWorld custom package-creation process.

  • How to create and install BTSREL.

  • The BTSREL objects created in JD Edwards OneWorld.

Note

BTSREL.exe is a custom package (an automated software update, or ASU, in JD Edwards OneWorld terminology). It contains business functions to extract metadata. A custom package should be created for a specific configuration and version of JD Edwards OneWorld.

Defining a Custom Package

A custom package is a post-release deliverable that provides software changes for specific purposes, such as regulatory changes or enhancements. These custom packages are created for specific functionality. For example, BTSREL is created to extract metadata. When the BTSREL custom package is installed, it updates selected modules in the JD Edwards OneWorld environment. To update, BTSREL objects must be merged into the appropriate JD Edwards OneWorld environment. For a detailed list of modules updated by BTSREL, see the list of modules.

Installing the Custom Package BTSREL

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

The existing BTSREL.exe package directly works with the B7333 version. For the package to work with the B7334 version, you must do the following:

  1. Download and extract the contents of BTSREL.exe to your working folder.

  2. Modify both the ReleaseLevelRequired and the Release values to B7334 in the Deployment.Inf file.

  3. Run the Setup.

To install the custom package, BTSREL, the following are required:

  • Deployment server installation

  • Installation Workbench

Installing BTSREL on the Deployment Server

The custom package only works on a Windows operating system and is used with the deployment server. It must be built on the deployment server and then deployed to the enterprise server. The enterprise server is usually a production server, and can be on either a Windows or UNIX operating system.

Note

When applying the ASU to the JD Edwards OneWorld deployment server, verify that you are in Update mode. The Proof mode verifies that there are no bugs in the ASU, whereas Update mode is designated for when you apply the ASU.

To install the custom package on the deployment server

  1. Log on to the deployment server as user JDE.

  2. Create a new folder, named BTSREL, on the Deployment Server (root) /B7 folder.

  3. Copy BTSREL.exe to the newly created BTSREL folder.

  4. Run BTSREL.exe from the.../B7/BTSREL folder.

    JD Edwards OneWorld Installation Manager automatically starts after the executable file opens.

  5. On the JD Edwards OneWorld Deployment Server Setup Type screen, click Next, and then click Finish.

    After the installation finishes, a dialog box informs you if the installation was successful.

  6. Log on to the JDEPLAN environment as user JDE on the JD Edwards OneWorld deployment server.

    1. If the electronic software update (ESU) that includes SAR #4533357 has not been installed on the system, select Software Updates from the System Installation Tools menu (GH9612).

    2. Enter 02 for option 1 in the Processing Options panel.

    3. If the ESU that includes SAR #4533357 has been installed on the system, select Application Software Update from the System Installation Tools menu (GH9612).

Installing BTSREL on the JD Edwards OneWorld WorkBench

To install BTSREL on the JD Edwards OneWorld WorkBench:

  1. On the Work with Application Update screen, double-click the BTSREL update, and then click Next.

  2. Double-click the environments where you want the update installed, and then click Next.

    1. Check Unattended Workbench if you want the software update to run in unattended mode.

    2. Select Backup if you want the backup of the specifications (so that the original specifications can be restored).

  3. On the Work with Installation Plan screen, select the plan for the update you are installing, and then click Select.

  4. See the automatically generated PDFs for errors after the installation is finished.

    Note

    If errors occur, look in the JD Edwards OneWorld Software Update Guide for troubleshooting tips, or contact JD Edwards OneWorld directly.

  5. Manually register the business function library using the steps included in "Manually Registering the Business Function Library" in this section.

Uninstalling the Custom Package

There is no requirement to uninstall the custom package. However, if you want to clean the system, you can uninstall in different ways. You must rebuild the package after uninstalling. You can use one of the following methods:

  • Using the JD Edwards OneWorld Deployment Server, Gh8612—P96470, on the ROW menu, select Update, and then click Uninstall.

  • Check out all the custom objects (BTSREL) to a client computer and delete them.

  • Apply a previous snapshot of database.

During the clean-up, verify any other modifications to the other objects of JD Edwards OneWorld.

Manually Registering the Business Function Library

Because of a limitation of the JD Edwards OneWorld product packaging process, the custom Business Function Library DLL for BizTalk Adapter for JD Edwards OneWorld must be manually registered with JD Edwards OneWorld. This process consists of the following four steps:

Step 1: Create the Custom Business Function Library

Using JD Edwards OneWorld Object Management Workbench (OMW), create the Custom Business Function Library. The following procedure must be performed on initial setup and applies to all platforms.

To create the custom business function library

  1. Start the Object Management Workbench (fast path: "OMW" or menu selection: GH902 Object: P98220).

  2. Click Add, and select the option for Business Function Library.

  3. Enter the following information for the New Business Function Library Object:

    • Name: ACBLIB

    • Description: Microsoft DLL

    • Product Code: 55

    • Product System Code: 55

  4. Click OK.

Step 2: Rebuild Libraries from the Deployment Server

The following procedure must be performed on initial setup for each platform.

To rebuild libraries from the deployment server

  1. To start the BusBuild program in a standalone mode, click Start, click Run, and then click busbuild.exe.

    You are prompted to log on to JD Edwards OneWorld.

  2. Log on to JD Edwards OneWorld in the pathcode (PY7333, PD7333, or DV7333).

  3. In the Rebuild Libraries list, select the Build.

Step 3: Copy the Custom DLL

Copy the custom DLL from the pathcode directory to the parent package directories on the JD Edwards OneWorld deployment server and on the JD Edwards OneWorld Enterprise Server, as follows:

  • By using the JD Edwards OneWorld XE Deployment Server:

    1. Copy ACBLIB.dll from DV7333\bin32 to DV7333\Packages\DV7333FA\bin32.

    2. Copy ACBLIB.def, ACBLIB.dmp, and ACBLIB.mak from DV7333\obj folder to DV7333\Packages\DV7333FA\obj folder.

    3. Copy ACBLIB.exp, ACBLIB.lib, and sACBLIB.lib from DV7333\lib32 folder to DV7333\Packages\DV7333FA\lib32 folder.

  • By using the JD Edwards OneWorld Enterprise Server:

    After each directory and file is created, verify the authorization.

    1. Create a directory ACBLIB under DV7333FA\obj\.

    2. Create a directory ACBLIB under DV7333FA\source.

    3. FTP b5500900.c from Deployment Server DV7333\source directory to DV7333FA\source\ACBLIB directory.

    4. FTP b5500900.h from Deployment Server DV7333\include directory to DV7333FA\include directory.

Step 4: Build a Full Package

Because of a limitation of the JD Edwards package-build process, you must build a full package for the environments to which you applied the BTSREL update, or the update package build will not work correctly. See the JD Edwards documentation on how to build a full package build.

Note

When you apply JD Edwards OneWorld ASU/ESUs, the ASU/ESU does not typically create new library and business functions. Therefore, the process is simple: however, the BizTalk Adapter for JD Edwards OneWorld custom package creates a new library; therefore, you must perform extra steps, such as manually creating a directory and running a full package build.

List of Modules

The custom package BTSREL creates the following objects in JD Edwards OneWorld. BTSREL contains business functions to extract metadata and custom functions to test the data types.

Note

There is a bug in the JD Edwards OneWorld update. If you do not have all the business and custom functions, verify that a full package build was performed, rather than an update package build.

If you are missing files from the list, for example, if you have everything below ACBTEST but nothing above it, you might be missing the Data Dictionary (DD) items. You can go to Work With Data Items and look for missing files.

If you are missing other items, such as ACBCHAR01, ACBDATE01, ADBINT01, ACBMATH01, and ACBSTR01, these are the Primary Data Elements. When you merge objects from planner to DEV, many reports run in the background. You can open the merge reports and look for errors. The reports should list all the items and indicate that they were completed without errors or warnings. With this verification, you can continue because all items are accounted for.

  • ACBCHAR01 - TEST CHAR TYPE 01

  • ACBCUST - ACB CUSTOMER ID

  • ACBDATE01 - TEST DATE TYPE 01

  • ACBDEF - ACB FUNCTION TYPE DEFINITION

  • ACBFCNT - ACB FUNCTION NAME LIST COUNT

  • ACBFUNC - ACB FUNCTION NAME LIST

  • ACBFUNCN - ACB FUNCTION NAME

  • ACBINT01 - TEST INTEGER TYPE 01

  • ACBLIB - CONTROL BROKER LIBRARY

  • ACBMATH01 - TEST MATH TYPE 01

  • ACBNEWS - ACB NEW STATUS

  • ACBORDER - ACB ORDER NUMBER

  • ACBPRC - ACB ITEM PRICE

  • ACBPROD - ACB PRODUCT ID

  • ACBQTY - ACB ITEM QUANTITY

  • ACBRES - ACB RESULT INDICATOR

  • ACBSTAT - ACB STATUS

  • ACBSTR01 - TEST STRING TYPE 01

  • ACBTEST - ACB TEST SCREEN

  • ACBTEST2 - ACB TEST SCREEN 2

  • ACBTEST3 - ACB TEST SCREEN 3

  • B5500900 - CONTROL BROKER SUPPORT MODULE

  • D5500900 - CONTROL BROKER DATA STRUCTURE

  • D5500900A - CONTROL BROKER DATA STRUCTURE

  • D5500900B - FETCH PRICE DATA STRUCTURE

  • D5500900C - GET CUSTOMER STATUS DATA STRUCTURE

  • D5500900D - SET CUSTOMER STATUS DATA STRUCTURE

  • D5500900E - UPDATE SALES ORDER STATUS DATA STRUCTURE

  • D5500900F - TEST INTEGER

  • D5500900G - TEST STRING

  • D5500900H - TEST DATE

  • D5500900I - TEST CHAR

  • D5500900J - TEST MATH NUMERIC

  • D5500900K - TEST DATE 2

Customizing the jdeinterop.ini File

The JD Edwards OneWorld XE connector classes in Connector.jar and Kernel.jar require that you use a configuration file named jdeinterop.ini. This file is defined by the JD Edwards OneWorld software and uses its terminology. For more information about the purpose and terminology of this file, see the JD Edwards Interoperability Guide Release OneWorld. There is a sample jdeinterop.ini file in <Adapter_Installation>\config\jde.

You must edit jdeinterop.ini to match the parameter values that you defined in the Transport Properties screen. Multiple JD Edwards OneWorld logical systems can share the same jdeinterop.ini file if their parameters are compatible. Generally, if two logical systems point to two different JD Edwards OneWorld computers, they will need two different copies of jdeinterop.ini.

Note

The logging in jdeinterop.ini should be kept turned off, and the parameters for the various log files can safely be ignored.

The following table itemizes the settings found in the jdeinterop.ini file. The information is organized by section. For example [JDENET] and the sections are listed in the order that they appear in the JD Edwards OneWorld software.

File settings for jdeinterop.ini

Section Parameter and Description

[JDENET]

EnterpriseServerTimeout. The time-out value for a request to the enterprise server in milliseconds. The default size is 120000.

maxPoolSize. The JDENET socket connection pool size. The default size is 30.

[SERVER]

glossaryTextServer. The enterprise server and port that provide glossary text information. This is the server that returns text descriptions for errors. This is frequently the same host and port as the JD Edwards OneWorld application server. There may be more than one glossary server for different supported language encodings. For example, JDED:6010 or actsrv1:6009. The values must match those set in System Definition.

codePage. The encoding scheme. The default is 1252.

  • 1252 English and Western European

  • 932 Japanese

  • 950 Traditional Chinese

  • 936 Simplified Chinese

  • 949 Korean

[LOGS]

log= c:\jas.log. Location of the log file. You can safely ignore this parameter.

debuglog= c:\jasdebug.log. Location of debug log file. You can safely ignore this parameter.

Debug. Determines whether JDENET debugging is on. The default is FALSE.

[DEBUG]

JobFile= c:\Interop.log. Location of error file. You can safely ignore this parameter.

DebugFile= c:\InteropDebug.log. Location of debug file. You can safely ignore this parameter.

log= c:\net.log. Location of log file. You can safely ignore this parameter.

debugLevel= 0 - 12. Debug levels. You can safely ignore this parameter. This defines the level of tracing provided by the COM Connector and the Callobject component in the specified log file, in the COM server only.

  • 0 None. Logging is turned off and only errors are written to the JobFile.

  • 2 Errors (error messages)

  • 4 System Errors (exception messages)

  • 6 Warning Information

  • 8 Min Trace (Key operations. For example, Logon, Logoff, Business Function calls.)

  • 10 Troubleshooting Information (Help).

  • 12 Complete Debug Information (Logs everything)

  • By default, you do not have to turn on tracing, but tracing is useful when you are debugging your code.

    NetTraceLevel=0. Trace levels. You can safely ignore this parameter. Defines the level of tracing provided by the ThinNet component in the specified log file, in the COM server only. The odd values are reserved for future levels to be added.

    The following list describes debug levels even more:

    • 0 No trace

    • 1 Refers to the Record process ID, thread ID, and the available socket status when a new connection is added and the socket pool is searched.

    • 2 Includes the information in trace level 1 and also traces every call made in the connection manager class.

    • 3 Includes all information in trace level 2, and also traces getPort() calls and getHost() calls.

[INTEROP]

enterpriseServer. This value is the name of the host server. Make sure that this value is the same value that you enter in the Host Name field in the JDE Credentials section in System Definition in the Transport Properties dialog box. The default is JDED.

port. This value is the port number that is used to exchange data. Make sure that this value is the same value that you enter in the Port Number field in the JD Edwards Credentials section in the Transport Properties, System Definition. For example, 6010 or 6009. The values must match those set in System Definition.

inactive_timeout. The time-out value in milliseconds for a transaction in auto-commit mode. If the user is inactive for this period of time (in milliseconds), the interop server logs off the user. You can change this value to a shorter period of time. The default is 1200000.

manual_timeout. The time-out value in milliseconds for a transaction in manual commit mode. The default is 120000.

Repository. Points to the location of the directory that contains Connector.jar and Kernel.jar. On UNIX, this is a full path.

[CORBA]

You can safely ignore this parameter.

Multithread. The setting can be ignored. Set to 1 for multithread support for CORBA.

Objects= CORBA::Connector;CORBA::OneWorldVersion

Defines the objects for the CORBA server to create at startup. Also replaces the -DIORFILENAME = command-line option, for example: CORBA::Connector=connector.ior.

Top of page

Requirements for BizTalk Adapter for JD Edwards EnterpriseOne

Microsoft BizTalk Adapter for JD Edwards EnterpriseOne requires the following:

BizTalk Server 2013 R2 BizTalk Server 2013
  • Windows 8.1

  • Windows 7 SP1

  • Windows Server 2012

  • Windows Server 2012 R2

  • Windows 8

  • Windows 7 SP1

  • Windows Server 2012

  • Windows Server 2008 R2 SP1

JD Edwards EnterpriseOne

Supported Line-of-Business (LOB) and Enterprise systems lists the supported versions.

JD Edwards EnterpriseOne

Supported Line-of-Business (LOB) and Enterprise systems lists the supported versions.

Note

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

Executing a JD Edwards EnterpriseOne Master Business Function

You can use the BizTalk Adapter for JD Edwards EnterpriseOne to invoke a JD Edwards EnterpriseOne master business function, such as Address Book, Purchase Order, or Sales Order. You can also use the adapter as part of an integration effort to connect JD Edwards EnterpriseOne with BizTalk Server.

Accessing Data Stored in JD Edwards EnterpriseOne

The adapter accepts XML messages to enable BizTalk Server applications to communicate and exchange transactions with JD Edwards EnterpriseOne using one of the following:

  • Transmit Adapter, which uses a Static Solicit-Response Send port to send a message to JD Edwards EnterpriseOne and expects a response.

  • Receive Adapter, which uses a Static One-Way Receive port to receive messages from JD Edwards EnterpriseOne.

Interoperability Framework

JD Edwards EnterpriseOne provides for integration with systems through its interoperability framework. The adapter uses the JD Edwards EnterpriseOne framework and takes advantage of various integration access methods to provide the greatest amount of flexibility and functionality.

BizTalk Adapter for JD Edwards EnterpriseOne supports the following integration access methods:

  • JD Edwards EnterpriseOne ThinNet API

  • JD Edwards EnterpriseOne XML

  • JD Edwards EnterpriseOne unedited transaction tables (Z tables)

The adapter uses the JD Edwards EnterpriseOne ThinNet API to communicate with the JD Edwards EnterpriseOne application. By using the ThinNet API, the adapter can invoke one master business function (MBF) in a single unit of work (UOW). When an MBF fails, the whole UOW fails. This prevents partial updates. The validation of data, business rules, and communications to the underlying database are handled by the JD Edwards EnterpriseOne application.

JD Edwards Outbound Processing Framework

In the outbound process, the event starts when a specific MBF is executed in the JD Edwards EnterpriseOne environment. The MBF writes the required information for the event into the appropriate interface table and then notifies the subsystem batch function (BF) that an event occurred. The subsystem BF then includes an entry about the event on the subsystem data queue.

The outbound subsystem retrieves the data queue entry and looks in the Data Export Control table for the external processes to notify. The outbound subsystem then calls the BizTalk Adapter for JD Edwards EnterpriseOne listener with notification. The listener passes the notification to the generator. The generator then uses the JD Edwards EnterpriseOne ThinNet API to retrieve the appropriate information from the interface table.

Setting String Justification in Jdearglist

To configure certain string arguments as right-justified and left padded in the J.D. Edwards EnterpriseOne jdearglist.txt file, you must know what business function you want to access; specifically, you must know which fields in the business function you want to call.

You must update the jdearglist.txt before you generate the bindings (schemas) in the orchestration. The instructions for updating the jdearglist.txt file outlined in the "Handling String Values" section.

If you receive a jdearglist.txt warning message in the log, its purpose is to inform you that the jdearglist.txt is missing. However, if you are running the SalesOrder or PurchaseOrder business function, you must have that file in your PATH or it will not work.

Understanding the jdeinterop.ini File

The JD 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 JD Edwards EnterpriseOne software and uses its terminology. For more information about the purpose and terminology of this file, see the JD Edwards Interoperability Guide. There is a sample jdeinterop.ini file in: Program Files\ Microsoft BizTalk Adapters for Enterprise Applications\ J.D. Edwards EnterpriseOne(r)\config.

It is not recommended that you edit this file manually because it interacts with the Transport Properties dialog box for the send port -- for example those fields marked as <configured by BizTalk>.

Top of page

Requirements for BizTalk Adapter for PeopleSoft Enterprise

You must have the following software installed before you can continue with the installation of Microsoft BizTalk Adapter for PeopleSoft Enterprise. Install the software in the order listed:

BizTalk Server 2013 R2 BizTalk Server 2013
  • Windows 8.1

  • Windows 7 SP1

  • Windows Server 2012

  • Windows Server 2012 R2

  • Windows 8

  • Windows 7 SP1

  • Windows Server 2012

  • Windows Server 2008 R2 SP1

BizTalk Server 2013 R2

BizTalk Server 2013

Sun Systems Java Development Kit (JDK)

Sun Systems Java Development Kit (JDK)

PeopleSoft:

  • Tools Release

  • Applications Release

Supported Line-of-Business (LOB) and Enterprise systems lists the supported versions.

PeopleSoft:

  • Tools Release

  • Applications Release

Supported Line-of-Business (LOB) and Enterprise systems lists the supported versions.

BizTalk Adapter for PeopleSoft Enterprise requires a modification to the PeopleSoft application. To use component interfaces, you must upload a custom component interface, GET_CI_INFO, into PeopleSoft. GET_CI_INFO.pc is located in Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\PeopleSoft Enterprise(r)\Config\.

BizTalk Adapter for PeopleSoft Enterprise requires a modification to the PeopleSoft application. To use component interfaces, you must upload a custom component interface, GET_CI_INFO, into PeopleSoft. GET_CI_INFO.pc is located in Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\PeopleSoft Enterprise(r)\Config\.

Receive Handler PeopleSoft Requirements

The PeopleSoft Integration Broker must be able to communicate with BizTalk Server. The following could have already occurred in an existing PeopleSoft environment and you could reuse an existing node; therefore, you would not have to do anything except obtain the HTTP specifications from a PeopleSoft System Administrator. For detailed information, refer to PeopleSoft documentation.

These are the basic steps that you must follow in PeopleSoft:

  1. Set up the message and make it active through the Application Designer.

  2. Make a one-time change to the PeopleSoft integration.gateway.properties file.

  3. Create and configure the gateway and nodes to activate HTTP.

    • The node must be using some triggering method, for example, the LOCATION_SYNC mechanism.

    • The node must use HTTP.

    • The node must point to the host and port to which you are sending the event.

Send Handler PeopleSoft Requirements

BizTalk Adapter for PeopleSoft Enterprise consists of a custom component interface (CI) that provides access through a Java API. A custom CI object, GET_CI_INFO, is deployed in the PeopleSoft system using PeopleSoft Tools, to provide metadata information that is required by BizTalk Adapter for PeopleSoft Enterprise. For more information, refer to PeopleSoft documentation.

Uploading of the custom component interface is a one-time occurrence. This file, GET_CI_INFO.pc, is provided with the product and must be installed in the PeopleSoft system before you can use the adapter to browse CIs. You must have access to the PeopleSoft Application Designer; however, the Application Designer does not have to be anywhere near the BizTalk Server computer. You use the Application Designer to upload the custom CI into the PeopleSoft computer that you will browse.

You must have access to the PeopleSoft computer because you must set the environment variable CLASSPATH (or set the information in the Transport Properties window) to point to the PeopleSoft PSJOA/psjoa.jar file.

Preparing to Use PeopleSoft

This section discusses how to set up PeopleSoft for use with Microsoft BizTalk Adapter for PeopleSoft Enterprise.

For more information about PeopleSoft, see the PeopleSoft documentation.

Setting Environment Variables

Updating JAVA_HOME

Set the JAVA_HOME variable to point to your JDK installation, for example:

set JAVA_HOME=C:\j2sdk1.4.2_06

Updating CLASSPATH

To use component interfaces (PeopleSoft 8 only) you must update your CLASSPATH to include the PeopleSoft component interface jar file.

To update the CLASSPATH:

  1. In Control Panel, open System.

  2. On the Advanced tab, click Environment Variables, and then select CLASSPATH.

  3. Add the path, for example:

    <PeopleSoft_Home>\web\PSJOA\psjoa.jar

BizTalk Adapter for PeopleSoft Enterprise requires the psjoa.jar file. This is performed when you create a send port. For more information, see "Setting Transport Properties in PeopleSoft System" in the adapter documentation.

Note

Only have one of these directories in your PATH to make sure that BizTalk Adapter for PeopleSoft Enterprise picks up the correct DLLs. Failure to set up your environment correctly for the desired version of PeopleSoft could lead to errors that are difficult to trace.

Using Component Interfaces

Uploading a Custom CI into PeopleSoft

BizTalk Adapter for PeopleSoft Enterprise requires a modification to the PeopleSoft application. To use component interfaces, you must upload a custom component interface, GET_CI_INFO, into PeopleSoft. You only have to import GET_CI_INFO during initial setup to use the adapter. The adapter uses GET_CI_INFO to obtain information about other existing component interfaces in PeopleSoft.

This section explains how to manually import a custom component interface that will let you browse component interfaces in PeopleSoft. Note that the custom methods do not use or modify any properties of the component interface that it is installed in. To import the custom component interface, you can use one of the following methods:

  • Create a new component to import the custom methods.

  • Use an existing component that contains no keys, for example, INSTALLATION_RS.

The simple component interface must not contain keys. If you are not sure whether a particular component interface contains keys, you can run this 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.

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))

You can follow PeopleSoft documentation to create a unique simple component for storing BizTalk Adapter for PeopleSoft Enterprise custom methods. You can also clone one of the pre-existing component interfaces and use it to store the custom methods.

To verify that your GET_CI_INFO has no keys, run the PeopleTools Application Designer Component Interface Test tool.

Creating a New Component Interface

Follow these steps to create a new component interface using the PeopleSoft, Application Designer.

To create a component interface

  1. Open the PeopleSoft Application Designer.

  2. Enter a three-tier connection type, and then click OK.

    For example, select Application Server from the list.

  3. In the Application Designer, on the File menu, select New.

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

  5. Click Select.

  6. From the list of all components, select any simple component.

    For example, select INSTALLATION_RS, or a new PeopleSoft component that you created.

The custom methods do not use or modify any properties of the component interface that it is installed in.

This simple component interface must not contain keys. If you are not sure whether a particular component interface contains keys, you can run this 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:

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.

To verify that your GET_CI_INFO has no keys, run the PeopleTools Application Designer Component Interface Test tool.

Checking Component Interface

You have completed uploading the Microsoft 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 using the Microsoft Adapter Wizard. You can locate and expand GET_CI_INFO to view its user-defined methods.

Note

For more information about user-defined methods, see "PeopleSoft: Component Interface User-Defined Methods" in the adapter documentation.

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.

  • 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
  1. Point to PeopleTools, point to Security, point to Permissions & Roles, and then select Permission Lists.

  2. In the Maintain Security window, click Search, select the relevant Permission List, and then click the appropriate list hyperlink.

  3. In the Permission List pane on the right, click the right arrow next to the Sign-on Times tab to display the Component Interfaces tab.

  4. Click the Component Interfaces tab.

  5. Click the plus sign (+) to add a new row to the Component Interfaces list.

  6. Select the GET_CI_INFO component interface, and then click Edit.

  7. To set the methods to Full Access, click Full Access (All), and then click OK.

  8. Scroll to the bottom of the Component Interfaces window, and then 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

  1. Start the PeopleSoft Application Designer.

  2. On the File menu, point to Open, and then select Definition = Component Interface.

  3. From the list of component interfaces, select GET_CI_INFO CI.

  4. 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.

Top of page

Requirements for BizTalk Adapter for TIBCO Rendezvous

Microsoft BizTalk Adapter for TIBCO Rendezvous requires the following:

BizTalk Server 2013 R2 BizTalk Server 2013
  • Windows 8.1

  • Windows 7 SP1

  • Windows Server 2012

  • Windows Server 2012 R2

  • Windows 8

  • Windows 7 SP1

  • Windows Server 2012

  • Windows Server 2008 R2 SP1

TIBCO Rendezvous

Supported Line-of-Business (LOB) and Enterprise systems lists the supported versions.

TIBCO Rendezvous

Supported Line-of-Business (LOB) and Enterprise systems lists the supported versions.

Additional 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 executable.

Top of page

Requirements for BizTalk Adapter for TIBCO Enterprise Message Service

Microsoft BizTalk Adapter for TIBCO Enterprise Message Service requires the following:

BizTalk Server 2013 R2 BizTalk Server 2013
  • Windows 8.1

  • Windows 7 SP1

  • Windows Server 2012

  • Windows Server 2012 R2

  • Windows 8

  • Windows 7 SP1

  • Windows Server 2012

  • Windows Server 2008 R2 SP1

TIBCO EMS

Supported Line-of-Business (LOB) and Enterprise systems lists the supported versions.

TIBCO EMS

Supported Line-of-Business (LOB) and Enterprise systems lists the supported versions.

Enterprise Message Service (EMS) version 5.x and above includes a client SDK (using the TIBCO EMS C# API). BizTalk Adapter for TIBCO EMS uses this to communicate with the Server.

Top of page

Installing BizTalk Adapters for Enterprise Applications

Before running the Microsoft BizTalk Adapters for Enterprise Applications installation program, make sure that you install Microsoft BizTalk Server and all the software prerequisites for the adapters that you want to install. It is recommended that you close all applications before running Setup.

To install Microsoft BizTalk Adapters for Enterprise Applications

  1. From the BizTalk Server installation media, run Setup.exe. From the splash screen, click Install Microsoft BizTalk Adapters. From the next splash screen, click Install Microsoft BizTalk Adapters for Enterprise Applications.

    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.

  2. On the Introduction page, click Next to continue.

    The License Agreement appears.

  3. Click Next after you read and accept the license agreement.

    • If you select No, the installation program removes the extracted files and closes.

    • If you select Yes, the installation program prompts you to enter your customer information.

  4. Enter the user name and organization on the Customer Information page, and then click Next.

    The Setup Type page appears.

  5. Select how you want to install Microsoft BizTalk Adapters for Enterprise Applications: 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 run time.

    • Custom: lets you choose the adapters and features that you want to install and where they will be installed.

    To set the destination, click Browse and set the installation path.

  6. Click Next to continue.

  7. Click Install on the Ready to Install page.

    BizTalk Adapters for Enterprise Applications loads files to your selected location.

  8. On the Install Complete page, click Finish.

Important
  • You might encounter the following error during installation:
  • Error 1609. An error occurred while applying security settings. CREATOR OWNER is not a valid user or group
  • To work around this error, perform the following steps and run the installation again:
    • Create a new user called CREATOR OWNER (Type this command on the command prompt – net user "CREATOR OWNER" /add)

    • Create a new group called Users (Type this command on the command prompt – net localgroup Users /add)

For information about how to add the adapters to BizTalk Server, see the section, Adding the BizTalk Adapters for Enterprise Applications to BizTalk Server.

Top of page

Installation Information for BizTalk Adapter for JD Edwards OneWorld

Microsoft BizTalk Adapter for JD Edwards OneWorld consists of a transmit adapter that interfaces supported databases and server systems to Microsoft BizTalk Server. The transmit adapter enables you to invoke a server system's call from BizTalk Server. The transmit adapter (the BizTalk Server Administration Send Handler) configuration specifies the location of the SQL database.

See the adapter documentation for information about how to use BizTalk Adapter for JD Edwards OneWorld and about the mapping between its model and the BizTalk Server model.

Single Sign-On

BizTalk Adapter for JD Edwards OneWorld provides support for Enterprise Single Sign-On (SSO). If you select to use SSO in the Transport Properties page, the credentials for the affiliate application in the SSO Credentials database are used. An affiliate application represents an application—a back-end that requires credentials.

Installed Components

As BizTalk Adapter for JD Edwards OneWorld finishes its installation, it registers its components in the global assembly cache (GAC) by gacutil.exe. This is required by the Microsoft .NET Framework. You can verify the registration in the GAC by viewing the assembly folder in your explorer; for example, <%WINDIR%>\assembly, or use gacutil /l.

  • 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

The following GAC entry is installed and deployed by btsTask.exe for the adapter. The BizTalk Server Deployment Log results are located in \Program Files\Microsoft BizTalk Adapters for Enterprise Applications\jdeDeploy.html and jdeDeploy.xml:

  • Microsoft.BizTalk.Adapters.JDEProperties.dll

    Adapter-specific files are installed in Program Files and Program Files\Common Files.

The following files are installed in Program Files\Microsoft BizTalk Adapters for Enterprise Applications\ J.D. Edwards OneWorld(r)

  • sdk\

Program Files\ Microsoft BizTalk Adapters for Enterprise Applications\JD Edwards OneWorld(r)\ contains the following files:

  • classes\JDEJAccess.jar

  • Config\ J.D. Edwards OneWorld(r) \BTSREL.exe

  • Config\ J.D. Edwards OneWorld(r) \jdearglist.txt

  • Config\ J.D. Edwards OneWorld(r) \jdeinterop.ini

Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\Bin\ contains the following files:

  • Microsoft.BizTalk.Adapters.JDEProperties.dll

  • jdecba.dll

Top of page

Installation Information for BizTalk Adapter for JD Edwards EnterpriseOne

Microsoft BizTalk Adapter for JD Edwards EnterpriseOne contains a transmit adapter that interfaces with supported databases and server systems to BizTalk Server. The transmit adapter enables you to invoke a server system’s call from BizTalk Server.

BizTalk Adapter for JD Edwards EnterpriseOne provides support for Enterprise Single Sign-On (SSO). If you select to use SSO in the Transport Properties page, the credentials for the affiliate application in the SSO Credentials database are used. An affiliate application represents an application—a back-end that requires credentials.

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

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\J.D. Edwards EnterpriseOne(r).

  • 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.

Top of page

Installation Information for BizTalk Adapter for PeopleSoft Enterprise

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

BizTalk Adapter for PeopleSoft Enterprise provides support for Enterprise Single Sign-On (SSO). If you select to use SSO in the Transport Properties page, the credentials for the affiliate application in the SSO Credentials database are used. An affiliate application represents an application—a back-end that requires credentials.

The adapter installation includes samples in the \sdk directory.

Installed Components

As BizTalk Adapter for PeopleSoft Enterprise finishes its installation, components are registered in the GAC by gacutil.exe. This is required by the .NET Framework. You can verify the registration in the GAC by viewing the assembly folder in Windows Explorer; for example, <%WINDIR%>\assembly, or use gacutil /l.

  • Microsoft.BizTalk.Adapters.BizUtil.dll

  • Microsoft.BizTalk.Adapters.CoreManagement.dll

  • Microsoft.BizTalk.Adapters.CoreReceiver.dll

  • Microsoft.BizTalk.Adapters.CoreTransmitter.dll

Adapter-specific files are installed in Program Files and Program Files\Common Files.

The following files are installed in Program Files\Microsoft BizTalk Adapters for Enterprise Applications\PeopleSoft Enterprise (r)

  • bin\BTAPeopleSoftTrace.cmd

  • config\btaPeopleSoftTrace.mof

  • config\GET_CI_INFO.pc

  • config\GET_CI_INFO.pc

  • sdk\

The folder Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications contains the following files:

  • bin\psosa.dll

  • bin\Microsoft.BizTalk.Adapters.CoreManagement.dll

  • bin\Microsoft.BizTalk.Adapters.CoreReceiver.dll

  • bin\Microsoft.BizTalk.Adapters.CoreTransmitter.dll

Top of page

Installation Information for BizTalk Adapter for TIBCO Rendezvous

Microsoft BizTalk Adapter for TIBCO Rendezvous contains receive and transmit functionality that interface with 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.

See the adapter documentation for information about how to use Microsoft BizTalk Adapter for TIBCO Rendezvous and about the mapping between its model and the BizTalk Server model.

Installed Components

As BizTalk Adapter for TIBCO Rendezvous finishes its installation, it registers its components in the GAC using gacutil.exe. This is required by the .NET Framework. You can verify the registration in the GAC by viewing the assembly folder in your explorer; for example: <%WINDIR%>\assembly or use gacutil /l.

  • Microsoft.BizTalk.Adapters.TibcoRV

  • Microsoft.BizTalk.Adapters.TibcoRV.Common

  • Microsoft.BizTalk.Adapters.TibcoRV.Service

  • Microsoft.BizTalk.Adapters.TibRV.Properties

  • Microsoft.BizTalk.Adapters.TibcoEMS

  • Microsoft.BizTalk.Adapters.TibcoEMS.Properties

  • Microsoft.BizTalk.Adapters.TibcoRVManagement

  • Microsoft.BizTalk.Adapters.TibcoRVReceiver

  • Microsoft.BizTalk.Adapters.TibcoRVTransmitter

Adapter-specific files are installed in Program Files and Program Files\Common Files. The following files are installed in Program Files\Microsoft BizTalk Adapters for Enterprise Applications\ TIBCO(r) Rendezvous(r).

  • 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.CoreManagement.dll

  • bin\Microsoft.BizTalk.Adapters.CoreReceiver.dll

  • bin\Microsoft.BizTalk.Adapters.CoreTransmitter.dll

  • bin\Microsoft.BizTalk.Adapters.TibRV.Properties.dll

  • Config\btaTibcoRVTrace.mof

  • sdk\

The folder Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications contains the following files:

  • bin\tibcorvcba.dll

  • Microsoft.BizTalk.Adapters.CoreManagement.dll

  • Microsoft.BizTalk.Adapters.CoreReceiver.dll

  • Microsoft.BizTalk.Adapters.CoreTransmitter.dll

Adding TIBCO.Rendezvous.dll to the GAC

BizTalk Adapter for TIBCO Rendezvous requires “TIBCO.Rendezvous.dll”.The minimum version that is required is FileVersion: 1.0.3036.23330,  which is shipped with the product version 8.1. The adapter triggers an exception and logs an appropriate message if this assembly is not installed.

You must use late binding to load assemblies so that the TIBCO Rendezvous assemblies do not fail when a particular version of the TIBCO.Rendezvous.dll and TIBCO.Rendezvous.net module are not present on the target computer..

Runtime Component

Verify you have the TIBCO Rendezvous Runtime Component installed on your computer. The Runtime Component is the only component that you must install when you install TIBCO Rendezvous.

At a Visual Studio command prompt, change directories to the location of the TIBCO.Rendezvous.dll file. The path of this DLL in the default installation of TIBCO Rendezvous is C:\TIBCO\TIBRV\BIN\TIBCO.Rendezvous.dll.

At the command prompt, type the following:

C:\TIBCO\TIBRV\BIN > gacutil /i TIBCO.Rendezvous.dll

The TIBCO.Rendezvous.dll now shows GAC list. To view the list, in Control Panel, open Administrator Tools, open Microsoft .NET Framework Configuration, and then open Assembly Cache.

Top of page

Installation Information for BizTalk Adapter for TIBCO Enterprise Message Service

Microsoft BizTalk Adapter for TIBCO Enterprise Message Service (EMS) contains receive and transmit functionality that interface with 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.

See the adapter documentation for information about how to use BizTalk Adapter for TIBCO EMS and about the mapping between its model and the BizTalk Server model.

Installed Components

As BizTalk Adapter for TIBCO Enterprise Message Service finishes its installation, it registers its components in the GAC using gacutil.exe. This is required by the .NET Framework. You can verify the registration in the GAC by viewing the assembly folder in your explorer; for example: <%WINDIR%>\assembly or use gacutil /l.

  • Microsoft.BizTalk.Adapters.TibcoEMS.dll

Adapter-specific files are installed in Program Files and Program Files\Common Files. The following files are installed under Program Files\Microsoft BizTalk Adapters for Enterprise Applications\ TIBCO(r) Enterprise Message Service(TM).

  • bin\BTATibcoEMSTrace.cmd

  • Microsoft.BizTalk.Adapters.TibcoEMS.dll

  • Config\btaTibcoEMSTrace.mof

  • sdk\

The folder Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\bin contains the following files:

  • Microsoft.BizTalk.Adapters.CoreManagement.dll

  • Microsoft.BizTalk.Adapters.CoreReceiver.dll

  • Microsoft.BizTalk.Adapters.CoreTransmitter.dll

    Note

    You must use late binding to load assemblies so that the TIBCO EMS assemblies do not fail when a particular version of the TIBCO.EMS.dll is not present on the target computer. For instructions about how to use late bindings, see http://go.microsoft.com/fwlink/?LinkID=63509 and http://go.microsoft.com/fwlink/?LinkId=63512.

Adding TIBCO.EMS.dll API to the GAC

BizTalk Adapter for TIBCO EMS requires that you add the TIBCO.EMS.dll to the GAC. BizTalk Adapter for TIBCO EMS triggers an exception and logs an appropriate message if this assembly is not installed.

To add TIBCO EMS C# API to GAC

  1. Copy the TIBCO EMS C#API to your BizTalk computer.

  2. At a Visual Studio command prompt, change directories to the location of the C# API file.

  3. In a Visual Studio command prompt, type the following:

    C:\<TIBCO EMS Folder>bin> gacutil /i TIBCO.EMS.dll

The TIBCO.EMS.dll now shows in the C:\Windows\assembly listing. Or, in Control Panel, open Administrator Tools, open Microsoft .NET Framework, and open Assembly Cache to view the GAC list.

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:

  1. Message compression, which enables the TIBCO EMS client to send messages in a compressed form to EMS, is not available.

  2. 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 but the Adapters support the SLL with Tibco.EMS.dll with ProductVersion 5.0 and above.

  3. Administration API for EMS is not supported.

Top of page

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 Using Windows Trace Event.

Trace files install in \Program Files\Microsoft BizTalk Adapters for Enterprise Applications\.

  • bin\BTATrace.cmd

  • config\btaTrace.mof

Top of page

Using Windows Trace Event

The adapters log error, warning, and information messages to the 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 makes sure 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 Microsoft SDK 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:

BTAXXXTrace -transmitter -start -cir 10 -rt c:\log\mylog.etl
BTAXXXTrace -transmitter -stop
Note

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

Top of page

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.

Note

If you install BizTalk in a multicomputer environment (runtime-only installation on one computer and an administration tools-only installation on another computer), you should install the BizTalk Adapters for Enterprise Applications on both the computers.

To add Microsoft BizTalk Adapters for Enterprise Applications

  1. Start the BizTalk Server Administration Console.

  2. Expand Microsoft BizTalk Server, and then expand Platform Settings.

  3. Right-click Adapters, point to New, and then select Adapter.

  4. Type a name, for example, PeopleSoft.

  5. Select the name, in this example, PeopleSoft, from the Adapter list.

  6. Click OK.

Top of page

Copyright

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.

© 2013 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, BizTalk, IntelliSense, JScript, MSDN, Visual Basic, Visual C#, Visual C++, Visual Studio, Win32, Windows, Windows Server, Windows Server System, and Windows Vista are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.

Top of page