Table of Contents
When first trying to learn about the deployment of a composite application, it is important to understand the role of links to components in composite applications.
Composite applications are basically definitions of applications with lists of links to the internal components as well as some wiring properties shared between them. In order to deploy a composite application, the composite application definition as well as various application artifacts have to be deployed along with the actual components which make up the application. This makes it important that you understand how the various links to application components work.
Composite applications are usually not deployed by the developers but by someone such as a system administrator. In some cases, a system administrator may have questions about what kind of components make up the composite application being deployed. This information is useful in helping to decide the correct application deployment method.
To find out what types of components are in a composite application you can do two things:
- Export the CA XML from the composite application via Domino Designer and look at the contents OR
- Open the composite application in the Composite Application Editor and read the Advanced Component Properties of the components.
With either approach you have to read the internals of the component properties. If there is a "com.ibm.notes.notesurl" property, then it is a Notes component. If there is a "url.feature property," then it is an Eclipse component. The first uses the Notes: url format, the second uses a nrpc: url format. For more information about these URLs read the sections that follow.
In a composite application, you can refer to NSF components and Eclipse either via static or dynamic links. The following sections describe how these static and dynamic links are handled.
Table of Contents