Step by Step Guide for SCM Server Start and Stop Procedure with LiveCache and Optimizer.

Size: px

Start display at page:

Download "Step by Step Guide for SCM Server Start and Stop Procedure with LiveCache and Optimizer."

Hollie Chandler
5 years ago
Views:

Step by Step Guide for SCM Server Start and Stop Procedure with LiveCache and Optimizer. Applies to: This document applies to SCM 5.0 (NW 7) and above with LiveCache 7.

1 Step by Step Guide for SCM Server Start and Stop Procedure with LiveCache and Optimizer. Applies to: This document applies to SCM 5.0 (NW 7) and above with LiveCache 7.6 (LCAPPS 2005_700, LiveCache Applications 5.0) and Optimizer 5.0 and above. For more information, visit the Supply Chain Management homepage. Summary This document mainly highlights step by step procedures to start and stop SCM Server with LiveCache and Optimizer. It is assumed that SCM, LiveCache and Optimizer are installed, implemented and configured. Author: Pratap Kumar Bose Company: IBM India Pvt. Ltd. Created on: 30 September 2008 Author Bio Pratap is working in IBM India Pvt. Ltd. as SAP NW BASIS Consultant SAP AG 1

2 Table of Contents Startup Process...3 Steps to Start SCM Server...3 SAP SCM ABAP and Java Under UNIX...3 SAP SCM ABAP and Java Under Microsoft Windows...3 SAP SCM ABAP Under UNIX...3 SAP SCM ABAP Under Microsoft Windows...3 Java Stack of an SAP SCM Add-In Installation (Restart/Start/Stop)...4 Steps to Start LiveCache Server...4 Steps to Start Optimizer...5 Shutdown Process...6 Steps to Stop LiveCache Server...6 Steps to Stop Optimizer...7 Steps to Stop SCM Server...7 SAP SCM ABAP and Java Under UNIX...7 SAP SCM ABAP and Java Under Microsoft Windows...7 SAP SCM ABAP Under UNIX...7 SAP SCM ABAP Under Microsoft Windows...7 Java Stack of an SAP SCM Add-In Installation (Restart/Start/Stop)...8 Related Content...9 Disclaimer and Liability Notice SAP AG 2

3 Startup Process Most of the places SCM server is installed with AS ABAP. Usage type AS JAVA is installed mainly for EM (Web Communication Layer) and F & R (Forecast and Replenishment) for Store User Interface. Startup process of SCM server actually means starting up of following servers : SCM Server LiveCache Server Optimizer Steps to Start SCM Server Process of starting up SCM Server is same as starting up any ECC Server. Starting SCM ABAP and Java Instances together : In case of an add-in SCM installation (ABAP + Java), when ABAP instances are started, the corresponding Java instances are also automatically started, by default. SAP SCM ABAP and Java Under UNIX 1. Log on to the central system host as SAP administrator <sid>adm. 2. Enter startsap ALL to start SAP SCM ABAP and Java. The database, the ABAP instances, all Java instances and all other processes of the system are started on this host. SAP SCM ABAP and Java Under Microsoft Windows 1. Start the Microsoft Management Console (MMC) that contains the SAP snap-in. 2. Select the system ID of the system and open the context menu by right-clicking. 3. Choose Start. The database, all ABAP instances, all Java instances, and all additional processes of the system are started. If all instance icons appear green, the start was successful. Starting SCM ABAP and Java Instances separately : To deactivate the automatic starting of the Java instances along with the ABAP instances, the instance profile parameter rdisp/j2ee_start needs to be set to the value 0 in transaction RZ10. SAP SCM ABAP Under UNIX 1. Log on to the central system host as SAP administrator <sid>adm. 2. Enter startsap ALL to start SAP SCM ABAP and Java. The database, the SCM ABAP instances, all Java instances and all other processes of the system are started on this host. SAP SCM ABAP Under Microsoft Windows 1. Start the Microsoft Management Console (MMC) that contains the SAP snap-in. 2. Select the system ID of the system and open the context menu by right-clicking. 3. Choose Start SAP AG 3

4 Java Stack of an SAP SCM Add-In Installation (Restart/Start/Stop) With an add-in installation, a SCM Java instance is assigned to an SCM ABAP instance. The Internet Communication Manager (ICM) of the SCM ABAP instance starts the associated Java instance as required. To restart the Java stack of SAP SCM add-in installation (ABAP + Java), the following process can be used: 1. Log on to the ABAP stack of SAP SCM. 2. Open the list of SAP servers by calling transaction SM To connect, Double-click the instance for which the Java stack is to be restarted. 4. Start the ICM Monitor (transaction SMICM) by entering /nsmicm in the command field. 5. In transaction SMICM, choose Administration-> J2EE Server 6. Choose option to start J2EE Server. Steps to Start LiveCache Server Starting X_Server in LiveCache Server : To access MaxDB in LiveCache server from SCM server, x_server process is to be started in LiveCache Server. MaxDB is accessed from SCM Server through SQLDBC driver for AS ABAP. If SCM Server and LiveCache are installed on same server, then to access MaxDB through SQLDBC, it does not require any x_server process to be initiated in LiveCache Server. But if LiveCache server installed separately (which is recommended) than SCM Server, then to access MaxDB from SCM Server, it requires x_server process to be started. For Java, MaxDB is accessed through SQLJDBC driver, which requires x_server to be installed and started, even if both LiveCache and SCM are installed on same server. x_server is automatically installed while installing LiveCache. And for Windows, x_server is automatically started with Windows startup. In Unix, it is not configured to be started automatically while LiveCache installation. Following steps are to be followed to start x_server in Unix : 1. Log in to Live Cache Server : User Id :- <sid>adm Password :- ******* 2. Now Go to cd /sapdb/programs/bin 3. Run command./x_server start Starting LiveCache From SCM Server : Start the LiveCache as mentioned below : (IN SCM SERVER) Go to LC10 Click on LiveCache : Monitoring SAP AG 4

