In ABAP stack Startup sequence.
The Startup script will start the sapstart binary which will read the start profiles (/usr/sap/SID/SYS/profiles/START_INSTANCE_HOSTNAME) and get all the information like Hostname, System Name (SID), instance number.
Once the information are available the script will start the dispatcher which in turn will read the install profile and starts the server like, Database, Message Service, Enqueue Service, Dispatcher Service. The dispatcher in turn will start all the Work Process Services.
Java Startup process. (JCONTROL and JLAUNCH :- JControl starts JLaunch)
Sequence
1. Database is Started : Database must be operational before SAP is started.
2. Central Services is Started : Java Central services which includes the message service, enqueue service are started.
3. Central Instance is started : Now the Java Central Instance which includes the services like Dispatcher, Server process and SDM is started by “Start and Control Framework”
The Start procedure in the Startup and Control Framework
3.1 JControl is started by the startup script.
3.2 JControl creates a connection to the message server (on the CS).
3.3 JControl starts a Java Instance bootstrap process with parameters that are defined in the file bootstrap.properties (/usr/sap/SID/instance/j2ee/cluster/bootstrap). The bootstrap process synchronize all required binaries for the Java Nodes from the database with the file system. This is necessary, since the Class Loading is performed using the file system in the Java environment. The database always contains the current (deployed) binaries and properties and distributes these to every java node when starting.
3.4 The java instance bootstrap process reads the instance description from the java schema of the database.
3.5 The java instance bootstrap process stores a file instance.properties, containing the instance description, at operating system level.
3.6 JControl start the instance description from the file system.
3.7 JControl starts the specified bootstrap processes for java nodes. Then JControl starts all java nodes such as dispatchers and servers as JLaunch processes and, when doing so, loads a JVM in the JLaunch process.
--->>> If an ABAP instance is started with an additional Java Instance, the ABAP dispatcher uses a signal from the ABAP dispatcher process to run a start command on the Startup and control Framework.
Every time Java instance is started it will create a instance.properties file (/usr/sap/SID/instance_name/j2ee/cluster/instance.properties ), which is used for synchronizing the information with the database. The instance profile contains A service called Jcontrol will start initially which in turn will start Jlaunch process. There would be as many as jlaunch processes as many there are server process like dispatcher process, Server process, SDM. For each instance it will start one jcontrol and atleast 2 jlaunch process (dispatcher and Server process).
Central services (Message Service and Enqueue Service) are not started by jcontrol process. Java’s instance profile is not used for any configuration, here the configurations are done in services which are modified by either tool called “Configtool” or “Visual Administrator”.
4. Java Additional Dialog instances are Started : Other Dialog instance is started here.
Showing posts with label configtool. Show all posts
Showing posts with label configtool. Show all posts
Monday, March 5, 2012
Wednesday, July 20, 2011
How to Activating SAP* User in Visual Admin in SAP
Use
In emergency situations where you configured user management incorrectly and can no longer log on to any applications, or all administrator users are locked, you can activate the emergency user SAP* to allow you to log on to applications, in particular the configuration tools, and change the configuration. The SAP* user has full administrator authorizations. For security reasons, the SAP* user does not have a default password, so you must specify a password when you activate the user.
Procedure
1. Activate the SAP* user:
a. Start the config tool for editing UME
properties as described in Editing UME Properties.
Editing UME Setting:
1. Start the Config Tool by executing
\j2ee\configtool\configtool.bat.
2. In the tree, navigate to Global server configuration services com.sap.security.core.ume.service.
The list of UME properties appears.
¡ To change the value of a property:
i. Select the property in the list.
ii. In Value at the bottom of the screen, enter
the new value that you want to assign to the property.
iii. Choose Set.
iv. Choose (Apply changes).
To restore a property to its default value:
i. Select the property in the list.
ii. Choose Restore to default.
iii. Choose (Apply changes).
To restore all properties to their default values:
i. Choose Restore all to default.
3. Restart the nodes in the cluster for the changes to take effect.
b. Set the following properties:
Property Value Comment
ume.superadmin.activated true This activates the SAP* user.
ume.superadmin.password
Enter any password of your choice. This defines the password for the SAP* user.
c. Restart the Java application server.
The SAP* user is now activated. While it is activated, all other users are deactivated. You can only log on
with the SAP* user.
2. Fix your configuration as required, logging on with the user ID SAP*and the password you specified.
For example, to log on to the Visual Administrator to unlock users or create a new administrator user,
proceed as follows:
i. Start the Visual Administrator by executing \j2ee\admin\go.bat.
ii. If you have not already done so, you have to create a new connection entry in which you specify SAP* as the user name.
For more information, see Creating a New Connection Entry.
iii. In the Connect to SAP J2EE Engine dialog, select the connection entry you created and choose Connect.
iv. Enter the password you specified in the UMEproperties and choose Connect.
v. Do whatever is necessary to fix your configuration. For example, unlock all administrator users.
Similarly, you can log on to the UME administration console using the SAP* user.
3. When you have fixed your configuration, deactivate the SAP* user again.
a. Start the config tool for editing UME properties as described in Editing UME Properties.
b. Set the property ume.superadmin activated to false.
b. Restart the Java application server.
In emergency situations where you configured user management incorrectly and can no longer log on to any applications, or all administrator users are locked, you can activate the emergency user SAP* to allow you to log on to applications, in particular the configuration tools, and change the configuration. The SAP* user has full administrator authorizations. For security reasons, the SAP* user does not have a default password, so you must specify a password when you activate the user.
Procedure
1. Activate the SAP* user:
a. Start the config tool for editing UME
properties as described in Editing UME Properties.
Editing UME Setting:
1. Start the Config Tool by executing
\j2ee\configtool\configtool.bat.
2. In the tree, navigate to Global server configuration services com.sap.security.core.ume.service.
The list of UME properties appears.
¡ To change the value of a property:
i. Select the property in the list.
ii. In Value at the bottom of the screen, enter
the new value that you want to assign to the property.
iii. Choose Set.
iv. Choose (Apply changes).
To restore a property to its default value:
i. Select the property in the list.
ii. Choose Restore to default.
iii. Choose (Apply changes).
To restore all properties to their default values:
i. Choose Restore all to default.
3. Restart the nodes in the cluster for the changes to take effect.
b. Set the following properties:
Property Value Comment
ume.superadmin.activated true This activates the SAP* user.
ume.superadmin.password
Enter any password of your choice. This defines the password for the SAP* user.
c. Restart the Java application server.
The SAP* user is now activated. While it is activated, all other users are deactivated. You can only log on
with the SAP* user.
2. Fix your configuration as required, logging on with the user ID SAP*and the password you specified.
For example, to log on to the Visual Administrator to unlock users or create a new administrator user,
proceed as follows:
i. Start the Visual Administrator by executing \j2ee\admin\go.bat.
ii. If you have not already done so, you have to create a new connection entry in which you specify SAP* as the user name.
For more information, see Creating a New Connection Entry.
iii. In the Connect to SAP J2EE Engine dialog, select the connection entry you created and choose Connect.
iv. Enter the password you specified in the UMEproperties and choose Connect.
v. Do whatever is necessary to fix your configuration. For example, unlock all administrator users.
Similarly, you can log on to the UME administration console using the SAP* user.
3. When you have fixed your configuration, deactivate the SAP* user again.
a. Start the config tool for editing UME properties as described in Editing UME Properties.
b. Set the property ume.superadmin activated to false.
b. Restart the Java application server.
Subscribe to:
Posts (Atom)