Shared Resources
TIBCO Rendezvous
Rendezvous (RV) Configurations
The Rendezvous Configuration in the EAI software components has a constant name: ESIMaster_RVTransport
SAPAdapter Subjects
<Domain>.<Deployment>.<ESISAPAdapter/SystemID><ESISAPAdapter/Client>.< ESISAPAdapter/Locale>.<Configuration>
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.
Configuration
The object configuration name
API
The API being used
ESISAPAdapter/SystemID
The destination SAP system that the data is being published to.
ESISAPAdapter/Client
The destination SAP Client that the data is being published to.
ESISAPAdapter/Locale
The destination SAP locale that the data is being published to.
Subject Standards
For example, a message being published to SAP to create a part with Deployment Production_Deployment, Domain masterDomain, SystemID DV1, Client 850, and US locale would be called:
masterDomain.Production_Deployment. DV1850.en_USBAPI_MATERIAL_SAVEREPLICAServer
JMS Application Properties & Configurations
JMS Queue Naming
JMS Queues Between Windchill and TIBCO com.ptc.windchill.esi.<Identifier>
JMS 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:
Identifier
Description
DataResponse
The response with business data to TIBCO from Windchill.
Result
The results of the transaction.
JMS Queues Identifiers
Refer to the Interface Control Document for complete specifications of all JMS queues.
For example, a queue that carries the Windchill Result information should be called com.ptc.windchill.esi.Result.
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?