Creating a Deployment Profile

Before creating a Deployment Profile, you must have created an appropriate runtime Environment to support the Project.

Note - If the Project includes web services, then each of a Project’s active Deployment Profiles must target a separate SOAP/HTTP External System; otherwise, the web containers can cause duplicate servlet names to appear in the domain.

Note - Deployment Profile names should contain only alphanumeric characters (letters and numbers), dashes, and underscores.

To create a Deployment Profile

1. In the NetBeans Project window, right-click on the Project to display its context menu.
2. From the menu, select New > Deployment Profile to display the Create Deployment Profile dialog.
3. Enter the Deployment Profile Name you want to use (or accept the default).

   Note - The resulting application ( .ear ) file will default to a concatenation of the Deployment Profile name and the Project name (see Naming the Application File).

4. Select the Environment to which you want to deploy the Project.
5. Select the Connectivity Map(s) to include in the deployment.
6. The Deployment Profile Editor now appears, showing all deployable Project components.
7. Drag the Project components from the left panel and drop them into the appropriate Environment components in the right panel.

   • Drag the topics and queues to the appropriate message server, being careful not to split inbound and outbound message destinations between separate servers.

   • Drag the Collaborations to the appropriate application servers.

   • Drag the Adapter components to the appropriate external systems.

   Note - You can select multiple components of the same type that are destined for a single external system, dragging them to that external system in one operation.

8. When the Environment components are fully populated, the left panel will be blank. You should now Save the profile.

   Note - You can deploy two services that are not directly dependent upon each other across two domains; however, two processes that need to have direct access to one another must be deployed to the same domain.