SAP Basis Tech Supports

Symptom

You want to upgrade the XI PCK.
Other terms

Partner Connectivity Kit, PCK
Reason and Prerequisites

XI Partner Connectivity Kit is installed. You would like to import the current Support Package.
Solution

You must make the following adjustments:

I.) Upgrade to XI Partner Connectivity Kit 701 on IBM i / IBM DB2 for i

If you want to include the Enhancement Package stack make sure that this stack does not contain a kernel (the files SAPEXE_ .SAR and SAPEXEDB_ .SAR) and that these files are also not referenced after the download in XML.
Otherwise, you will have problems subsequently when processing these
files in the Java phase BIND_SUPPORT_PACKAGES.

II.) Checking the aii.properties.

Check whether the file aii.properties exists on the file system of the J2EE -installation under usr/sap//JC00/j2ee/cluster/server0.
If you are installing a fresh XI 3.0/7.0 PCK installation, the installer should have generated the file, and saved it in the correct location. For 7.1, this is also taken care of by the CTC template.
If you are performing a an upgrade from 3.0 to 7.0, or if you are performing a syscopy procedure you must carry out this step manually, and adjust the parameters as necessary.
(For syscopy procedure , only step I needs to be carried out.)
An example of the aii.properties is attached to this note.
If the system consists of several cluster nodes, make sure that the file ‘aii.properties’ exists on all server nodes X, from which you want to start the PCK under the following path:
usr/sap//JC00/j2ee/cluster/serverX

This also holds true if the cluster node is on another host – often referred to as the ‘dialog instance’. In such a case, please make sure that the hostname in aii.properties is also adjusted.
Pleaseappendthe list of languages through which you can logon into the PCK using this property in ‘aii.properties’
For example, for adding French one will set:
com.sap.aii.ib.client.login.languages = EN,DE,FR

III.) Changes to the properties of the J2EE “SAP XI AF CPA cache” service:

Start the Visual Administrator of the SAP J2EE Engine on your PCK-host. Select the service “SAP XI AF CPA Cache” from the path Cluster -> Server -> Services. In the “Properties” tab, assign the value “false” to the property “SLDAccess”, and the value “PCK” to the property “cacheType”.
Now save, so that the service is restarted, the changed values adopted and then restart the SAP J2EE Engine.

IV.) Changes to the properties of the J2EE “SAP XI AF Core” service.

Start the Visual Administrator of the SAP J2EE Engine on your PCK-host. Select the service “SAP XI AF CORE” from the path Cluster -> Server -> Services. In the “Properties” tab, assign the value “false” to the property “alerting.isActive” .
Now save, so that the service is restarted, the changed values adopted and then restart the SAP J2EE Engine.
For more detailed information refer note : 1156008

V.) Assignment of User Roles.

Steps for 3.0/7.0 release :
The following user roles must be assigned on the J2EE in the Visual Administrator (Server x x_ … -> Services -> Security Provider -> Policy Configurations) to the PCK user (depending on task):
1.) The role “administer” from the component sap.com/com.sap.xi.pck*aii_ib_sbeans.jar. This role allows you to access the configuration interface of the PCK.
2.) The role “xi_af_receive” from the component sap.com/com.sap.aii.af.ms.app*MessagingSystem so that you can receive messages as well as the role “xi_af_monitor” so you can archive messages.
3.) The roles “display” from the component sap.com/com.sap.xi.mdt*mdt (for the message monitor), “modify” (edit a message) and “payload” (display the payload).
4.) The role “xi_af_adapter_monitor” from the component sap.com/com.sap.aii.af.app*AdapterFramework for the status display of the individual adapters.
5.) The role “support” from the component sap.com/com.sap.xi.pck*pck. This allows you to call the link “administration” on the PCK first page; you can display and set different configuration parameters.
For security reasons, you should avoid assigning all roles to one user. Instead, distribute the roles to four users for example: pckuser with “administer”, pckreceiver with “ai_af_receive”, pckmonitor with “display” and “payload” and pckadmin with “display”, “modify”, “xi_af_adapter_monitor” and “support”.
Steps for 7.1 release :
The following user roles must be assigned using NWA.
http:: /nwa ( Operation Management -> Users and Access ->
Identity Management )
1.) Assign role “SAP_XI_PCK_CONFIG” to user “PCKUSER”
2.) Assign role “SAP_XI_PCK_COMMUNICATION” to user “PCKRECEIVER”
3.) Assign role “SAP_XI_PCK_MONITOR” to user “PCKMONITOR”
4.) Assign role “SAP_XI_PCK_ADMIN” to user “PCKADMIN”
Note :Create users if they do not exist.
Problems encountered
1.) The PCK takes an extremely long time to login and is very slow. Solution: Please look into Note: 1130572 for further information on solving this issue.
2.) The PCK launch process terminates with an error message that complains about a jar file missing.
Solution: This problem usually occurs when the server side jar cache of the PCK has not been refreshed with the new jars after the upgrade. You can manually refresh the cache by navigating to the Administration page from the PCK start page. Select ‘Java Web Start Administration’ and click on ‘Re-initialization’ of jars. This will clear the cache and bring in the new jars in the server cache.
3.) You are unable to access the PCK administration page since you get a 403 Forbidden error.
Solution: Please ensure that ‘pckuser’ (or whichever user you are using to access the administration page) has the role ‘administer’ for the component sap.com/com.sap.xi.pck*aii_ib_sbeans.jar and the ’support’ role for the component ’sap.com/com.sap.xi.pck*pck’.
4.) Adapter types description is displayed as “Unknown” in the channel
configuration dropdown.
Solution : Restart the engine.