IBM E02HMLL-I Implementation Guide - Page 106

Dependencies that cannot be detected by the system There are some dependency and reference relationships that cannot be automatically detected and enforced by the system. Table 9 describes the components for which the system cannot determine dependencies and references. Although the system is unable to detect these dependencies and references, they must still be satisfied for the system to operate properly. You must maintain accurate project documentation to make sure that when you deploy an interface from one environment to another you include any of these extra dependencies. Table 9. Components for which the system cannot determine dependencies and references Component Explanation Relationships Maps and collaboration templates can use relationships, but they do so through APIs in Java code. The system cannot parse all the code in all maps and collaboration templates to detect the use of relationships. Database connection pools Maps and collaboration templates can use database connection pools, but they do so through APIs in Java code. The system cannot parse all the code in all maps and collaboration templates to detect the use of database connection pools. Data handlers Connectors, as well as other components, can use data handlers to format data. Data handlers are not managed by the system at all, and it therefore cannot detect them. any component used exclusively in code Although the system can determine that a map depends upon a business object when you have drag-and-dropped the business object definition into the map as a source or destination, it cannot detect any use of components that occurs exclusively through custom Java code. If you instantiate a new business object or manually invoke a map in a map or collaboration, the system is not able to detect that dependency. Schedules The system does not currently support the detection of dependencies and references for schedules. Standard operations available for multiple workbench resources Although many of the tasks you perform in the workbench are sensitive to the particular resource you are working with or the context in which you are working, there are many operations that affect all resources the same way. This section describes the tasks you can perform in the workbench that work similarly for all resources. Cutting, copying, and pasting resources You can cut, copy, and paste resources both in System Manager and in the file system. To cut, copy, or paste a user project, integration component library, integration component, shortcut, or folder in System Manager, right-click the resource and choose the desired menu item. If you copy integration components, you cannot paste them into the same library (for instance, to copy a business object definition and paste it into the same library to specify a different name and use it as a template). You can, however, open the component definition in its designer tool and do a "Save as" operation to save it with a new name to the same library. 94 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation Guide