This topic describes how to start and stop a connection and lists the possible connection status values.
Starting and stopping connections
A connection needs to be fully defined before you can start it.
Tip: Micro Focus Connect attempts to run a connection once it is defined. You can see a connection's status on the Micro Focus Connect dashboard.
- To start an idle connection, click the Modify connection button adjacent to the connection name, and select Start Connection.
- To stop a running connection, click the Modify connection button adjacent to the connection name, and select Stop Connection.
Note: From version 4.4.2, if you start multiple connections one after the other, the connections are queued: The second connection will enter its startup process only after the first connection is running.
For information on how to start and stop connections using batch utility scripts, see Batch utility scripts.
Connection status values
The Connections page contains a grid listing each of your connections. One of the columns in the grid is Status. The following are the available Status values:
|Disabled||The connection is disabled and not active, its projects are not active, or an error was detected that caused Micro Focus Connect to disable the connection.|
|Failed||One or more sync-sets associated with this synchronization have failed and no subsequent iterations have succeeded. See the Running status for an example.|
There are no projects to synchronize or the projectMaps are disabled.
|Restarting||Either the application is restarting causing a Connection to restart, a change to the underlying configuration occurred causing a Connection to restart, or the user started the Connection. When the sync is complete, the status changes to Running or Failed.|
The status is Running when the last available status for all sync-sets is Success.
For example, for a synchronization with three sync-sets (ss1, ss2, ss3):
Case 1 RUNNING: Iteration 2: ss1=success, ss2=success, ss3=success Iteration 3: ss1=ongoing Case 2 FAILED Iteration 2: ss1=failed, ss2=success, ss3=success Iteration 3: ss1=ongoing Case 3 RUNNING: Iteration 2: ss1=failed, ss2=success, ss3=success Iteration 3: ss1=success, ss2=ongoing
|Server Reinitializing||The application is reinitializing after changes to the configuration. This status is displayed for all connections until the application has restarted the configuration and created the associated sync-sets.|
|Unknown||The synchronization status is not known to the application. There is an error.|