This chapter provides suggested naming conventions for the files and
directories used in ODA development. Naming conventions provide a way
to make your ODA's code more easy to locate and identify. Table 63 summarizes the suggested naming conventions for an
ODA.
Table 63. Suggested naming conventions for an ODA
ODA name | ODA package and class name | ODA startup script | ODA library file | ODA runtime directory |
---|---|---|---|---|
srcDataNameODA |
com.ibm.oda.srcDataName.ODAname
| start_ODAname | ODAname.jar | ODA\srcDataName |
Each ODA should have a name that uniquely identifies it within the WebSphere business integration system. By convention, an ODA name (ODAname) takes the following form:
srcDataNameODA
where srcDataName is a unique string that identifies the source data that the ODA converts. For example, if an ODA converts HTML objects to business object definitions, its source data is in the HTML format. Therefore, its ODA name is HTMLODA. Alternatively, this ODA name can identify the adapter with which the ODA is associated. For example, the ODA that generates business object definitions for the WebSphere Business Integration Adapter for PeopleSoft has an ODA name of PeopleSoftODA.