After you create a target, you can add deployment configurations and change settings for the target from the property pages for the target. For information about deploying a JSP target, see Chapter 12, “Building and Deploying JSP Targets.”
Before you add a deployment configuration, you should decide whether you want to create a test (local) configuration, a shared or production (target) configuration, or both. You can deploy using both types of configuration at the same time.
Local configurations are stored in your registry, whereas target configurations are stored in the PBT file. PBT files with target configurations can be shared in a source control system, but users have to make certain that any configuration paths, database profiles, and target mappings have identical names on all machines that use the source-controlled target configurations.
You can add multiple deployment configurations to the list of local or target configuration profiles. You can change the order of the configurations in the list by using the wavy arrow keys above the configuration list boxes. A check box next to each deployment configuration in the list lets you select which of the configurations you want to use the next time you deploy your JSP target. When you add a configuration, it is selected for deployment by default.
To add deployment configurations:
Right-click the JSP target on the Workspace tab of the System Tree and select Properties from the pop-up menu.
Click the Deploy tab.
The Deploy page is one of three pages in the Properties dialog box for a JSP target.
Click the Create New Configuration button for either a local deployment configuration or a target deployment configuration.
The Name New Deployment Configuration wizard starts.
Follow the instructions in the Name New Deployment Configuration wizard. In the wizard, you provide the following information:
A name for the deployment configuration
Whether you are using the default object model or no object model
The JSP server to deploy to
If your JSP server is EAServer, the EAServer profile
If your JSP server is EAServer, the HTTP server name and port
How to handle failures (deploy all or nothing or only successful files)
A folder name for a local copy of the deployed files
The WAR file name
The JSP server can also be Tomcat or Command Line.
After you click Finish on the last wizard page, the new deployment configuration displays in one of the list boxes on the Deploy page of the Target Properties dialog box. You can use the toolbar above the list box to edit, delete, or change the order of the configurations in the list.
Click the Run tab and select a start page for your JSP target.
If you want to start your Web application from the design-time environment, you do not need the complete URL, but you can give the complete URL, including the server name, if you want to.
Select a deployment configuration that you want to use for running.
The deployment configurations you created for the current JSP target are available for selection from the Deploy Configuration For Running drop-down list.