================================================================================
Closed Issues in 3.3.0_hotfix007 (This release)
This hotfix contains fixes that apply to the following types of installations:
- Administration
- Runtime Host
- TIBCO Business Studio
PER-2000
This refers to a fix, made in Hotfix-006, related to the premature removal of
policies for TIBCO ActiveMatrix BPM user applications when they were upgraded.
This fix resolved the issue for newly performed application upgrades after the
application of Hotfix-006. With this Hotfix, it is now possible to recover the
prematurely deleted policies for applications that were upgraded prior to the
Hotfix-006 such that normal functionality is restored for the older running
versions of those applications. To repair the policies for existing applications,
execute the provided Admin CLI repair script, as a one-time task. The Admin CLI
script sample files are installed at:
<TIBCO_HOME>/administrator/3.3/samples/
- repair_policies_build.xml
- repair_policies_data.xml
The repair policies script can be used in 3 ways:
1. Run the repair action for all applications only on specific nodes within a
specific environment. This option is enabled by default in the CLI script.
2. Run the repair action for all applications on all nodes within a specific
environment.
3. Run the repair action only for specific applications on all target nodes
where those applications are distributed to.
To run the repair action with minimal down time, option (1) above is the most
useful when you have the applications distributed to two or more nodes, allowing
you to run the repair action on one node at a time. You can switch the option
by uncommenting sections in the CLI sample, both in the build and data files.
NOTE: After the repair action completes, a node restart is required for the
repaired policies to take effect.
Below are steps to run the repair policies script:
1) Copy files from <TIBCO_HOME>/administrator/3.3/samples/ to
<CONFIG_HOME>/admin/<enterprise>/samples/
- repair_policies_build.xml
- repair_policies_data.xml
Edit the copy of "repair_policies_data.xml" and change 'BPMEnvironment' and
'BPMNode' to the desired environment and node names.
2) Copy "admin-scripts-base.xml" from <TIBCO_HOME>/administrator/3.3/samples/
to <CONFIG_HOME>/admin/<enterprise>/samples/.
Edit the copy and replace @@TIBCO_HOME@@ with the <TIBCO_HOME> path.
3) Run "ant -f repair_policies_build.xml" and wait for the action to complete.
4) Restart the affected nodes.
There are some errors logged in the node log after running the repair
script. These are expected and can be ignored:
Error 1)
[ERROR] [] com.tibco.amx.cf.logger.lifecycle - TIBCO-AMX-CF-000028:
Error processing command file "..../work/NodeConfigurations/rda1415922167985-6.zip".
....
TIBCO-AMX-CF-000035: Cannot add component "....." because a component with the
same URI is already registered.
Error 2)
[ERROR] [] com.tibco.amx.governance.agent.core.PolicySetMessageHandler -
TIBCO-OGS-GA-900270: Failed to add policy document.
Detailed Message: TIBCO-OGS-GA-900269: Add Policy Sets task failed.
Policy Set Id: ..., Detailed Message:
TIBCO-OGS-GA-900572: Merge Failed on Governed Object: uri==urn:amx:BPMEnvironment/...
These errors occur because the policy repair script reconstructs and deploys
all policies for the application, with no knowledge about which policies had
been damaged earlier. Deploying a policy that already exists will produce the
errors above, and they can be ignored since the policy was already intact.
================================================================================