Last steps for PI configuration

So, it's been a long time but now i thought of finishing with the last steps of configuring usage type PI, and in future posts walk you through some simple PI scenarios..


We last configured the RFC Java destinations; moving on...:


Step 7

The next step is to create a HTTP connection in the Java environment required for Process Monitoring Infrastructure .

a. This is done easily by going to Cluster --> Server --> Services --> Destinations in the Visual Administrator tool.
b. In the HTTP node of the Runtime tab create a New destination named "pmistore". (lowercase does matter). You must enter at least the following details :

- the URL : http://[pi_host]:[ABAP_Port]/sap/bc/spi_gate (usually the port is 8000; you can find the port in tcode SMICM under Goto --> Services)
- select Basic Authentication
- username : PIRWBUSER and its password
- Save


Step 8

1. On your Integration Server host, call transaction SXMB_ADM.

2. On the Integration Engine: Administration screen, choose Integration Engine Configuration.

3. Choose Edit and Change Global Configuration Data.
4. In the Global Configuration Data box, select Integration Server as Role of Business System, and leave the other fields empty.
5. Save your settings.


Step 9

I hope you didn't close the Visual Administrator, because now you must go to Cluster --> Server --> Services --> Deploy and after checking the Application checkbox, restart the application com.sap.aii.af.cpa.app to trigger the SLD self-registration of the Central Adapter engine

Step 10

Now we must import PI content; this step isn't covered by the configuration wizard also and i think it is quite useful to know. You need of course an SAP_XI_ADMINISTRATOR or SAP_XI_CONTENT_ORGANIZER role to import / export content for PI.

XI content can be found on the SAP marketplace under Downloads --> Support Packages and Patches --> ESR content (XI content). Files are usually ZIP files and always contain both previous objects and the changes and enhancements delivered in the support package.

a. Download the files and unzip them; the actual export files have the extension .tpz

b. Copy the export files into the import directory for the Integration Repository (\xi\repository_server\import).

c. Open the Integration Builder start page by calling it either from your user menu or with transaction SXMB_IFR, choose Integration Repository, Tools --> Import design objects to import the XI content.

After a successful import, the Integration Builder moves the imported TPZ files into the directory /xi/repository_server/importedFiles.

Step 11

If you have configured corectly PI, then execute transaction SLDCHECK and it should show nothing but green.


============

PI configuration step error

I discovered a minor problem when configuring manually an SAP system with usage type PI. On the second step of the configuration, Configuring Workflow for BPM, you must execute tcode SWF_XI_CUSTOMIZING. When trying to perform execute for the activity "Schedule Background Job for Deadline Monitoring", the system displays the error message "Error within method CL_SWF_ADM_JOB_FACTORY=>GET_INSTANCE->" . Then, the system does not schedule the relevant job and the status icon displays a red cross. This happens because that activity is obsolete and was not removed from automatic customizing by mistake; so you must :

1. execute transaction SM30

2. maintain the view SWFCTASK.

3. Delete all the rows for "CL_SWF_CST_DEADL_SERVICE_JOB" (usually there are two)

4. Don't forget to save;

Now, in SWF_XI_CUSTOMIZING you should be able to get green crosses everywhere, and move on to the next configuration step...

PS: these instructions are mentioned in SAP Note 1117735

Basis J2EE server problem after installing on x64 systems

I encountered this error recently when i installed NW 7.0 (2004s) on Windows Server 2003 x64 with MSSQL. The system seemed to be working fine, instances were green; but as soon as i tried to open a browser and log on to SLD, i got an error that the Page cannot be found. Surprisingly, when i returned to sapmmc console to check the status, now the J2EE server wasn't green anymore, it suddenly stopped and restarted.

After some digging around on all sorts of forums and checking the logs (dev_dispatcher) i saw that the Java error was returning code 666 (ironic, isn't it :P) and soon discovered that on all SAP installations on 64bit operating systems, you MUST modify the Java Heap size parameters using the J2EE config tool;

The parameters you need to modify for your instance must follow some rules; every information needed is found in SAP Note Number 723909.