Shared Resources
TIBCO Rendezvous
Rendezvous (RV) Configurations
The Rendezvous Configuration in the EAI software components has a constant name: ESIMaster_RVTransport.
Oracle Applications Adapter Subjects
<Domain>.<Deployment>.adorapps.MasterConfiguration.<API>.<ESIORADatasource>
The following describes the fields in this standard:
Field
Description
Domain
The BusinessWorks domain in use.
Deployment
The deployment name of the repository in use.
API
The API being used.
ESIORADatasource
The destination Oracle Applications system that the data is being published to.
Subject Standards
For example, a message being published to Oracle Applications to create a part with Deployment Production_Deployment, Domain masterDomain, Data Source VIS7:
masterDomain.Production_Deployment.adorapps.MasterConfiguration.Item.VIS7
EMS Application Properties & Configurations
The EMS Configuration for the EAI software components has a constant name: ESIMaster_EMSTransport.
EMS Queue Naming
EMS Queues Between Windchill and TIBCO
com.ptc.windchill.esi.<Identifier>
EMS queue names should be organized as a sequenced hierarchy, separated by periods (.), in increasing order of detail. All queue names should begin with the phrase "com" and end with some piece of information that identifies the specific data being transported. Words in each field should follow Windchill ESI Capitalization Notation.
The following are acceptable contents for the Identifier field:
Windchill
Identifier
Description
Event
The initial Event generated by Windchill.
DataRequest
The request for information sent to Windchill from TIBCO.
DataResponse
The response with business data to TIBCO from Windchill.
Result
The results of the transaction.
ResultResponse
The result of Windchill’s commitment of transaction information.
EMS Queues Identifiers
For example, a queue that carries the Windchill Event information should be called com.ptc.windchill.esi.Event.
JDBC Configurations
The JDBC Configuration for the EAI software components has a constant name: ESIMaster_JDBCTransport.
Schema Definitions
Schemas should be given the same name within BusinessWorks as their filename.
For example, the ESILog.xsd schema should be called ESILog.
Was this helpful?