ShowTable of Contents
The following information provides steps and guidelines for deploying a basic composite application. This topic is divided into the following sections:
- Preliminary application preparation and definition
- Initially deploying your application
- Deploying an update to your application
For these procedures, there should be two servers configured in the environment. The servers should not be connected via replication connection records as this will mirror a development and production environment. There should also be two client machines involved - a production client and a development client.
Preliminary application preparation and definition
In the process of getting a composite application ready for a basic deployment as described in this topic, it first needs to be in a Notes template.
In addition, carry out the following preparation steps:
Create a profile document
In your composite application, use the following command pattern for the preference com.ibm.notes.ComputedNotesURL:
The preference com.ibm.notes.ComputedNotesURL contains a Notes @function that is used to set the NotesURL. As an example, take the following command:
In the example, a profile document exists in the Notes Database that contains the composite application. This profile document form name is CAProfile and it contains a field MyComponentKey with the value to be used for the Notes URL.
To create the CAProfile profile document form in your composite application with Domino Designer, use the following steps:
1. Create a new form in the composite application database and name it "CAProfile"
2. Create a field on the form for each URL that you will need to store. Say, for example, that your application database has two Notes components, a navigator and a banner. You would create two fields named "Navigator" and "Banner."
3. Deselect the Display options in the Form properties.
4. Save the form.
Create an agent to edit the form
You now create an agent to edit the form. The formula for this is the following (using the example form name):
@Command( [EditProfileDocument] ; "CAProfile" );
In the agent Properties box, set the Target to "None."
Open the application as a database
Use the following steps:
1. In Notes, use Ctrl-O to launch the Open Database dialog box.
2. Select the database
3. Hold down the Ctrl and Alt keys as you click OK
This causes the database not to open as a composite application as a regular NSF.
Run the CAProfile action
You now run the CAProfile action. Use the following steps:
1. From Notes, select Action-Edit CA Profile.
2. Copy in the URL for each component.
Update the Application to use the profiles
Use the following steps to update the application to use the profiles:
1. Close the application
2. Open the application as a composite application using the Composite Application Editor.
3. Select Advanced Properties for each of the Notes components.
4. Add a new property named com.ibm.notes.ComputedNotesURL and provide it with a value.
For this example, use the following: @GetProfileField("CAProfile";"Navigator")
5. Delete the original notes URL property in the application.
The next section describes hwo to initially deploy your application.
Initially deploying your application
The following is a step matrix for deploying your composite application to a production server.
Create your Eclipse Update Site
1 Create a new NSF based on the Eclipse update site.ntf
2 Import your Features into the update site
3 Create a replica copy of your NSF on your development server
Create your composite application
1 Create your application using the "Blank Composite Application"
2 Construct your application using CAE and Designer
3 Reference your features to the update site NSF database by using its replica-id
4 Use the @Command and profile document pattern to change NSF based references
5 Save the application as a template - template1.ntf
6 Create a new CA off of template1.ntf - devapp.nsf
7 Copy the database to the development server and test it
Deployment Instructions to Production
1 Send copy of template1.ntf to administrator
2 Create new application from template1.ntf - ca-app1.nsf
3 Create a new update site NSF on production server from the NSF Update site template
4 Import the features from development update site - usually an Eclipse HTTP or file based update site
5 Create a new profile document to point to the production NSF URL for those components that use it
6 Change the CA XML to point to the production NSF update site - all feature URL's must reference the production replica ID.
7 Using a client open the vodafone contact number application
Deploying an update to your application
In some scenarios you may wish to update or upgrade your composite application. These scenarios can include the following:
Upgrading a notes database that is a component of a app
Upgrading a notes database with a change of WSDL
Upgrading an Eclipse Component
Upgrading an Eclipse Component with a change of WSDL
This update assumes you have modified all artifacts of you application - ca xml, wsdl's, and feature numbers
Update your Eclipse Update Site
1 Modify your features and plugins - you need to bump up the version numbers if you want them to be upgraded on the client machines.
2 Update the development eclipse update site with the new eclipse features.
* do this by loading the features from your Eclipse update site
Update your application
1 Modify the template1.nsf in Designer, CAE, and PBE
2 Replace the design of your development application - devapp.nsf with template1.nsf
3 Update the version numbers of the components
- update the individual component or text search and replace the ca xml.
4 Using the development client, open the application on the development server and test it.
- You must verify that the WSDL, Pages, and new features are installed.
1- New features are installed
2- WSDL changes have taken
3- CA XML changes have taken
4 - Verify removal of components
5 - Verify the Notes components are changed
Deploy your update site changes to production
1 Import the new eclipse update site into the NSF based update site
- the new site should have the newly modified features with the new version numbers
Deploy your application to production
1 Put the new template on the production server
2 Replace the design of the production app (ca-app1.nsf) with the new template
3 Update the featured URL to point to the production eclipse site database - all feature URL's must reference the production replica ID.
4 Update the profile documents to the production URL's
5 Using the production client - open the application on the production server
1 - Application runs
2- New features are installed
3- WSDL changes have taken
4- CA XML changes have taken
5 - Verify the Notes components are changed