Business object restart requirements

Table 30 describes the restart requirements for business objects.

Note:
These restart requirements are for administrative tasks only. For information on restart requirements for development or implementation tasks, see the appropriate development guide or the System Implementation Guide.

Table 30. Business object restart requirements

Action Restart requirement
Add a business object Dynamic
Delete a business object Delete business object dependencies prior to deleting business object
Any change listed in this table. If any tool, such as Map Designer or Process Designer, is connected to InterChange Server when any change listed in this table is made, that tool must be disconnected from, then reconnected, to the server.
Change the application-specific text for attributes. Restart connector agent. Restarting InterChange Server is strongly recommended.
Change key attribute. Restart connector agent.
Change default value. If the connector uses the "UseDefaults" connector configuration property, the connector agent must be restarted. Restarting InterChange Server is strongly recommended.
Change max length for an attribute. Restart connector agent.
Change required field for an attribute. Restart connector agent.
Change trace level. Dynamic
Change attribute names. Restart connector agent.
Change business-object structure (removing or adding attributes/sub-objects). Stop InterChange Server.

Clean queues.

Restart InterChange Server.

The maps using the object must be updated and recompiled.

Copyright IBM Corp. 1997, 2004