You are on page 1of 3

SDM: to uncar the downloaded patches from service market place JSPM:to apply the patches which are

uncar successfully VISUAL ADMIN:to work with rfc connections CONFIG TOOL:used to work in user administration Visual administrator and config tool are for maintaining the Java settings: like parameters and its values, starting and stopping services. Visual administrator is online tool where as config tool is offline. you need to login with sidadm user to operate these tools SDM :- Software Deployment Manager is been replaced with JSPM tool for more intelligent work. It is a tool from where we can apply the support packages, but now it is outdated and we are using JSPM tool to deploy the support packages. For SDM tool we need to manually feed the support packages. With SDM tool we can also undeploy the support packages. It is initialized with remotegui.bat (Windows) or remotegui.sh (Unix) JSPM:- Java supsport package manager is initialized by go.bat (WIndows) or go.sh (Unix). It uses the SDM password. It is an intelligent tool it will check the patch levels at market place with the existing patch levels. it will read the SP's from inbox automatically. we can even upgrade the kernel here. Config tool : It is a configuration tool which works offline. it does not require java engine to be up and running to open. it is initialized by configtool.bat or configtool.sh it is used to configure the ldap to populate the user information. it is used to increase and decrease the server processes. it is used to change the password of superuser when all the users got locked.

Visual Admin Tool : It is online tool requires java engine to be start. remote login is possible with this tool. it is initialized by go.bat or go.sh Most of the parameters are dynamic and does not require restart of engine. it requires user id and password to login

Steps for Patching JAVA Stack Once the required patches files are downloaded from Service Market place,then move all the patches files to global EPS inbox directory /usr/sap/trans/EPS/in. Step 1: Start the JSPM tool from \usr\sap\CTM\DVEBMGS00\j2ee\JSPM\go.bat .It will prompt for the JSPM password. Step 2: Choose the Deployment tab.JSPM guides you through the process of applying a support package stack via a wizard, which consists of the following five options: 1.Select Package Type 2.Specify Queue 3.Check Queue 4.Deploy Queue and 5.Completed. Step 3: Select Support Package Stack type(option button). Support package Stack, Single Support Package etc.. NWDI controls:(option button) If your system is not used for NWDI development, select No NWDI. And If your system is used for NWDI development, select the role of your system by selecting one of the following: DEV, CONS, TEST, or PROD. Step 4:Choose Next. Support package stacks that are available for deployment from the global EPS inbox directory are displayed in the screen.

Step 5:Click on Next button JSPM starts the deployment of the software components that are part of the selected support package stack. The status of all software components changes to SCHEDULED. Note: If the support package stack includes a kernel upgrade, and if your system is distributed, during the deployment you will be first prompted to stop the central services instance and any running dialog instances, and to choose Next. You will be then prompted to start the central services instance and to choose Next. Step 6: The deployment of the components of the support package stack can finish with the one of the following status: *DEPLOYED *DEPLOYED WITH WARNING *ERROR *NOT DEPLOYED If the support package stack includes the JSPM, when it has been updated, for the update to take effect, you will be prompted to restart it. If there are still components in status NOT DEPLOYED, JSPM will proceed with their deployment when you start it again. Bear in mind that you must not change the content of the global EPS inbox directory before the deployment has finished.

Step 7: Click Next If the deployment of the support package stack has finished with status DEPLOYED, you can choose New Deployment or Exit Completed

You might also like