| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: Relaunching OTDs |
|
Creating a Runtime Environment
Designing Business Processes in the Sun Business Process Manager
Working with TCP/IP HL7 Collaborations
Developing Sun Master Indexes (Repository)
Developing Sun Master Patient Indexes
Developing OTDs for Application Adapters
Date and Time Stamp Requirements
Creating a SAP ALE OTDs Wizard
SAP JCo and SAP IDoc Class Library Installation
Exporting the IDOC File from SAP
Saving the IDoc Description File (After 4.6)
Creating an Oracle Applications OTD
Select Oracle Applications Module
Exposed Oracle Applications OTD Nodes
SWIFT Alliance Gateway Adapter OTD Features
Generating DTDs from PeopleTools 8.13
Generating and Publishing an XML Test Message
To generate a PeopleSoft XML message
Extracting and Viewing the XML Test Message
Generating a DTD for the XML File
OTD Methods and Business Process Operations
Developing OTDs for Communication Adapters
Developing OTDs for Database Adapters
Developing OTDs for Web Server Adapters
Designing with Application Adapters
Designing with Communication Adapters
Designing with Web Server Adapters
Designing with Sun JCA Adapters
A single OTD can consist of many lines of metadata. When a change to the metadata occurs in an OTD, it does not have to be recreated from scratch. Using the Relaunch function allows the OTD to be rebuilt and saved under the same name, then relaunched back to the same Java Collaboration Definition (JCD) or Business Process Execution Language (BPEL).
Note - The File Name must be identical to the original since the name is used to generate the OTD name.
When relaunching an OTD, an existing collaboration will not be affected if:
New columns are added
Deleted columns are not used in the original collaboration
Note - Validation will fail if existing collaborations are not modified when columns are renamed or deleted.