IBM BPM, V8.0.1, All platforms > Administer applications and processes in the runtime environment > Manage installed snapshots > Manage orphaned tokens

Changing the security policy

If you are upgrading from an earlier version of IBM BPM, you might need to configure the security policy before you move or delete a token.

Ensure the 100Custom.xml exists in the directory PROFILE_HOME\config\cells\ cell_name\nodes\ node_name\servers\ server_name\process-server\config.

If not, create the file. See Manage IBM BPM configuration settings with the 100Custom.xml file.

In version 8.0, the security policy has been set by default to support the moving and deleting of orphaned tokens. If you are upgrading from earlier versions, you might need to configure the security policy in the following way before you can move or delete an orphaned token.

Procedure

1. Stop IBM Process Server.
2. Open the original server configuration file (99Local.xml) and your local configuration file (100Custom.xml) in text editors.
   • PROFILE_HOME\config\cells\ cell_name\nodes\ node_name\servers\ server_name\process-server\config\system\99Local.xml
   • PROFILE_HOME\config\cells\ cell_name\nodes\ node_name\servers\ server_name\process-server\config\100Custom.xml

3. In the 99Local.xml file, locate the following line and copy it to your 100Custom.xml file:

   <portal>
   <adhoc-reroute-enabled merge="replace">true</adhoc-reroute-enabled>
   </portal>

4. In the 100Custom.xml file, edit the value of the property, as shown:

   <adhoc-reroute-enabled>false</adhoc-reroute-enabled>

5. Save the 100Custom.xml file and restart the server.

Manage orphaned tokens

Related concepts:
Manage process applications

Related tasks:
Manage orphaned tokens with a policy file
Manage tokens using the REST API Client and Process Inspector