5 LC10 LCA Administrator Operating The Operational State should show green light Steps to Start Optimizer Optimizer is basically collection of executable files, guided by global objective functions based on key performance indicators for optimization. These files are accessed from SCM server for external optimization of certain processes. In SAP to access one SAP server from another, we require Gateway service is to be in place in both the server. So here also Gateway service is installed automatically when we install SCM Optimizer in a server. To start this optimizer, from SAPCONSOLE manually start SID of Gateway Service by right click and then start. (It is not mandatory to start Optimizer immediately after SCM and LIVECACHE. Optimizer will only be referred by SCM when functionally it is directed to Optimizer and that time if Optimizer is not up then there will be problems.) All Gateway SID processes lights should be green SAP AG 5

Shutdown Process Steps to Stop LiveCache Server

6 Shutdown Process Steps to Stop LiveCache Server Shutdown LiveCache From SCM Server : From SCM Server we can stop LiveCache by going through following processes : Go to LC10 Click on LiveCache : Monitoring. LC10 LCA Administrator Operating The Operational State should greyed SAP AG 6

7 Stop X_Server in LiveCache Server : In Windows, there is no need to stop x_server, because it is automatically stopped when Windows shuts down. In Unix we use following steps : 1. Log off from SAP. 2. Now log in to Live Cache Server : Steps to Stop Optimizer User Id :- <sid>adm Password :- ******* 3. Now Go to cd /sapdb/programs/bin 4. Run command./x_server stop From SAPCONSOLE manually stop SID of Gateway Service by right click and then stop. All Gateway SID processes lights should be greyed. Steps to Stop SCM Server Process of stopping SCM Server is same as stopping any ECC Server. Stopping SCM ABAP and Java Instances together : In case of an add-in SCM installation (ABAP + Java), when SCM ABAP instances are stopped, the corresponding Java instances are also automatically stopped, by default. SAP SCM ABAP and Java Under UNIX 1. Log on to the central system host as the SAP SCM administrator <sid>adm. 2. Enter stopsap R3 or stopsap J2EE to stop SAP SCM ABAP and SAP SCM Java. The stopsap command with the switch R3 or J2EE does not stop the database simultaneously. To stop the database simultaneously, the command stopsap or stopsap ALL will be used. SAP SCM ABAP and Java Under Microsoft Windows 1. Start the Microsoft Management Console (MMC) that contains the SAP snap-in. 2. Select the system ID of your system and open the context menu by right-clicking. 3. Choose Stop. If all instance icons appear gray, the stop was successful. The database is not stopped automatically when SAP SCM is stopped. Database-specific tool has to be used to stop the database. Stopping SCM ABAP and Java Instances separately : SAP SCM ABAP Under UNIX 1. Log on to the central system host as the SAP administrator <sid>adm. 2. Enter stopsap R3 or stopsap J2EE to stop SAP SCM ABAP and Java. The stopsap command with the switch R3 or J2EE does not stop the database simultaneously. To stop the database simultaneously, the command stopsap or stopsap ALL will be used. SAP SCM ABAP Under Microsoft Windows 1. Start the Microsoft Management Console (MMC) that contains the SAP snap-in. 2. Select the system ID of your system and open the context menu by right-clicking. 3. Choose Stop. If all instance icons appear gray, the stop was successful SAP AG 7

8 The database is not stopped automatically when SAP SCM is stopped. Database-specific tool has to be used to stop the database. Java Stack of an SAP SCM Add-In Installation (Restart/Start/Stop) With an add-in installation, a SCM Java instance is assigned to an SCM ABAP instance. The Internet Communication Manager (ICM) of the ABAP instance starts and stops the associated Java instance as required. To restart the Java stack of SAP SCM add-in installation (ABAP + Java), the following process can be used: 1. Log on to the ABAP stack of SAP SCM. 2. Open the list of SAP servers by calling transaction SM To connect, Double-click the instance for which the Java stack is to be restarted. 4. Start the ICM Monitor (transaction SMICM) by entering /nsmicm in the command field. 5. In transaction SMICM, choose Administration-> J2EE Server 6. Choose one of the following functions: a. Sending a Soft Shutdown (With or Without a Restart) The (SCM ABAP) dispatcher of the SAP Web Application Server sets the restart flag for the J2EE Engine and sends the SOFTSHUTDOWN message to the J2EE Engine. The dispatcher does not actively close the connection, the J2EE Engine must close itself instead. If the application server is restarted, the J2EE Engine is restarted by the dispatcher. b. Sending a Hard Shutdown (With or Without a Restart) The (SCM ABAP) dispatcher of the SAP Web Application Server sets the restart flag for the J2EE Engine and sends the HARDSHUTDOWN message to the J2EE Engine. The dispatcher does not actively close the connection, the J2EE Engine must close itself instead. If the application server is restarted, the J2EE Engine is restarted by the (SCM ABAP) dispatcher. c. Ending the Process (With or Without a Restart) The (SCM ABAP) dispatcher sets the restart flag for the J2EE Engine and sends a signal to the process (shell or Java process). If the application server is restarted, the J2EE Engine is restarted by the dispatcher. d. Restart Yes/No This set the J2EE Engine s restart flag SAP AG 8

9 Related Content For more information, visit the Supply Chain Management homepage SAP AG 9

10 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 10

Step by Step Guide for PI Server Start and Stop Procedure

Step by Step Guide for PI Server Start and Stop Procedure Applies to: This document applies to PI 7.0 and 7.1 and above. For more information, visit the Application Management homepage. Summary This document