Central Cluster Configuration
SIDNumber 0 for DEV, 1 for QAS Sysnr.: 00, 01 for DEV; 10, 11 for QAS
ABAPInstance: D<sysnr>, DVEBMGS<sysnr>
Visual Administrator
1-1 Start the Visual Administrator Tool.
1-1-1 Double click on G:\usr\sap\<SID>\DVEBMGS<ABAP instance number>\j2ee\admin\go.bat
1-2 Create a new Connection
1-2-1 Choose New in the pop-up window Connect to SAP J2EE Engine
Field Name Value
Display name <SID> J2EE_Admin by Dispatcher Lookup method Connection to a dispatcher node
1-2-2 Choose Next
2
Transport Layer Default
1-2-3 Choose Save 1-3 Log on as Administrator
1-3-1 Double click on the <SID> J2EE_Admin entry.
1-3-2 Enter the password (enjoy) 1-3-3 Click on Connect
1-4 Which are the ID numbers of the instances and nodes in your system and with which ABAP instance are they related?
1-5-1 Select the node in the left tree and you will see and Info tab with information on the node on the right panel.
1-5-2 Open the JControl trace file at:
G:\usr\<SID>\<ABAPInstance>\work\dev_jcontrol
Find the Worker nodes section to find the nodes associated with that particular ABAP instance
ABAP Instance <InstanceID> Node Type <NodeID>
DVEBMGS<sysnr> 37030
For the rest of the exercise use the Java Instance associated with the central ABAP Instance.
1-4 List all the Managers that are not in the Dispatcher and Server nodes ApplicationThread Manager is only in Server nodes
ConnectionsManipulator is only Dispatcher nodes
1-5 Find information about these managers
1-5-1 Go to http://help.sap.com → Search Documentation on Area SAP NetWeaver, Application SAP NetWeaver, Release 04
1-5-2 Enter “ApplicationThread” → Narrow by BACKGROUND Info-Class and Select “ApplicationThread Manger”
1-5-3 This manager supplies the threads in which client applications’ source code is executed. It provides a set of properties for starting and managing client threads in the Java Virtual Machine. This manager runs on servers only.
1-5-4 In the left hand side tree, under click on the Connections Manipulator Manager”
1-5-6 This manager is responsible for managing client connections to the cluster. It provides a set of properties for managing the pools where the TCP connection objects are stored. The Connections Manipulator Manager runs on dispatchers only
4
1-6 Which Data Sources are configured in the JDBC Connector Service of your J2EE Engine and how many free connections do they have left?
1-6.1 The only JDBC connector is in the server node (which is the only process that connects to a DB)
1-6.2 On the left tree go to Server → JDBC Connector 1-6.3 On the right panel choose Runtime tab → Datasources
1-6.4 There is only one data source called SAP<SID>DB (the default datasource) 1-6.5 In the monitoring tab you can see 2 free connections of a maximum of 10
(20% available).
1-8 Check the Telnet Service port and change it to 50088 for DEV and 51088 for QAS with the Visual Administrator using the local properties of the node.
1-8-1 To find the correct Telnet Port of the dispatcher you can have a look to the
“System Info” page with the J2EE_Admin user:
http://<full qualified DNS name>:50000 for DEV http://<full qualified DNS name>:51000 for QAS
1-8-2 Check the Service opening a Telnet connection to that port. Open a command port and execute telnet localhost 50008 for DEV or telnet localhost 51008 for QAS
1-8-3 Navigate to the Telnet Provider Service on the Dispatcher and the Server nodes. Only the Dispatcher one is configured to listen on port 50008. The Telnet service on the Server node is not been using
1-8-4 Select the property Port of the Telnet Provider Service on the Dispatcher and edit its value to 50088 for DEV or 51088 for QAS.
1-8-5 Click on Update and then on Save Properties.
1-8-6 Restart the Telnet Service on the Dispatcher node
1-8-7 Refreshing the System info page should update the change.
The Dispatcher trace also logs the open telnet ports at:
G:\usr\sap\<SID>\<ABAPInstanceID>\work\dev_dispatcher Look for “Telnet Port”.
Shell Console
2-1 Log on to the Shell Console with an administrator user
2-1-1 execute in a command prompt telnet <hostname> <custom port> where
<custom port> is 50088 for DEV and 51088 for QAS.
2-1-3 Log on with Administrator and password provided by your instructor 2-2 Which commands are available?
2-2-1 Type MAN to see the available commands and commands groups:
ADMIN, SYSTEM and TELNET 2-3 List all active Cluster Elements.
2-3-1 use the LSC to get and overview of the nodes in the current instance
Node ID
Dispatcher <Instance1ID>00 Server <Instance1ID>50 Dispatcher <Instance2ID>00 Server <Instance2ID>50
2-4 Use the GET_FREE_CONN command of the DBPOOL group of the server node to find the free available DB connections of the DB pool.
2-4-1 Jump to the Server node of the J2EE Engine: JUMP <InstanceID>
2-4-2 Add the DBPOOL commands group: ADD DBPOOL
2-4-3 Ask for the free connections of the DB pool : GET_FREE_CONN SAP<SID>DB (you can also use GET_DS to get the available datasources)
6
Config Tool
3-1 Connect to the default database with the Config Tool
3-1-1 Start the config tool on the server: G:\usr\sap\<SID>\ DVEBMGS<ABAP instance number>\\j2ee\configtool\configtool.bat
3-1-2 Once the tool is started you are already connected to the default database 3-2 Check the Local and Global custom/default properties of the Dispatcher Telnet
Service.
3-2-1 Click on the Telnet Provider service of your instance dispatcher.
Property Values
Global custom blank Global default 2323
Local custom 50088 for DEV, 51088 for QAS Local default 50008 for DEV, 51008 for QAS
3-3 Change the Telnet port of every dispatcher of every instance of the system to 50089 for DEV or 51089 for QAS.
3-3-1 Click on the Telnet Provider service of one dispatcher of your System (.
3-3-2 Select the Local property Port and click on Restore to Global 3-3-3 Click on the Telnet Provider service of the global dispatcher.
3-3-4 Select the Port property and edit its value to 50089 for DEV or 51089 for QAS.
3-3-5 Press SET then APPLY CHANGES and confirm the information popup.
3-3-6 Go the Visual Administrator, check that the Telnet Port value of the appropiate Dispatcher hasn’t change yet, and Restart the Dispatcher node.
3-3-7 After the restart of the Dispatcher check the Telnet port is 50089 for DEV or 51089 for QAS.
3-4 Check the Local and Global custom/default properties of the Telnet Service of the Dispatcher node in the Config Tool.
3-4-1 Click on the Telnet Provider service of the instance dispatcher.
Property Values
Global custom 50089 50089 for DEV or 51089 for QAS.
Global default 2323 Local custom Blank Local default Blank
3-5 Modify the Max Heap Size of the JVM of any server node in your Java instance 3-5-1 Go to the Servers General tab of your instance, increase the Max heap size
(in MB) value to 333.
3-5-2 Click Apply Changes and confirm both information pop ups (do not restart the instance yet)
3-6 Add a new node. Write down the new node ID, the name of the node and the path associated with the binary files. Finally check the existence of the new node 3-6-1 Select your instance in the right tree of the config tool (or one of its
components) and click on the Add Server button 3-6-2 Confirm the information pop-up
3-6-3 The log pop-up shows the information asked:
Property Values
Name Server 1 0_<InstanceID>
Node ID <InstanceID>51
Path G:\usr\sap\DEV\DVEj2ee\server1 3-6-5 Apply Changes and Restart the instance.
3-6-6 To check the existence of the new node, check the System Info page.
3-7 What’s the Max Heap size of each server node?
3-7-1 You can read it in the Config tool, General tab of the selected node. Or looking for the –XMx parameter in the JVM propertoes of the System Info Page:
8
Node ID Max Heap Size
<InstanceID>50 333 Mb
<InstanceID>51 333 Mb
Offline Configuration Editor
4-1 Start the config tool in the server box.
4-1-1 You can start it directly with a script:
G:\usr\sap\<SID>\JC00\j2ee\configtool\offlinecfgeditor.bat 4-1-2 Or from the Config Tool: Switch to Configuration Editor button.
4-1-3 Or from the Configuration Adapter service in the Visual Administrator 4-2 Write down the Global/Local custom/default values for the Port property of the Dispatcher Telnet Service and the path of the PropertySheet that contains it. Try with the instance you have been working during the previous exercises and with the instance that you haven’t used.
For example if you have been only using the Java instance associated with the Central Abap Instance of the DEV System (Java instance number 3703000) you should find the following Property Sheetes and values:
Editor Path Property Values
Global custom 50089 Cluster_data/dispatcher/
cfg/services/PropertySheet telnet Global default 2323 Local custom 50108 Cluster_data/dispatcher/
ID15769700/services/PropertySheet telnet Local default 2323
SDM GUI
5-1 Verify that the SDM Server is running 5-1-1 In the Web info page
5-1-2 Connecting to the http port of the SDM Server: http://hostname:50019
5-2 Start the SDM GUI:
5-2-1 Execute: G:\usr\sap\<SID>\JC00\j2ee\SDM\program\RemoteGUI.bat 5-3 Connect to the SDM Server
5-3-1 Click on the Connect to the SDM Server button 5-3-2 Use the password provided by your instructor (sdm) 5-3-3 Use the standard port 50018
10
5-4 What’s the Port number for Admin-Communication?
5-4-1 In the Repository Æ Configuration you’ll find an entry showing 50017 for DEV and 510017 for QAS as the Admin port.
5-5 Add the CustomerEAR.ear archive in
N:\setup\ATP_Web_AS_6.40_TC_Track\TADMJ1\WAS_Admin_Tools to the deployment list and find information about the vendor and the software type of the application.
5-5-1 Go to the deployment tab.
5-5-2 Select Hello.ear file provided by your instructor.
5-5-3 Add an archive to the list with the Add SCD/SDA to the Deployment list (Local file Browser).
5-5-4 You can right click of the SDA to be deployed to find out that the vendor is sap.com and that the software type is J2EE (it will be deployed against the J2EE Target System)
5-5 Deploy the CustomerEAR application, but be sure that it stops if an error occurred.
5-5-1 Check the settings option:
5-5-2 Choose Next to Go to step 2/4.
5-5-3 Choose Next to go to step ¾ 5-5-4 The SDA is ready for deploy 5-5-5 Choose Next to start.
5-5-6 Confirm after the deployment is finish correctly
5-6 Did the deployment switch off the J2EE engine after the deployment?
5-6-1 In the Log tab you’ll find the information. The SDM Server didn’t change the previous status of the J2EE Engine. So if the engine was online it should be still online. (In some cases the deployment has to be done with the Engine offline, so the SDM Server might need to change the state of the J2EE Engine).
5-7 Execute the application.
5-7-1 open the following URL: http://<hostname>:<httpPort>/Hello