- In Server Explorer, right-click your enterprise server, and select the appropriate action to perform:
Start,
Stop, or
Restart.
Tip: Use the filter box in the top-right corner of the Server Explorer to restrict the servers displayed: type in the box to automatically
restrict the list of servers displayed.
For certain actions, the
Enterprise Server Sign On dialog box may be displayed.
Note: If the required options are not available, it may be that the server is in an unstable state; use the
Open Administration Page option to open ESCWA and view (and fix) the server status from there.
- If it is displayed, do one of the following:
- If Eclipse detects that the server uses an external security manager (ESM),
Server is secured is selected by default. Enter the required credentials.
- If no ESM is in use, but the server is secured, select
Server is secured, and enter the required credentials.
- If no security is enabled for the server, leave the options as they are.
- If you entered any credentials, select
Store Credentials to save them for future use.
The Enterprise Server Sign On screen will not be displayed next time the server is started/restarted, or a JCL job submitted to it.
Note: Use the
Clear credentials option on the server's context menu to clear the current credentials, and then enter new ones.
For local servers, the enterprise server is started by running the
casstart command under the current user's credentials. Otherwise, the server is started using the ESCWA services, under the "SYSTEM"
user ID. (These credentials are separate from the sign-on credentials that are prompted for.)
You can see the progress of these commands in the console if you have enabled
Show Local Console for your enterprise server in
Enterprise Server Common Web Administration (ESCWA). When you have signed on, the sign-on details are displayed in the Properties pane when
the server node is selected.