Tuesday, June 29, 2010 J2EE Engine : JControl & JCmon JControl JControl starts, stops, and monitors

the processes of a Java instance - primarily the server and dispatcher processes. JControl restarts terminated processes, ends hanging processes, and sends a shutdown signal to Java instances. JControl starts the JLaunch processes, which in turn start Java nodes such as dispatchers or servers. JControl starts a Java instance bootstrap process with parameters that are defined in the file bootstrap.properties (/usr/sap///j2ee/cluster/bootstrap) -> Java profiles are stored under \usr\sap\\SYS\profile\DIR_PROFILE JCmon The JCmon tool can be used to monitor the JControl process. JCmon is part of the Startup and Control Framework, and is located in the JControl/JLaunch home directory, that is, in the executable directory /usr/sap///j2ee/os_libs. JCmon can be started with the command JCmon pf=. Posted by ~SAP Consultant~ at 9:45 AM 0 comments Links to this post Labels: Netweaver Thursday, October 15, 2009 J2EE Engine : Restarting a Single Process 1. Start JCmon The system prompts you to choose a command number. 2. Choose command 5 "Restart process" (this command restarts a specified process). The system prompts to specify the index of the process that you want to restart. You can view the process indexes from the table of processes that is displayed every time you execute a command. The indexes are displayed in the first column of the table (Idx). 3. Specify the index of the process that you want to restart and confirm your choice. The JCmon restarts the specified process.

Posted by ~SAP Consultant~ at 3:50 PM 0 comments Links to this post Labels: Netweaver J2EE Engine - Checking That All Processes Are Running Procedure ... 1. Start JCmon. The system prompts you to choose a command number. 2. Choose command 11 "Process list" (this command displays the status of the processes). The result displayed on the command line will be something like this:

-----------------------------------------------------------SAP System Name : J2E SAP System : 00 MS Host : testpc-doc MS Port : 3601 Process Count : 3 PID of JControl : 3108 State of JControl : All processes running State inside MS : All processes running Admin URL : -----------------------------------------------------------|Idx|Name |Type |PID |State |Err or|Restart|Debug|Debug|Debug | | | | | | |Cou nt|Mode |Prep.|Mode |Port | |---|--------------------|--------------------|--------|--------------------|----|-------|-----|-----|------| | 0|dispatcher |J2EE Dispatcher | 2900|Running | 0|yes |no |no | 50000| | 1|server0 |J2EE Server | 3580|Running | 0|yes |yes |no | 50021| | 2|SDM |SDM Server | 3556|Running | 0|yes |yes |no | 50002| ----------------------------------------------------------------------------------------------------------------------SAP System Name : J2E SAP System : 00 MS Host : testpc-doc

The status of each process is displayed in the corresponding tables above. Posted by ~SAP Consultant~ at 3:49 PM 0 comments Links to this post Labels: Netweaver JCmon Menu options (features) The JCmon main menu provides the following functions: 0: Exit Returns back to the main menu. 1: Refresh list Refreshes the process list and the menu. 2: Shutdown instance Invokes the shutdown of the specified J2EE instance. 3: Enable process Enables and starts a process, which is switched off. (Restart == no) 4: Disable Process Stops a running process and switches off the restart flag. 5: Restart Process Restarts the specified process. 6: Enable bootstrapping on restart 7: Disable bootstrapping on restart 8: Enable Debugging Checks if the specified process is running in debug mode. If not and the process is configured for debugging, JControl will restart the process in debug mode. 9: Disable Debugging If the process is running in debug mode, JControl will restart the process and switch off the debug mode. 10: Dump stack trace

The specified process gets an event to invoke the dump of the stack trace of the Java VM. The stack trace is stored in the stderr output file in the work directory. 11: Process list Displays the status and additional information about all the processes. 12: Port list Displays a list with detailed information about the ports used by the J2EE Engine. 13: Activate debug session Activates the debug session for the specified process. To activate a debug session: 1. The process must be running in debug mode. 1. The process must be "Load Balance Restricted". 14: Deactivate debug session Deactivates the debug session. The process will be restarted or stopped this depends on the process configuration. 15: Increment trace level This increments the trace level for the developer trace file of the specified process (dev_) 16: Decrement trace level This decrements the trace level for the developer trace file of the specified process (dev_) 17: Enable process restart 18: Disable process restart ----98: Synchronize instance properties 99: Extended process list on/off Posted by ~SAP Consultant~ at 3:46 PM 0 comments Links to this post Labels: Netweaver J2EE Engine : Monitoring JCmon The JCmon is a native monitoring program, part of the startup and control framework, which can be used to:

1. Display a list of the processes 2. Enable, disable, and restart the specified processes 3. Shutdown a specified J2EE instance 4. Enable/disable debugging for a specified process 5. Dump stack trace 6. Display a list of the ports used by the J2EE Engine 7. Activate/deactivate debug sessions 8. Increment/decrement the trace level To start the JCmon, execute the jcmon script file from the /usr/sap///j2ee/os_libs directory, where is the system ID of the cluster (for example, C11) and is the instance name of the J2EE instance (for example, JC00). The instance name consists of a prefix (JC or J) and the two-digit instance number afterwards. As parameter for the jcmon script file specify the SAP instance profile: jcmon pf=/usr/sap//sys/profile/__. Example: jcmon pf=/usr/sap/C11/sys/profile/C11_JC00_testpc. Enter command '20' to display the main menu.

Posted by ~SAP Consultant~ at 3:31 PM 0 comments Links to this post Labels: Netweaver J2EE Engine : Requesting & Installing SAP License

You need a valid SAP license to log on to SAP Web AS. After installation, a temporary license is installed, you must replace it with a permanent license. Note : With a J2EE + ABAP installation (SAP Web Application Server with ABAP and J2EE to the ABAP import license (see SAP license), You can ignore this section. Before Requesting & Installing licensem SAP J2EE Engine must be installed and Visual Administrator have to be started. Procedure

1. Visual Administrator, choose Server 0 -> Services -> Licensing Adapter. You will see the system data, you need to request the license on the SAP Service Marketplace: installation number (if available) System ID, System number (if available) Hardware key News Release 2. Under the web https://service.sap.com/licensekeys you to the start page of the license key request in the SAP Service Marketplace. Here you will find all necessary information to request license keys. 3. Give in to the request your email address. The license key is provided to you via email if available. Alternatively, the license key in the SAP Service Marketplace can be downloaded. Do not make any manual changes to the license file through! To import the license, it is necessary that the file is used unchanged! 4. Select Licensing Adapter in the Visual Administrator install license from file. 5. Select the license file you received from SAP.

You can see all installed licenses of its SAP system by using the Visual Administrator choose Server -> Services -> Licensing Adapter tab Runtime -> Installed Licenses. Posted by ~SAP Consultant~ at 3:21 PM 0 comments Links to this post Labels: Netweaver Licensing J2EE Engine After installing the SAP J2EE Engine, you can sign up as a temporary license was automatically installed. You must now request for a permanent SAP license and install it. If you have installed the SAP Web Application Server with ABAP and J2EE, you use the licensing system, which came with earlier releases of SAP Web AS.

There are 2 types of licenses for SAP: permanent and temporary licenses. Permanent License How do you request a permanent license for SAP and install it on your system, under SAP Request license to install and described. Temporary License If your permanent license has expired, you can install a temporary license for quick remedies. In the Visual Administrator, choose Server 0 -> Services -> Licensing Adapter. Here you select the tab page Runtime -> General and then install subsequent temporary license. This is 28 days. Then again, you should have installed a permanent license. Note that you can not install another temporary license if the license had expired even temporarily. A newly installed license is effective until you restart the SAP J2EE Engine! It does not matter whether it is permanent or temporary license. Posted by ~SAP Consultant~ at 3:16 PM 0 comments Links to this post Labels: Netweaver Specifying the J2EE Engine Client to Use for Logon Tickets When issuing logon tickets, it is necessary to make sure that the user's ID for which the logon ticket has been issued is unique. For SAP Web AS, this includes determining the system ID and the client where the user exists. These attributes are necessary when maintaining the access control list in accepting systems and are therefore included in the user's logon ticket. When the J2EE Engine is the ticket-issuing system, its system ID is used as specified in the installation. Although the J2EE Engine does not have a client, it still needs to provide a client value to use for logon tickets so that the tickets can be accepted by other systems, for example, from an SAP Web AS ABAP. The default client for the J2EE Engine is 000, however, you can explicitly set a different value to use. The system ID and client combination must be unique when tickets are to be accepted by an SAP Web AS ABAP system. Therefore, in an Add-In installation, where the system IDs are the same, you must change the default client for the J2EE Engine (000) to a client that does not exist on the SAP Web AS ABAP system.

You can specify the configuration for logon tickets either in the UME properties or in the options for the login module CreateTicketLoginModule. The configuration to use depends on the value of the property ume.configuration.active. If you use the UME configuration, then to specify the J2EE Engine's client set the property login.ticket_client in the UME property sheet. Otherwise, set the property client in the options for the login module CreateTicketLoginModule. (The reason for these two configuration options is to provide for downward compatibility.) See the procedures below for information about checking the ume.configuration.active property and where to set the logon ticket client property. Checking the Property ume.configuration.active To check the value of the property ume.configuration.active for the login module CreateTicketLoginModule, use the Security Provider service. Check for this parameter in both the policy configurations as well as in the user store configuration. Checking the Property in the Policy Configurations 1. In the Security Provider service, choose Policy Configurations. 2. Select each template or application that uses the login module CreateTicketLoginModule, for example, the template ticket. The login module stack for this component appears. If you do not know which components use the login module, then check the login module stacks for all of the components. The table below shows the login module stack for the ticket template as it is delivered with the J2EE Engine. In this case, the option ume.configuration.active=true is set in the policy configuration for the ticket template. Ticket Template Login Module Stack Login Modules com.sap.security.core.jaas. EvaluateTicketLoginModule BasicPasswordLoginModule com.sap.security.core.jaas. CreateTicketLoginModule Flag SUFFICIENT Options {ume.configuration.active=true}

REQUISITE OPTIONAL

{} {ume.configuration.active=true}

Checking the Property in the User Store Configuration

1. In the Security Provider service, choose the User Management tab page. 2. Choose Manage security stores. 3. Select the login module CreateTicketLoginModule and choose View / Change Properties. Recommendation If the ume.configuration.active property (or any other property) is set in the policy configurations and not in the login module options in the user store, then we recommend moving the setting(s) to the user store. Reason If properties are set in the login module options in the user store, then these properties are inherited by the policy configurations that use the corresponding login module. However, if a property is set in the policy configurations, then no inheritance will take affect, even for additional properties that are set in the user store. Therefore, we recommend only setting options in the user store and not in the policy configurations. Posted by ~SAP Consultant~ at 3:14 PM 0 comments Links to this post Labels: Netweaver J2EE Engine : Post-Installation Procedures Creating a second administrator user To prevent locking the administrator in case you do change its password and forget to update the entry secure storage, we also recommend you create a second administrator user after installing the J2EE Engine. Add-In installation only: Single Sign-On using logon tickets requires a client from the ticket-issuing system. For this purpose, the J2EE Engine uses the client 000 per default. However, the system ID and client combination must be unique when tickets are to be accepted by an SAP Web AS ABAP system. Therefore, in an Add-In installation, you have to change the default client (000) to a client that does not exist on the SAP Web AS ABAP system. (SAP Web AS installation guide is available on SAP Service Marketplace at http://service.sap.com/installNW70 -> Installation.) Posted by ~SAP Consultant~ at 3:05 PM 0 comments Links to this post Labels: Netweaver

Sunday, December 28, 2008 Configuration Steps for SAP NetWeaver Administrator (NWA) As of SAP NetWeaver 04 SP Stack 12, the SAP NetWeaver Administrator (NWA) is also available to you for landscape-wide administration and central monitoring. The NWA runs as an application on the J2EE Engine and is called using the URL : http://host:port/nwa To use the NWA for central monitoring, install a Java Add-In for your CEN, if it does not already have one. Since you can use the NWA not only for central monitoring, but also for central administration, the corresponding double-stack system is referred to as the central administration and monitoring system. This system is also abbreviated to CEN If you want to use the NWA to monitor your system landscape, you need a System Landscape Directory (SLD), since information about the monitored systems is stored in the SLD for this application. We recommend that you set up an SLD on the J2EE Engine of CEN for this purpose. This SLD is known as the administrative SLD.

You need to configure and start the administrative SLD; you also need to enter all ABAP and Java systems in your system landscape into this SLD. CEN must be able to write data about the agents of the monitored systems to the administrative SLD. You need to create special connections and authorizations for this. You also need to set up a special RFC connection between the ABAP and the Java stacks of CEN. If you want to use the NWA to administer multiple Java systems, we recommend that you store the corresponding logon data in the NWA's J2EE Engine, so that you do not need to log on with a user name and password every time.

To simplify this step, the Template Installer is available in the NWA. You can use it to perform the above configuration steps more easily.

More can be found @ http://service.sap.com/nwa Prerequisites: 1) Monitored ABAP systems must be entered in transaction RZ21; 2) A CCMSPING availability agent must be installed and registered with CEN; 3) Monitored Java systems must be registered with CEN using the CCMS agent SAPCCMSR;

4) It is recommended to register the monitored ABAP instances with CEN using the CCMS agent SAPCCM4X; More Information can be found from the link below. http://help.sap.com/saphelp_nw04s/helpdata/en/3d/b5f9c2ea65c242957ee504ca4a37a9/frameset.ht m Posted by ~SAP Consultant~ at 8:54 PM 0 comments Links to this post Labels: Netweaver Wednesday, December 24, 2008 SAP Netweaver 2004s - Components of Monitoring - Global Workload Monitor The Global Workload Monitor (transaction ST03G) displays statistical records for entire landscapes and therefore allows the analysis of statistical data from ABAP and non-ABAP systems. You can use this data to analyze the workload of the monitored components in great detail. While statistics records for an ABAP system can only trace actions that are processed by ABAP components, you can use Distributed Statistics Records (DSRs) to trace actions that are processed by, for example, the J2EE Engine, ITS, and TREX. You can even do so across component boundaries. Posted by ~SAP Consultant~ at 2:08 AM 1 comments Links to this post Labels: CCMS and Monitoring, Netweaver SAP Netweaver 2004s - Components of Monitoring - Standalone Log Viewer With the standalone log viewer, you can monitor any J2EE Engine or Java application log files, even if the J2EE Engine is not functioning correctly, cannot be started, or is not available on the system to be monitored. The standalone log viewer contains any number of servers and one client:

The server of the standalone log viewer monitors log files that are registered with this server. It must be installed on every host of the J2EE system landscape. The various servers function independently of each other.

The client of the standalone log viewer connects to one or more servers of the standalone log viewer and displays the contents of the log files. You only need to install the client once in the J2EE system landscape.

For general information about the standalone log viewer, see the SAP NetWeaver Library under SAP NetWeaver -> SAP NetWeaver by Key Capability -> Application Platform by Key Capability -> Java Technology in SAP Web Application Server -> Administration Manual -> Supportability and Performance Management -> Logging -> Log Viewer -> Standalone Log Viewer. Posted by ~SAP Consultant~ at 2:06 AM 0 comments Links to this post Labels: CCMS and Monitoring, Netweaver SAP Netweaver 2004s - Components of Monitoring - Operating System Collector SAPOSCOL The operating system collector SAPOSCOL is an independent program that runs in the operating system background. It functions independently of the SAP instances, exactly once per monitored host. SAPOSCOL collects data about operating system resources, including: * Usage of virtual and physical memory * CPU utilization * Utilization of physical hard disks and file systems * Resource usage of running processes Posted by ~SAP Consultant~ at 2:04 AM 0 comments Links to this post Labels: CCMS and Monitoring, Netweaver SAP Netweaver 2004s - Components of Monitoring - CCMS Agents CCMS agents are independent processes with an interface using RFC to a central monitoring system and an interface to the shared memory. These agents have the following properties: A connection to CEN using RFC, to ensure greater downtime security and general availability Use of the push technology to optimize performance when reading and writing monitoring attributes and alerts Inclusion of the operating system collector SAPOSCOL to monitor processes at operating system level. Connection to systems with no SAP NetWeaver Application Server Monitoring of any log files

There are various CCMS agents, including: SAPCCMSR - Monitoring of components on which no SAP ABAP

instance is active, such as the J2EE Engine or SAP IPC SAPCCM4X - Monitoring of SAP ABAP systems as of SAP Basis 4.X Posted by ~SAP Consultant~ at 2:01 AM 0 comments Links to this post Labels: CCMS and Monitoring, Netweaver SAP Netweaver 2004s - Components of Monitoring - SAP NetWeaver Administrator (NWA) The SAP NetWeaver Administrator (NWA) unifies the most important administration and monitoring tools both for Java and for ABAP systems in a new, browser-based user interface. The most important advantages of the NWA are: You no longer need to switch between different tools for administration, troubleshooting, and problem analysis of your entire SAP NetWeaver system landscape. There is now a central administration tool available to you landscape-wide for both Java and ABAP systems for starting and stopping instances, checking configuration settings and logs, and monitoring error-free functioning of components. The interface follows the current guidelines for interface design, is easy-to-use, task-oriented, and complete. By using Web Dynpro, it runs in a normal browser. The interface allows seamless navigation to other SAP NetWeaver administration tools (User Management Engine, in the future also System Landscape Directory, Adaptive Computing). For Java, the NWA represents the crossover from various expert tools to an integrated, simple, and clear solution. The NWA also completes the integration of the data sources for monitoring. For ABAP, the NWA represents the crossover from many different expert transactions, some of which are difficult to use, to integrated, centrally available information.

The NWA is delivered for the first time for SAP NetWeaver 04 SP Stack 12. A more advanced version is delivered with SAP NetWeaver 2004s. It is intended to deliver an advanced version with SAP NetWeaver 2004s. The NWA will also be continually further developed in later releases, and extended with additional administration and monitoring functions