The proxy container or proxy component must be configured before you can start it successfully.
You start a proxy by selecting the menu item Start Proxy in the context menu of the relevant proxy node in the navigation tree.
If the proxy is only configured for partners of type openUTM then it is started immediately.
If the proxy is (also) configured for partners of type CICS, a selection dialog box then appears which allows you to select those components of the proxy which you want to be started:
Proxy container
openUTM-LU62 Gateway
Communication Service
Before you start openUTM-LU62 and the communication service, the associated MC-CmdHandler must already be started.
If you are starting the openUTM-LU62 Gateway (CICS) you can also select the option Cold Start. All restart information is lost during a cold start.
Before starting a proxy, the Management Console first checks whether the proxy container or the proxy component is already available.
The proxy container or the proxy component must be configured before it can be started successfully.
The openUTM-LU62 Gateway and the Communication Service cannot be started until at least one EIS partner of type CICS has been defined for the proxy. For more information, refer to the section Configuring the BeanConnect proxy .
For CICS partners:
To administer the Communication Service the administration user must be member of the predefined SNA administrator group sna. The user group sna is present after the installation of the communication service. The administrator is the user under whose user ID, the MC-CmdHandler was started.
The Management Console issues appropriate messages in an action dialog box in which you can monitor the actions and results. You can
identify what actions have already been carried out and control the results of the completed actions,
display detailed information on the results if an error occurs,
if necessary, cancel the entire operation. In this case, only the execution of the subactions that have not yet been performed is cancelled. Subactions that have already been executed are not undone.
If an availability check has been performed, the status icons in front of the relevant node in the navigation tree are colored depending on result (green if the proxy container or, in the case of CICS partners, the proxy component is running or red if not running). In the case of UTM proxies, the icon consists of one part and describes the status of the proxy container. In the case of CICS proxies, the icon consists of three parts.
The individual icons stand for the following components:
Left | Proxy container |
Middle | openUTM-LU62 Gateway |
Right | Communication Service |
An availability check is performed automatically at predefined time intervals or can be started manually (see Checking the availability of BeanConnect proxies ).
To permit communication between the application server and the EIS partner, all the proxy components must be active (green).In the case of CICS partners, this is not always sufficient, i.e. the communication may not function properly even though the icons are green. In such cases, you must also check the established connections and opened sessions, see Diagnosis information for the openUTM-LU62 Gateway .
Starting the proxy container as a Windows service
On Windows systems, you can also start a proxy container as a Windows service using the Management Console:
Select the proxy in the navigation area of the Management Console.
From the context menu, select the item Edit Properties, open the General tab and select the option Start as Service.
Save the configuration with Save/Restart - Save. The next time the proxy is started, it is started as a Windows service. If the proxy is already running then this change does not take effect with the proposed restart. Instead, it only becomes effective when the proxy is shut down and then restarted.
Further information can be found in Starting as a Windows service .