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.
As described in InterChange Server modes, 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:
Click OK to close the "Validate Repository" prompt.
If there are unresolved dependencies in the repository then the "Missing Dependencies" dialog is displayed, as shown in Figure 24. Click Finish to close the "Missing Dependencies" dialog.
To validate a database connection pool, right-click the pool in the InterChange Server Express Component Management view and choose Validate database connection from the context menu.
For more information about database connection pools, see Configuring database connection pools.
You can use the InterChange Server Express Component Management view to manage the states of components in the repository of an InterChange Server Express instance.
This is very useful when you are developing an interface because you have to test the components you are developing. You will frequently test a component and find that you must change it. Then you will deploy the modified component to the server and test it again. To deploy a component to the server, however, it must be in an inactive state, so you must stop the component prior to deployment. Since you can develop, deploy, and test an interface all within the workbench, it is very convenient to also be able to manage the component states from it as well.
To change the state of a component in the InterChange Server Express
Component Management view, right-click the component in the navigation tree
and choose the desired state from the context menu. Table 7 lists the state operations that you can apply for each of
the component types that have runtime states. For more information on
the behavior of the system when components are in different states, see the
System Administration Guide.
Table 7. State operations available for components in System Manager
Component type | State operation |
---|---|
Collaboration object |
|
Connector |
|
Map |
|
Relationship |
|
You can also select multiple components, right-click one of the components, and apply state changes to all of them at the same time. This is very useful when you must deploy a number of components at the same time, because you do not have to perform a separate state-management operation for each one. You can use standard Windows selection techniques to select multiple user projects for deployment at the same time, such as the following:
To modify the state all of the components of a particular type, right-click the folder for the component type in the InterChange Server Express Component Management view and select Start All or Stop All from the context menu.
It is recommended that you use System Monitor to manage components in a production installation. System Monitor offers greater flexibility and is a dedicated administration tool. For more information on using System Monitor, see the System Administration Guide.
Maps, connectors, and collaboration objects have runtime properties that you can modify to change the behavior of those components. Follow the instructions in the following sections to modify the properties for particular components:
Do the following to modify the properties of a collaboration object:
For more information about collaboration object properties, see Configuring collaboration objects.
Figure 25 shows the "Properties" dialog for collaboration objects:
Do the following to modify the properties of a map:
For more information about map properties, see the Map Development Guide.
Figure 26 shows the "Maps Property Page" dialog:
Do the following to modify the properties of a connector:
Figure 27 shows the "Properties" dialog for connectors:
Collaboration templates must be compiled for the collaboration objects that are based on them to run, and maps must be compiled to run as well. You can deploy collaboration templates and maps to an InterChange Server Express running in design mode without compiling them, but must ensure that they are compiled to test them.
To compile a collaboration template in the server, right-click the template in the InterChange Server Express Component Management view and choose Compile from the context menu.
To compile all of the collaboration templates in the server, right-click the Collaboration Templates folder in the InterChange Server Express Component Management view and choose Compile All from the context menu.
To compile a map in the server, right-click the map in the InterChange Server Express Component Management view and choose Compile from the context menu.
To compile all of the maps in the server, right-click the Maps folder in the InterChange Server Express Component Management view and choose Compile All from the context menu.
To compile a map along with all of its submaps, right-click the map in the InterChange Server Express Component Management view and choose Compile with submaps from the context menu.
The "Console" view displays messages about the success or failure of compilation attempts.
As you develop a business integration system, the design of the system frequently changes. New requirements and environmental differences commonly result in the redesign of an interface. You will want to make sure that the repository contains only the components it needs to solve business problems according to the current design, and that will sometimes mean that you have to delete components that belong to designs that have changed.
To delete all of the components in a server repository using System Manager do the following:
Do the following to delete components from an InterChange Server Express repository by using the component browser:
You can use standard Windows techniques for selecting multiple items, such as holding Shift to select multiple contiguous items, and holding Ctrl to select multiple non-contiguous items.
To stop a component using the InterChange Server Express Component Management view in System Manager, see Managing component states in the repository.
To stop a component using System Monitor, see the System Administration Guide.
Figure 28 shows System Manager when the component browser is used to delete components.
For instance, a business object cannot be deleted if it contains other business objects because they depend on it, even if those dependent components are also selected for deletion, unless this option is enabled.
If the delete operation is successful then the wizard exits.
If the delete operation failed, click OK to close the error prompt, then resolve the problem and try the operation again. The error information in the prompt can be very difficult to use in troubleshooting, so it is recommended that you use the server logging output to determine the cause of the failure.
Do the following to use System Manager to delete components from an InterChange Server Express repository by using the Server Object Delete Wizard:
To stop a component using the InterChange Server Express Component Management view in System Manager, see Managing component states in the repository.
To stop a component using System Monitor, see the System Administration Guide.
For instance, a business object cannot be deleted if it contains other business objects because they depend on it, even if those dependent components are also selected for deletion, unless this option is enabled.
Figure 29 shows the "Server Objects Delete Wizard".
If the delete operation is successful then the wizard exits.
If the delete operation failed, click OK to close the error prompt, then resolve the problem and try the operation again. The error information in the prompt can be very difficult to use in troubleshooting, so it is recommended that you use the server logging output to determine the cause of the failure.