Table 29 describes the restart requirements for connectors.
Table 29. Connector restart requirements
Action | Restart requirement |
---|---|
Add a new connector | Restart InterChange Server |
Delete a connector | Dependent collaboration objects must be deleted first |
Change configuration property (other than those mentioned below) | Restart connector component. See property description in Connector Configurator to determine action |
Change supported business objects properties | Restart connector |
Remove supported business object | Restart connector |
Change trace level of the connector agent | Dynamic |
Change trace level of the connector controller | Dynamic |
Change poll frequency | Dynamic |
Change controller store and forward mode | Dynamic |
Change transport protocol | Restart InterChange Server |
Change concurrent event triggered flows | Restart InterChange Server |
Change poll start time | Restart connector |
Change poll end time | Restart connector agent |
Create new connector | Does not require a restart of InterChange Server |
Recompile connector | Restart connector agent |
New supported business objects | Restart connector agent |
Bind maps to supported business object | Refresh connector screen in System Manager |
Copy and paste connector | Restart InterChange Server. Until InterChange Server is restarted, the Associated Maps screen is blank because the information in this screen reflects the InterChange Server's run time only. Since this is a brand new connector with new supported BOs that are not yet reflected in InterChange Server's run time, the Associated Maps screen has no running BOs for binding maps. |
Make changes to the values of the following standard properties:
| From System Manager, right-click the server under Server Instances, then select Refresh. The Refresh option stops the connector, temporarily caches its transient state, removes the instance from memory and replaces it with the new instance, then starts the new instance. |