After developing and testing a module, you must export the module from a test system and bring it into a production environment for deployment. To install an application you also should be aware of the paths needed when exporting the module and any libraries the module requires.
The component folder should be named module-name with a file in it named module.module, the base module.
For ease of use, name the subfolder similar to module/component.
The component files contain the definitions for each individual component within the module.
In this step you ensure that any references to artifacts required by a component are available. Names for components should not conflict with the names the serviceDeploy command uses for staging modules. See Naming conventions for staging modules.
The references file defines the references and the interfaces within the module.
The wires file completes the connections between the references and the interfaces within the module.
The manifest lists the module and all the components that comprise the module. It also contains a classpath statement so that the serviceDeploy command can locate any other modules needed by the module.
The following example illustrates the directory structure for the module MyValueModule, which is made up of the components MyValue, CustomerInfo, and StockQuote.
MyValueModule MyValueModule.manifest MyValueModule.references MyValueModule.wiring MyValueClient.jsp process/myvalue MyValue.component MyValue.java MyValueImpl.java service/customerinfo CustomerInfo.component CustomerInfo.java Customer.java CustomerInfoImpl.java service/stockquote StockQuote.component StockQuote.java StockQuoteAsynch.java StockQuoteCallback.java StockQuoteImpl.java
Last updated: Tue Feb 21 17:40:17 2006
(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)