BEA Home | Events | Solutions | Partners | Products | Services | Download | Developer Center | WebSUPPORT
JAM Documentation | JAM Configuration and Administration Guide | Previous Topic | Next Topic | Contents | Index

Shutting Down the System for Planned Outages

Occasionally, your JAM system may need to be shut down for planned outages of your remote environment. You may shut the JAM gateway and the CRM down together or independently without stopping or re-starting WebLogic Server. In most cases, you would probably not want to shut down the CRM independently. When you shut the gateway down, all links associated with the gateway are shut down. You can also shut down specific links without shutting down the gateway.

Action List

Before you shut down your JAM system for planned outages, see the following action list and refer to the appropriate information sources.

| Your action... | Refer to...
--- | --- | ---
1 | Complete all prerequisite tasks. | Prerequisites
2 | Shut down the system. | Shutting Down the System
3 | Restart the system. | Restarting the System
4 | Determine what you want to do next. | What Do I Do Next?, BEA WebLogic Java Adapter for Mainframe Workflow Processing Guide, or BEA WebLogic Java Adapter for Mainframe Programming Guide

Prerequisites

Before you shut down your JAM system for planned outages, you should complete the following tasks.

| Your action... | Refer to...
--- | --- | ---
1 | Verify that system requirements have been met. | BEA WebLogic Java Adapter for Mainframe Introduction and Release Notes
2 | Determine which configuration your system requires and install the JAM product as appropriate for your configuration. | BEA WebLogic Java Adapter for Mainframe Installation Guide
3 | Verify that your mainframe configuration has been properly set up for the CRM. | Preparing Mainframe Configurations for CRM Requirements
4 | Create a JAM configuration file and verify that the gateway has been properly configured. | Defining the JAM Gateway Configuration
5 | Learn how to start or stop the CRM with the CRM administration commands. | Using the CRM Administration Commands
6 | Deploy your configuration and verify that the gateway is working properly. | Deploying Your Configuration
7 | Learn about the JAM administration utilities. | Using JAM Administration Utilities

Shutting Down the System

To shut down all, or parts of your JAM system without stopping or re-starting WebLogic Server, perform the following steps:

1. Shut down your CRM, gateway and associated links, or one or more links, using the following procedures as required:

Component | Shutdown Procedure
--- | ---
CRM | Use the crmdown command. Refer to the crmdown Command and Stopping the CRM On All Platforms sections for more information. Most likely you will not want to shut down the CRM without shutting down the gateway.
Gateway and associated links | Stop the gateway from the JAM Administration Servlet. Refer to the Starting and Stopping the Gateway with the JAM Administration Servlet section for more information.
Link | Use the crmlkoff command. Refer to the crmlkoff Command section for more information.

2. Using a procedure as appropriate for your system, bring your CICS or IMS regions down.

Restarting the System

To restart all, or parts of your JAM system, perform the following steps:

1. Using a procedure as appropriate for your system, bring up your CICS or IMS regions.

2. Restart the JAM components as required using the following procedures:

Component | Restart Procedure
--- | ---
CRM | Use the CRM command. Refer to CRM Command and Starting and Stopping the CRM for more information.
Gateway and associated links | Start the gateway from the JAM Administration Servlet. Refer to the Starting and Stopping the Gateway with the JAM Administration Servlet section for more information.
Link | Use the crmlkon command. You can specify one or more links to start. Refer to the crmlkon Command section for more information.

What Do I Do Next?

After you configure the JAM gateway and verify that your JAM system is working properly, you can begin using JAM for workflow processing or generating Java source code. If you want to perform workflow processing between Java applications and the mainframe, refer to the BEA WebLogic Java Adapter for Mainframe Workflow Processing Guide. If you want to develop Java applications by generating Java source code from COBOL copybooks, refer to the BEA WebLogic Java Adapter for Mainframe Programming Guide.

Copyright © 2001 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.