Importing Permissions 

Use

This topic describes how to import permissions to a portal after you have exported the ACL structure from the source portal (see Exporting Permissions).

The permissions of each object declared in the XML are only processed if the object already exists in the portal, otherwise it is ignored. The import mechanism behaves as follows:

·        The current permission settings for objects in the portal, which are declared in the XML file, are deleted.

·        The current permission settings for objects in the portal, which are not declared in the XML file, are not deleted.

 

Prerequisites

·        XML file containing the ACL structure exported from a source system.

·        The target portal is populated with the correct content.

 

Procedure

...

       1.      If you are working in a cluster environment, do the following:

                            a.      Stop all the dialog instances and server nodes in the cluster. Do not stop the central instance.

                            b.      Make sure that there is only one dispatcher node and one server node running on the central instance of the J2EE Engine.

       2.      Copy the initialPermissions.xml file you generated on the source system to the following folder on the target system:

·         Windows:

<installation drive>:\usr\sap\<SAP J2EE instance name>\JC<instance number>\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\system\xml\acl

·         UNIX:

/usr/sap/<SAP J2EE instance name>/JC<instance number>/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl

§         A safety mechanism in the portal prevents uploading more than once an XML file with the name initialPermissions.xml. If you attempt to do so, the file will not be processed and will remain on the target system in the folder you copied it to.

If you want to subsequently upload additional permission-based XML files, you need to first rename the file so that it does not contain initialPermissions as the prefix.

§         In a cluster environment, you only need to copy the XML file to the central instance. The remaining server nodes and dialog instances in the cluster are updated automatically.

       3.      Restart the J2EE Engine on the target system.

In a cluster environment, restart the J2EE Engine in all the cluster nodes. Upon restart, the J2EE Engine synchronizes all cluster nodes and automatically sets up the XML script on each node.

 

Result

Upon restart, the target system is updated according to the ACL structure in the initialPermissions.xml file.

After the content of the script has been integrated into the target system, the XML file is given the .bak.suffix. For example: initialPermissions.xml.bak.