SAP PI Net weaver Administrator tasks for PI developers.

Start/Stop Adapter Services

1. http://hostname:port/nwa
2. Go to Operation Management  -> Systems-> Start & Stop -> Java EE Services -> XPI Adapter: *
3. At the bottom, there will be push button to start/stop the service.

Adapter service Properties

1. http://hostname:port/nwa
2. Go to Configuration Management  -> Infrastructure -> JAVA system properties -> Services
3. Select Adapter server  XPI Adapter:*
4. Choose “ Extended Details” at the bottom to display the properties of the adapter

Certificate Key store

1. http://hostname:port/nwa
2. Go to Configuration Management  -> Certificates and Keys
3. Select the Key store view
4. The Entry Import dialog appears.
5. In Select Entry Type, choose X.509 and browse to the location of the exported entry. Here you have three choices, depending on the type of entry you want to import:

• • a.       X.509
  • b.      PKCS#12 Key Pair
  • c.       PKCS#8 Key Pair

     6.      Choose Import

Adapter JAVA consumer Thread

1.      http://hostname:port/nwa

2.      Go to Configuration Management  à Infrastructure àJAVA system properties à Services

3.      Select the service “XPI Service: AF Core”

4.      Choose “messaging.connectionDefinition” Property

Using the “name=global” entry some global template settings are defined. For each Adapter type these defaults can be individually overwritten, by adding additional configuration entries, according to the following syntax:

(name=<AdapterTypeIdentifier>, messageListener=localejbs/AFWListener, exceptionListener=localejbs/AFWListener, pollInterval=<a>, pollAttempts=<b>, Send.maxConsumers=<c>, Recv.maxConsumers=<d>, Call.maxConsumers=<e>, Rqst.maxConsumers=<f>),

The example below adds a new property set for the RFC Adapter. This is appended after the global AFW entry,

(name=global, messageListener=localejbs/AFWListener, exceptionListener=localejbs/AFWListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=5, Rqst.maxConsumers=5), (name=RFC_SAP Help Portal, messageListener=localejbs/AFWListener, exceptionListener=localejbs/AFWListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=8, Recv.maxConsumers=8, Call.maxConsumers=12, Rqst.maxConsumers=12)

JMS/JBDC Connection Properties

1.      http://hostname:port/nwa

2.     Go to Configuration Management  -> Infrastructure -> JAVA system properties -> Services

3.      Select the service “XPI Service: Messaging System”

4.      Choose following properties for verifying JDBC connection

• • messaging.connections
  • messaging.connectionParams
  • messaging.jdbc

5.      Choose following properties for verifying JMS connection

• messaging.jms.providers

JAVA Adapter Queue Parallelism

1.      http://hostname:port/nwa

2.      Go to Configuration Management  -> Infrastructure -> JAVA system properties -> Services

3.      Select the service “XPI Service: Messaging System”

4.       Add or modify the property “queueParalellism.maxReceivers” based on the maximum JAVA consumer thread settings.

RFC Destinations

1.      http://hostname:port/nwa

2.      Go to Configuration Management  à Security Management

The available destinations appear in the Destinations List. If you select a destination, its details are shown in the lower pane.

3.      To create a new destination, choose Create.

The General Data screen appears.

4.      Enter the following information in the corresponding fields:

Hosting system: <system where the destination is located>

Destination Name: <Name>

Destination Type: RFC

5.      Choose Next.

The Connection and Transport Security Settings screen appears.

6.      Enter the parameters for the connection to the ABAP server (hostname and system number or system ID and logon group if load balancing is used). If the destination is a registered RFC server program, enter the corresponding gateway’s hostname and service.

7.      If you use SNC to secure the connection, then enter the SNC parameters in the SNC section (active/inactive, quality of protection, and the target server’s SNC name).

8.      Choose Next.

The Logon Data screen appears.

9.      Enter the authentication information to use. You can use either a predefined technical user or the current user for the connection. If you use a technical user, enter the user’s data in the corresponding fields. If you use the current user, then specify whether a logon ticket or an assertion ticket should be used for authentication.

