| 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
Developing OTDs for Communication Adapters
Using Regular Expressions With the Batch Adapter
Using Name Patterns With the Batch Adapter
Creating a New COM and DCOM OTD
Viewing an OTD Using the OTD Editor
Modifying an OTD Using the OTD Editor
SNA Object Type Definitions (OTDs)
To associate the standard SNA eWay OTD to a new Java Collaboration:
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 or BPEL.
The Select Files Wizard opens.
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.