You create integration components in a library in your local file system and deploy them to an InterChange Server Express instance to make them executable. When components are deployed to the server, the server runtime is updated so they can be used immediately.
You can deploy a package of integration components using either the System Manager graphical interface or the repos_copy command-line interface. For information on using System Manager, see Deploying components using the deployment wizard. For information on using repos_copy, see Using repos_copy. For information on the advantages and disadvantages of each interface, see Deciding to use System Manager or repos_copy for deployment.
Table 6 describes the advantages and disadvantages of using System Manager or repos_copy for deployment. Evaluate the two interfaces and use whichever one is best suited to your needs.
Interface | Advantages | Disadvantages |
---|---|---|
System Manager |
|
|
repos_copy |
|
|
When you deploy a user project from System Manager to different servers, the configuration properties for some of the integration components may need to change for the new server environment. For example, an adapter in your solution may have properties that specify a database URL, a user name, and a password that are all valid for your development and testing server. But the production environment in which the solution will be deployed may require different values for these properties. Rather than manually reconfiguring the adapter (by manually using the connector configurator to change the connector configuration properties) --and other integration components that might require modification for the new environment--you can use the deployment configuration feature of System Manager.
The deployment configuration feature of System Manager enables you to define a set of values for certain integration component properties and make them applicable to a specific server (or servers) that you name. The values are stored in a deployment file (with the extension .dfg) associated with an Integration Component Library. When you deploy an existing user project to one of the servers that you listed in deployment configurator, System Manager uses the property values from the deployment file to modify the existing configuration files for the relevant components of the user project.
This feature can be used to modify the properties of connectors, maps, collaborations, and relationships.
To create and deploy properties using the deployment configuration feature, follow these steps:
To open the deployment configuration dialog, do this:
To add a server to the deployment file, in the Select the server section you must designate a name for a server that will use the deployment time properties that you are creating.
After you have selected or named a server, you must add the integration components, properties, and values that you want to apply for use with that server.
If you have previously added elements for one server, when you later add a new server in the Deployment Configuration dialog, it will automatically be populated with the elements previously created. You can then delete or modify the elements.
If you have not previously added configuration elements in the dialog for any server, you will need to add elements to the dialog for the first time. You can do so either by importing an existing deployment file (described later in this section) or by manually adding elements in the dialog. To manually add elements, position the cursor in the Property Name column, and right-click. The Components Selection dialog appears, displaying all the available integration components in the ICL that you right-clicked to open the Deployment Configuration dialog. Expand the categories as necessary. Then, for each individual component for which you want to configure properties, click the checkbox for the component, and choose OK. Do this in turn for each individual component. When you choose OK each time, the Components Selection dialog closes, and the Deployment Configuration dialog displays, showing the new component that you have added.
For each component that you add, you will need to also add the properties whose values you want to set for that component. To do so:
Now you need to specify the values that you want to use for these properties. To do so:
When you are done, click OK. The Deployment Configurator dialog closes. When you open the Deployment Configurator dialog again, the last configuration that you created will be displayed by default. If you have created more than one configuration (that is, if you have named more than one server in the Deployment Configuration dialog) you can display any of the other configurations by using the Please select destination server drop-down box.
After you have created a deployment configuration, the integration component properties and their values can be deployed to another server. After deployment, the property values you specified during deployment configuration will be applied to the component that went into the server. You can deploy to a server in either of the following ways:
If the server that you named in Deployment Configurator when you created the deployment configuration properties is a registered instance of InterChange Server Express, you can use System Manager to connect to and deploy your user project to that server, as described in Deploying components using System Manager
When you deploy the project, System Manager will use the deployment configuration property values to overwrite existing property values in the integration component's configuration, assuming that the System Manager preferences have been set for it to do so. Note that the original integration component definitions are not affected. The change occurs during deployment, when the values are modified in memory before being deployed to the server.
Check the System Manager preferences setting before you deploy. To check the setting, from within System Manager go to the Windows menu and open Preferences>System Manager Preferences>Deployment Preferences. In the Deployment Settings display, check or uncheck the box for Always apply Deployment configuration properties during deployment, depending on whether you want to use the deployment configuration properties.
When you use System Manager to deploy a user project, you can selectively choose the components in the user project that you want to deploy. The deployment configuration property values that you created will be applied only for the selected components.
Deployment configuration files are included within the package that is created when you export either user projects or individual ICLs to a repository package file, as described in Exporting components to a package using System Manager. When you do this for an ICL, any deployment configuration file (*.dfg file) that you created on that ICL will be included in the package. When you do this for a user project, the deployment configuration files that were created on any of the ICLs in the user project will be included in the package. If you selectively choose only certain components from an included ICL when you export the user project as a package, the deployment configuration file corresponding to that ICL will include properties and values for only those selected components.
You can export a file of deployment configuration properties, as described in Importing and exporting deployment time properties. This is especially useful if you are exporting a repository file package from an InterChange Server Express repository, as described in Chapter 6, "Using repos_copy," and you want to include deployment configuration properties. When you create a deployment configuration file, the file resides within System Manager, not within the InterChange Server Express repository. Consequently, when you use repos_copy to create a package from an InterChange Server Express repository, the deployment configuration file is not included. To add it, you can export the deployment configurator file using the Export Property Descriptor dialog, and then copy the configuration content into the repos_copy package file, using this syntax:
repos_copy -sserverName -uusername -ppassword -ireposcopyfile -ixdideploymentdescriptorfile
When you export an ICL or User Project from System Manager, the deployment descriptor.dfg file with the relevant entries will be included with the repository jar file. You can then use the repos_copy utility to repos copy the .jar file into the server. The values for the configuration file inside the .jar file will be automatically applied to the components before being deployed to the server.
If you do not want the transformations to happen, you can suppress them using the following option:
repos_copy -sserverName -uusername -ppassword -ireposcopyfile -xdn
The -xdn option ignores the .dfg file inside the repository .jar file and sends the deployment package to the server without changing the property values.
Deployment time properties are those properties of an artifact that are configured at the time of deployment, rather than at design time. System Manager allows you to specify deployment time properties specific to a server.
When an artifact is deployed to a server, System Manager applies the deployment time properties for that artifact before deploying it. You can also copy the properties of an artifact to more than one server. This keeps you from having to keep track of all the properties of the different components for the different servers. You can identify the properties that will have different values for different servers and add those properties as part of the deployment configuration. You can then configure the values for those properties depending on the server.
When the object is deployed to the server, System Manager automatically applies the configured values for the respective server before deploying it. To configure deployment time properties, right-click on the Integrated component library project and select Edit deployment descriptor. The Deployment Configuration window allows you to do the following:
One of the benefits of configuration management is the ability to copy properties between servers. To copy properties, right click on the property and choose Copy from the context menu. To paste the properties, right-click on a component and choose Paste. Multiple properties can be copied from one server and pasted in another. When the properties are copied, so are the values associated with them.
The deployment configuration can be imported or exported to and from a file from the Deployment Configuration dialog. Properties are exported by right-clicking on the property and selecting Export from the menu. The Export Property Descriptor dialog appears, where you must choose either Selected properties or All properties. Type the name of the file where you want the properties exported, or select Browse to locate the file. Click OK.
To import properties, right-click on the property and choose Import from the context menu. The Import Properties dialog appears. You can choose whether you would like to overwrite your properties or merge them. In the Please select Property Descriptor file field, type in the name of the file or choose Browse. Click OK.
When you create a repos_copy file out of System Manager, it will automatically have the deployment time properties included in the file. These properties will be applied to the artifacts before sending them to the server. For more information on using repos_copy and command-line options, see Using repos_copy.
Deployment configuration properties created for one server can be copied and pasted into the configuration for another server. When you copy and paste properties, any values assigned to those properties are copied and pasted as well. When you paste properties, if the properties already exist in the configuration, they are overwritten by the paste operation.
A standalone utility, contained in the deploymentconfigutil.zip file in the product \bin directory, can allow a *.dfg file to be edited without the use of System Manager. This can be useful, for example, in a situation where a database administrator needs to have a connector password property set to a specific value for interacting with the database, but does not want to reveal that value to the implementer who is using System Manager. The implementer can use the Deployment Configurator feature of System Manager to create a *.dfg file with default values and then send that file to the database administrator. The database administrator then runs the standalone utility, which allows modification of the property values (not the addition or deletion of integration components or properties). The database administrator uses the utility to modify the password value, and then sends the file back to the implementer, who uses System Manager to import the *.dfg file into Deployment Configurator.
This utility is controlled by a pre-defined password and you must contact the product support center to get one. The password is intended to prevent users without appropriate privileges from changing the passwords or encrypted data specified in the deployment descriptor files.
This standalone utility is contained in the deploymentconfigutil.zip file, which resides in the IBM\WebSphere\bin directory. The file can be extracted and used on a system that does not have either System Manager or InterChange Server Express installed.
For components with states (such as connectors, collaboration objects, maps, relationships, and database connection pools), you can set the state in which the component initializes when rebooting the server after deployment. Do the following to set the initial post-deployment state of components:
You can use standard Windows selection techniques to choose multiple components, such as the following:
You can validate a package comprised of the components you want to deploy before performing the deployment to ensure that the deployment will succeed. Do the following to validate a package of components:
For information on creating a user project see Creating user projects, and for information on adding shortcuts to a user project see Adding shortcuts to a user project.
System Manager displays the "Validate Project(s)" wizard, as shown in Figure 19.
If you have not selected any duplicate components, proceed to step 6.
If you have selected duplicate components, proceed to step 5.
System Manager displays the "Local Duplicates" screen, as shown in Figure 20.
Select distinct components among the duplicates.
System Manager creates a package containing the selected components and validates it against the server repository. A message is displayed to indicate whether validation was successful or not.
You can deploy components to an InterChange Server Express instance in one of two ways described in the following sections:
Do the following to use the deployment wizard to deploy a package of components to an InterChange Server Express instance:
Use the InterChange Server Express Component Management view or System Monitor to stop the duplicate components in the server before deploying a package. For more information, see Managing component states in the repository.
For information on creating a user project see Creating user projects, and for information on adding shortcuts to a user project see Adding shortcuts to a user project.
System Manager displays the "Deploy wizard page 1 screen", as shown in Figure 21.
The schemas for relationships and database connection pools must be created for interfaces that reference them to work. If you are deploying an interface for the purpose of running it then you must enable this option for any components the interface uses.
Maps and collaboration templates must be compiled for interfaces that reference them to work.
If you have selected duplicate components within the user projects then the "Deploy wizard page 2" screen appears, as shown in Figure 22:
Expand the folders of the displayed user projects and enable checkboxes for the particular components you want deployed between the local duplicates.
Do one of the following depending on your selections:
If you have chosen to deploy components that already exist on the server then the "Server Duplicate Objects" screen appears, as shown in Figure 23:
Expand the folders of the displayed user projects and enable checkboxes for the duplicate components you want to overwrite in the server repository.
System Manager attempts to deploy the selected components into the server repository. If you view the server logging output you will see messages logged as the deployment session is started and components are added to the repository.
When the deployment session finishes System Manager either presents an informational prompt that the deployment succeeded or an error prompt that the deployment failed.
Do the following to deploy components by using drag-and-drop techniques among the System Manager views:
Use the InterChange Server Express Component Management view or System Monitor to stop the duplicate components in the server before deploying a package. For more information, see Managing component states in the repository.
System Manager attempts to deploy the components to the specified InterChange Server Express instance. Messages and errors are displayed in the Console view.
Some WebSphere Business Integration Server Express users deploy solutions created by partners that involve communication across their respective organizations. Until now, communication was limited because the protocol used required additional configuration to communicate through a firewall. Web deployment functionality solves this problem by allowing the partner to perform deployment operations via the Web. This functionality enables a partner to
Web Deployment (WD) is a web-based application that allows users to deploy the components of a reposity file to InterChange Server Express or import the components of an InterChange Server back to a repository file through HTTP and HTTPS, protocols known to easily bypass firewalls. Both the deployment and import processes offer browser-based user interface allowing you to select some or all components to deploy or import. You can deploy and import between repository files and interchange servers.
This section covers the following topics:
When you ran the Installer for WebSphere Business Integration Express and included the Administrative Tools in your installation (or chose Typical), the Installer checked for supported versions of WebSphere Application Server and, if it found them, it automatically configured the Web Deployment feature to use them. In the same way, if you chose to install WebSphere Application Server Express 6.0 from the Launchpad before you installed the Administrative Tools, the Installer configured Web Deployment to use WebSphere Application Server Express 6.0.
However, before you can use Web Deployment, you must modify the ServerList.adm file, which contains the name and the location of the InterChange Server Express instance with which Web Deployment will communicate.
To locate the file, search on ServerList within the directory in which you installed the application server you are using with Web Deployment. If you installed WebSphereb Application Server Express 6.0, the location might look similar to this:
C:\IBM\WebSphere\Express60\installedApps\CHANGEMENode01
\WebDeployment.ear\WebDeployment.war\admin\ServerList.adm
Open ServerList.adm in a text editor, and add a line that provides the logical name of the InterChange Server Express instance to which you want to connect, along with the URL. You can add more than one entry, and you can connect to InterChange Server Express instances that are either local or across the Web. For example:
ibmserver=http://localhost:4443
test44=https://9.26.246.77:8080
Complete the following steps to register a new server and connect to it.
http://<host>:<port>:/WebDeployment
Where host is the IP address of the machine that is hosting the web server, and port is a port number that the web server has been configured to work with. For example, in a default installation of Web Deployment on a machine that is a supported version of WebSphere Application Server or WebSphere Application Server Express 6.0, the URL is typically:
http://localhost:7089/WebDeployment
If the server connects, the name of the server appears in the left frame under InterChange Server Instances. A connected server icon indicates that the server is connected.
If the server connection fails, the Register New Server form reappears with an error message. The server is registered, but appears in the left frame with a disconnected server icon.
Complete the following steps to delete a registered server. You can only delete a disconnected server.
Complete the following steps to connect a registered server that has been disconnected.
If the server connects, the connected server icon appears beside the server in the left pane. If the server connection fails, you receive an error message and the disconnected server icon appears beside the server.
Complete the following steps to disconnect a registered and connected server.
If you successfully disconnect the server, the icon beside the server indicates that the server is disconnected. A confirmation form also appears in the right panel to indicate that the server disconnected.
Complete the following steps to import some or all components of a server to a repository file.
Complete the following steps to deploy some or all components of a repository file to a server.
Complete the following steps to delete a part of or the entire server repository.