10.  If you need to access the ABAP repository, then enter a destination that contains the corresponding connection information in the Repository Connection section.

11.  Choose Next.

The Specific Settings screen appears.

12.  If the destination uses a pooled connection, select Pooled Connection Mode in the Pool Settings and enter the pool connection parameters accordingly.

13.  If a SAProuter is used for the connection, then enter the SAProuter connection information in the Advanced Settings.

14.  Save the data.

Log Viewer

Log Viewer allows you to view all log and trace messages that are generated in the whole SAP NetWeaver system landscape. These log records assist you to monitor and diagnose problems.

To access the tool,

1.      http://hostname:port/nwa

2.      Go to Troubleshooting  -> Logs and Traces  ->  Log Viewer

JCO RFC Provider

The JCo RFC Provider Service processes ABAP to Java requests, and dispatches the calls to Java applications. So, seen from an ABAP system, it provides an RFC destination. Technically, the service is based on the JCo (SAP Java Connector). In order to receive calls from ABAP, JCo Servers are started and registered at the gateways of the ABAP systems. The configuration of these JCo servers is done here.

To access the tool,

1.      http://hostname:port/nwa

2.      Configuration Management -> Jco RFC Provider

Message Prioritization on the ABAP Stack

Log on to your Integration Server, call transaction SMQ2, and execute. If you are running ABAP proxies on a separate client on the same system, enter ‘*’ for the client. Transaction SMQ2 provides snapshots only, and must therefore be refreshed several times to get viable information.

It’s highly recommended to use message prioritization on the ABAP stack to prevent delays for critical interfaces.

Heap Dumps Analysis

1.      http://hostname:port/nwa

2.      Go to Troubleshooting  -> Advanced Troubleshooting  -> Heap Dump Analysis

Generating Heap Dumps

1.      Choose Generate Heap Dump. A dialog window appears.

2.      Select a server process (node) and choose OK.

3.      The new heap dump is displayed in the table.

     Archiving Heap Dumps

• • • Select the relevant heap dump.
    • Choose Archive.
    • A confirmation dialog window appears. Choose OK.
    • In the Archive Size column, a progress bar is displayed showing the archiving process in percent (%)

     Downloading Heap Dumps

• • • Select the relevant heap dump.
    • Choose Download.
    • Save the downloaded content in your local file system

Removing Heap Dumps and Heap Dump Archives

1.      Select the relevant heap dump.

2.      Choose the Remove or Remove Archive button, accordingly.

3.      A confirmation dialog window appears

House-Keeping

1.      If your file system is out of memory because of too many heap dumps, a Delete column appears with a red indication.

2.      To delete old and obsolete heap dumps, select them and choose Remove.

Analyzing Thread Dumps

1. http://hostname:port/nwa
2. Go to Troubleshooting  -> Advanced Troubleshooting  -> Thread Dump Analysis

Triggering Thread Dumps

     For a Long Running Thread

1.      In the Availability and Performance work center, choose System Overview.

2.      Go to Threads and see if a long running thread is detected.

3.      If yes, from the Long running context menu, choose Trigger Thread Dump.

4.      The Thread Dump Analysis tool is opened.

5.      Choose Generate Thread Dump.

6.      From the dialog window, select Only Server Processes with Long Running Threads and choose OK.

7.      The archive file appears in the table. It has the Contains Red Threads column selected.

On a Particular Server Process

1.      Choose Generate Thread Dump.

2.      Choose Custom, select a server process and then choose OK.

3.      The archive file appears in the table.

On All Server Processes

1.      Choose Generate Thread Dump.

2.      Choose All Server Processes and then choose OK.

3.      The operation may take several minutes depending on the number of server processes.

The archive file appears in the table.

Analyzing Thread Dumps

1.      To see and resolve the problem, select the relevant thread dump and choose Download.

2.      Save the ZIP file to your local file system.

3.      Use the Eclipse Memory Analyzer tool to open the ZIP file and to analyze the dump.

4.      As a solution, you can decide whether to stop the application or to write a customer message.

Removing Thread Dumps

1.      Open the Thread Dump Analysis function.

2.      From the table, select the thread dump you want to delete.

3.      Choose Remove.