IBM E02HMLL-I Implementation Guide - Page 95
Working, components, InterChange, Server, Express, repository, Validating
View all IBM E02HMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 95 highlights
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" on page 84. 2. Do the following in the WebSphere Business Integration System Manager view to select the components you want to deploy: v Select user projects or integration component libraries to choose all of the components in them. v Choose all components of one type by selecting its folder in a user project or integration component library. v Expand the component folders and select individual components to choose them. You can use standard Windows selection techniques to select multiple user projects for deployment at the same time, such as the following: - Hold down Shift to select contiguous items. - Hold down Ctrl to select non-contiguous items. 3. Drag-and-drop the selected resources onto the InterChange Server Express instance to which you want to deploy the components in the InterChange Server Express Component Management view. System Manager attempts to deploy the components to the specified InterChange Server Express instance. Messages and errors are displayed in the Console view. Note: If you selected duplicate components in the WebSphere Business Integration System Manager view then System Manager generates an error when you try to deploy the components. Refine your selection to include only unique components and then attempt the deployment again. Working with components in an InterChange Server Express repository The InterChange Server Express Component Management view allows you to manage the repositories of the InterChange Server Expresss you have registered, and to manage the components in those repositories. Validating the components in the repository As described in "InterChange Server modes" on page 45, InterChange Server Express has different restrictions regarding the integrity of the repository depending on the mode you start it in. Although a server running in design mode allows the repository to be inconsistent so that you can add components as they become available, a server running in production mode requires that all references and dependencies among the components be resolved. When you migrate from a design-mode server to a production-mode server, then, you should validate the repository beforehand to make sure that the repository will be in a consistent state. Do the following to validate the repository using System Manager: 1. In the InterChange Server Express Component Management view, right-click the server instance whose repository you want to validate and choose Validate Repository from the context menu. 2. If the repository is in a consistent state, an informational prompt is displayed. Click OK to close the "Validate Repository" prompt. Chapter 4. Using System Manager 83