Libraries in Websphere Integration Developer
A library can deploy in server in two ways.
1. Deployinh libraries in modules (default setting)
-- A copy of the library JAR file is included in each module that uses it.
-- After deployment, if changes in library resources than modules using that library must be updated and redeployed.
2. Deploying libraries globally( memory save by this option)
-- Library is deployed as a delpoyable JAR file.
-- The resources references for a module are configured to use the global library using the module deployment editor
-- this option saves memory but you mush deploy each library independently.
- Libraries are projects used to store shared resources by several modules
- Libraries are accessed by adding them to module dependencies.
- Libraries are not runnable applications. It has no assemble diagram.
- Library projects do not include other types of business integration resources such as SCA components.
- Dependencies -- Used to include other libraries,projects, predefined resources.
- Integration Logic -- Contains artifacts theat perform business services(mediation subflows,Business calender)
- Data -- Business Objects.
- Intefaces -- Service interfaces and it's operations.
- Transformations - Contains data maps and relationships
A library can deploy in server in two ways.
1. Deployinh libraries in modules (default setting)
-- A copy of the library JAR file is included in each module that uses it.
-- After deployment, if changes in library resources than modules using that library must be updated and redeployed.
2. Deploying libraries globally( memory save by this option)
-- Library is deployed as a delpoyable JAR file.
-- The resources references for a module are configured to use the global library using the module deployment editor
-- this option saves memory but you mush deploy each library independently.
