Description:
Description:
============

This hotfix is cumulative. It provides a utility called "nodeutil" that
manages application components and node configuration from a Node's
runtime. The utility supports an interactive mode as well as a
non-interactive (scripted) mode.

This utility can be used for performing removing components from the
runtime or for updating the dependencies for a component.

When using this utility for removing components, use ONLY in those
cases where attempts to undeploy or force undeploy an application
using the Administrator UI or CLI does not remove all the components
from the Node runtime. A typical sequence for its use might look like:

1. Undeploy or Force Undeploy an application using Administrator UI or
   CLI. This step should remove application components from a Node's
   runtime.
2. Delete an application using Administrator UI or CLI. This step
   removes information about the application and its components from
   the Administrator's database.
3. If any of the above steps fail, use Force Delete using the
   Administrator UI or CLI to remove information about the application
   and its components from the Administrator's database. After that
   use the nodeutil tool to remove those components from the Node's
   runtime.

When using this utility for updating dependency metadata for components,
use it only when the component instance is not visible from administrator.
When a component instance is not visible from administrator, any upgrade
of dependent components would leave the component instance in 'Waiting
for dependency' state. A typical sequence for it's use might look like:

1. Find the URI of the component dependency before and after the upgrade.
2. Shutdown the runtime node. This can be done from Admin UI, CLI or tibcohost
   command.
3. Use the nodeutil tool to update the dependency for the component.
4. Start the node. Verify that the component is no longer in 'Waiting for
   dependency' state.

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

Environments:
=============

This hotfix applies to the following products and versions:
  
   - TIBCO ActiveMatrix Service Grid 3.0.x (+ Hotfixes)
   - TIBCO ActiveMatrix Service Bus 3.0.x (+ Hotfixes)
   - TIBCO ActiveMatrix Service Grid 3.1.x (+ Hotfixes)
   - TIBCO ActiveMatrix Service Bus 3.1.x (+ Hotfixes)
   - TIBCO ActiveMatrix BPM 1.1.x (+ Hotfixes)
   - TIBCO ActiveMatrix BPM 1.2.x (+ Hotfixes)
   - TIBCO ActiveMatrix BusinessWorks Service Engine 5.9.x (+ Hotfixes)

Download Instructions:
======================

You can download this HotFix from the TIBCO Product Support FTP server using your eSupport username and password, at
    
   ftp://support-ftp.tibco.com

Once you have successfully logged into the server, you will find the hotfix packages under

   available_downloads/ActiveMatrix/ActiveMatrixServiceGrid/3.x.x/TIB_amx_3.x.x_hotfix-nodeutil4

Closed Issues:
==============

Listed below is a summary of updates included. Please refer to the hot fix readme document for any additional information.

================================================================================
Closed Issues in 3.x.x_hotfix-nodeutil4 (This Release)

AMX-11652: Create HOWL log reader utility to discover active transactions in HOWL log.

           Specifying incorrect parameters to the howlLogReader command sometimes results in
       an error "TIBCO-AMX-TOOLS-NODE-UTIL-000029: Unable to complete transaction log scan
           due to exception
           Caused by: org.objectweb.howl.log.LogConfigurationException:
           LogFileManager.open: unable to obtain lock on file". The error then repeats persistently
           even on specification of the correct parameters. The solution is to restart nodeutil
           and then use the correct parameters.

AMX-11607: add validatePlatformFeatureVersion command.

AMX-11261: add command to validate and repair various machine model defects.

AMX-10807: Node utility fails to remove components.

================================================================================
Closed Issues in 3.x.x_hotfix-nodeutil3 (This Release)

AMX-11143
AMXBPM 1.3 upgrade leaves some component instances in 'Waiting for dependency'
state.
updateDependency was added to the nodeutil for handling this issue.

================================================================================
Closed Issues in 3.x.x_hotfix-nodeutil2

PER-1297
Delete policy set for an application when the application components
are removed from the Node runtime.

================================================================================
Closed Issues in 3.x.x_hotfix-nodeutil

AMX-9592
Introduce a nodeutil tool to remove application components from a
particular Node's runtime.

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

Attachments:
============

- TIB_amx_3.x.x_hotfix-nodeutil4_readme.txt

References:
===========

LBN1-CFWZV5 - What is "nodeutil" utility for TIBCO ActiveMatrix(R) release 3.x.x?. When should I use the utility in my ActiveMatrix installation?.
LBN1-CG1N4J - What are the cleanup utilites for TIBCO ActiveMatrix(R) BPM release 1.x.x?. When should I use these utilities in my ActiveMatrix installation?.

TIBCO ActiveMatrix(R) Platform hotfix "TIB_amx_3.x.x_hotfix-nodeutil4" is now available.

Product: TIBCO ActiveMatrix Service Grid Version: 3.1.5 OS: All --------------------