MIM 8.5 SR 1 has been released. Be sure to read the complete release notes for complete details. I have provided some of the important new features, changes and resolved issues.
Important Information, New Features, and Changes in this Release:
Process Monitor - enhanced navigation menu, Auditor views, and Fixit Summary view
The navigation menu has been restructured. Process Monitor functions are now grouped into five top-level categories: Welcome, Node and Service Management, Process Management, Managed File Transfer, and Administration. The Auditor views and Fixit Summary views have been enhanced. The command bar within the views contain new commands, such as "View Status" in the Fixit summary view or "Share" within the Auditor Summary view. Some views may now be customized by the user. Columns may be selected or deselected for display. The data presented may be sorted by the desired column.
ACTION REQUIRED: Refer to the MIM Process Monitor Reference for information on the navigation menu changes and enhanced views.
Process Monitor - Progress and cancel feature added
The Auditor view now provides the ability to display the progress of certain transfers and to cancel these transfers, if necessary. The progress feature provides a progress indicator that displays the number of bytes and the percentage of the file that has been transferred. The cancel option, available in the progress detail display, allows the user to fail the transfer or to send it to Fixit. The progress and cancel feature is only available for transfers that meet specific criteria: The transfer must run in immediate mode, must be within the progress file size threshold, and the ftf command line option "-progress false" must not be specified.
ACTION REQUIRED: No action is necessary to implement this feature. MIM Administrators should refer to the File Transfer Service topic "Setting Threshold and Interval for Progress and Cancel" in the MIM System Administration Guide for information on the settings related to the progress and cancel feature. Process Monitor users should refer to the MIM User's Guide and MIM Process Monitor Reference for information on using the progress and cancel feature.
Process Monitor - Status Filter Management
The Status Filter Management feature within the Process Monitor provides the ability for multiple status filters to be created, stored, and then shared among other users/roles. The MIM Administrator may control which roles have the ability to create and share filters. For example, the administrator may grant a role the ability to create filters but prohibit the users of that role from sharing the filters with others. Users of another role may have the right to view the Auditor status data but not have the right to create a filter or edit the unsaved filter.
ACTION REQUIRED: The default access control policy for Status Filter Management grants the Create Filters and Share Filters rights to the Super User role. The roles Operator and Requestor have the Create Filters right but not Share Filters. The role Viewer does not have either right; however, users of that role may use filters that have been made available to them through the share filter command. Customization of roles and rights may be performed after the service release install is completed. Refer to the MIM System Administration Guide to learn more about the administration of the roles and rights within the Process Monitor. The creation and sharing of filters should be performed after the service release install is completed. Refer to the MIM Process Monitor Reference and MIM User's Guide for more information on using the views associated with this new feature.
Process Monitor - Fixit enhancements
The Fixit feature within the Process Monitor has several new features available. Multiple Fixit requests, regardless of the failing activity, can be restarted at once using the new "resume" activity, available in the Next Activity selection. Resume results in restarting each request at the failed step. Direct navigation between Status Auditor detail view and Fixit view is now available. From within the Fixit Summary view, the user may select a Fixit entry and then click the View Status command to view the detail status of the request within the Auditor view. From within the detail view of the Auditor view, the user may select the "Go To Fixit" link that displays when the ControlCenter activity is expanded. The Go To Fixit links directly to the Fix Request Form where the request may be either terminated or modified, if necessary, and resubmitted.
ACTION REQUIRED: Review the MIM Process Monitor Reference and MIM User's Guide for more information on the Fixit enhancements.
Process Monitor - JDBC connectivity now used for all database access
All database access performed by the Process Monitor is now performed using JDBC. The Status Query Server is no longer used to retrieve status data for the standard auditor view. The DataDirect for JDBC driver is packaged with MIM. The driver is installed and configured for use during the service release install. Note: The Status Query Server is still available and supported.
ACTION REQUIRED: No action is necessary to implement this feature. Refer to the MIM System Administration Guide for information on the Process Monitor configuration.
Process Monitor - Added support for legacy Auditor instances
A legacy Auditor instance may be created when it is necessary to view status for a pre-MIM 8.5.1 or MIM for CICS installation. The legacy Auditor instance uses the Status Query Server of the external MIM enterprise to retrieve status data from that enterprise's database. The legacy Auditor displays status and filters as available in older versions of MIM. The STATUSFILTER table is required for use with legacy Auditor instances. The table must reside in the Process Monitor's database.
ACTION REQUIRED: If a legacy Auditor instance is needed in an existing MIM enterprise, ensure the MIM database contains the STATUSFILTER table. The table should exist if the database migration script is executed. If a new MIM database is created in place of performing the database migration (not recommended), then the table will not exist. Refer to the MIM Process Monitor Reference for information on creating an Auditor instance. Refer to the Enterprise Server - Service Release Install instructions in the MIM Installation Guides for information on migrating the MIM database.
Status Data and Process Monitor - Added support for timestamps to be stored and displayed in UTC time and with milliseconds or microseconds
Timestamps within the MIM status database can now be stored in UTC (GMT, Zulu) or local time. The MIM Administrator can also now control the timestamp precision by specifying seconds, milliseconds, or microseconds. The MIM Administrator can control the format in which the status data timestamps display within the Auditor views. Timestamps can now display to the millisecond or microsecond precision. Note: - The timestamp precision selected for display in the Process Monitor is dependent on the level of precision specified in the Status Loader. - The database must support the selected timestamp precision.
ACTION REQUIRED: The default settings retain the same base time (local) and timestamp precision (seconds) of prior releases. Refer to the Status Loader chapter in the MIM System Administration Guide for information on specifying the base time and precision for status timestamps. Refer to the Process Monitor topic "Setting Auditor Date Format" in the MIM System Administration Guide for information on specifying the display format of status timestamps.
HP NonStop - Authorization Level Security mode identify or verify
The Authorization Level Security modes identify and verify are now supported on HP NonStop. The new XMScript ftfpwdreset.xms must be run during the configuration steps of switching to mode identify or verify.
ACTION REQUIRED: To implement Authorization Level Security mode identify or verify, refer to the Security chapter within the MIM System Administration Guide.
Status Summary Query Servlet - obsolete
In previous releases, the Status Summary Query servlet serviced requests from the Process Monitor to retrieve historical status data for the History report view. The servlet ran within the XMScript Workflow Servlet Engine. The Status Summary Query servlet has been replaced with direct JDBC access to the MIM status database. The servlet is now obsolete and has been removed from the product.
ACTION REQUIRED: No action is necessary.
Process Monitor - Auditor Status view now reports requests resubmitted from Fixit as - in progress
When a transfer is resubmitted through Fixit, the Process Monitor summary will show the transfer's state as in progress (or completed, depending on timing). Previously, the transfer's state continued to be shown as in Fixit, while the transfer was in progress.
ACTION REQUIRED: Communicate this change to all users of MIM which create, submit, and/or monitor the status of transfer requests. Refer to the MIM User's Guide and MIM Process Monitor Reference for additional information on the Auditor views and transfer states.
Process Monitor - Auditor Status details for transfers involving destination lists
Status details for the receive activity of in progress transfers, that use destination lists, will now show the destination queue manager (DQM and destination path (DPATH). For transfers that are in progress, or possibly stalled, this facilitates determining which destination is experiencing the delay as the auditor now displays the DQM:DPATH while the receive activity is in progress. Previously, the DQM:DPATH did not display until the receive completed.
ACTION REQUIRED: Communicate this change to all users of MIM which create, submit, and/or monitor the status of transfer requests. Refer to the MIM User's Guide and MIM Process Monitor Reference for additional information on the Auditor views and transfer states.
Install type - name change for z-i5 Management Server
The install type that was previously named z-i5 Management Server is now named Management Server for z/OS. This install type is still supported on UNIX and Windows. The Management Server for z/OS contains the Process Monitor and is used when the Enterprise Server resides on z/OS.
ACTION REQUIRED: No action required.
MIM Registry - Database policy location
The database policies are now stored in the MIM Registry location: NodeInfo/nodename/Database.
ACTION REQUIRED: The Database.xml policy is relocated to this location during the Service Release install. No user action should be necessary. However, if there is any custom code that accesses the database policy using a hard-coded path name, the code will need to be updated. XMScript programs should use the XMDirectory class to access Registry artifacts. Refer to the XMScript Programming Reference for information on the XMDirectory class.
Managed File Transfer - Message-to-File change in behavior for no message found condition
Change in behavior For Message-to-File transfers that encounter a no message found condition, an exception is now thrown. In previous releases, the transfer completed by creating a zero byte file.
ACTION REQUIRED: Communicate this change of behavior to all users of MIM which create, submit, and/or monitor the status of transfer requests. Refer to the MIM User's Guide and Developer's Guide for additional information on the Message-to-File feature.
Managed File Transfer - z/OS record format FA, VA, and U are now supported
Managed File Transfer now supports the z/OS record formats Fixed-block ANSI (FA), Variable-blocked ANSI (VA), and undefined-length (U). This support is also available in XMFile and XMScript class XMPDynalloc. Note: With record format U, Load Modules/DLLs can be transferred; however, the transferred version is not executable and must be relinked in order to make it executable
ACTION REQUIRED: Refer to the MIM User's Guide for information on specifying record format FA, VA, or U for a transfer request. Refer to the MIM Developer's Guide for information on setting record format FA, VA, or U in the policy. Refer to the MIM XMScript Programming Reference for information on specifying record format FA, VA, or U with the class XMPDynalloc.
Managed File Transfer - new and changed options
The managed file transfer expiry option now supports a maximum value of 34560 minutes (24 days). The recordmode (Record Mode in the Process Monitor) option is now available for transfer requests. This option processes files one record at a time. The use of this option is recommended over the logical option.
ACTION REQUIRED: Refer to the MIM User's Guide and MIM Process Monitor Reference for information on the options.
Directory Monitor Service - new parameters
The parameters listed below have been added to the Directory Monitor Service configuration file (DirectoryMonitorService.xml). recoveryQueueInUseWait recoveryQueueMaxRetries
ACTION REQUIRED: Refer to the Directory Monitor Service chapter in the MIM System Administration Guide for information on the new parameters.
File Transfer Service - new or changed parameters
The parameters listed below have been added to the File Transfer Service configuration file (XMOFTS.xml / XMOFTS\_Client.xml). cancelCheckIntervalSeconds controlMessageExpiryImmediateSeconds progressFileSizeThreshold progressReportIntervalSeconds putBackTimeDelayMilliseconds putBackTimeThresholdSeconds stripspaces true|false timeout shutdownOnTimeout
ACTION REQUIRED: Refer to the File Transfer Service chapter in the MIM System Administration Guide for information on the new parameters.
Process Coordinator - new parameter
The parameter listed below has been added to the Process Coordinator configuration file (Coordinator.xml). useQueueCaching
ACTION REQUIRED: Refer to the Process Coordinator chapter in the MIM System Administration Guide for information on the new parameter.
Process Monitor - new parameters
The parameters listed below have been added to the Process Monitor configuration file (ControlCenter.xml). administration auditorDateFormat auditorDateFormatPrecision defaultAuditor nodeAndServiceManagement
ACTION REQUIRED: Refer to the Process Monitor chapter in the MIM System Administration Guide for information on the new parameters.
Registry Service - parameter timeoutSeconds now supported for TCP/IP client
The timeoutSeconds parameter in Client.xml is now supported for clients when the Registry Service connectivity is via TCP/IP. Previously, this parameter only applied to WebSphere MQ connectivity.
ACTION REQUIRED: Refer to the Registry Service chapter in the MIM System Administration Guide for information on the timeoutSeconds parameter.
Status Loader - new parameters
The parameters listed below have been added to the Status Loader configuration file (XMStatus.xml). timestampBase timestampPrecision
ACTION REQUIRED: Refer to the Status Loader chapter in the MIM System Administration Guide for information on the new parameters.
Product Database - table and index changes
The tables AUDITORFILTER and AUDFILTERSHAREXREF have been added to support the new Status Filter Management feature. The SYSTEMUSER table now contains two additional columns MFTFILTERID and PMFILTERID. The STATUSFILTER table is now only used for legacy Auditor instances. The REFERENCE table index for REFERENCEID has been changed to be unique. The index will be drop and created during the database migration.
ACTION REQUIRED: The Database Administrator will need to run the migrate SQL script that has been provided with the product distribution. The database must be migrated prior to applying the service release to the Enterprise Server. Consideration should be given to the space requirements of adding the new tables as well as the new columns to the existing tables. Depending on the database vendor, a reorganization utility can need to be executed, after the database is migrated, to reclaim space from fragmented pages. The Database Administrator and MIM Administrator should refer to the topic "Migrate the product database" in the MIM UNIX, Windows, or z/OS Installation Guides for more information on the database migration.
Windows system registry changes
The required Windows registry entries for MIM are now stored under Metastorm\\Metastorm Integration Manager. The previous registry entries under CommerceQuest\\enableNet BPI are removed when the service release is installed. The log control parameters are now defined in the Windows Registry during the install. The parameters were not previously defined automatically during the install; administrators had to manually define the entries to override the default values.
ACTION REQUIRED: The Windows System Administrator will need to reapply any customizations made to the product-related registry entries. If the log control parameters were previously modified from the default values, the modified values need to be reapplied after the install of the service release. Any other entries that were manually defined will need to be redefined. During the install of the service release, the existing registry entries under CommerceQuest\\enableNet BPI are exported to a file under the directory named install, of the location where MIM is installed.
XMScript - Class: XMQDescriptor – added methods expiry() and setExpiry()
The XMScript MQ Wrapper class XMQDescripter has two new methods: expiry() and setExpiry(). The new methods provide the ability to work with the expiry value in tenths of a second.
ACTION REQUIRED: Refer to the XMScript Programming Reference for information on the new methods.
XMScript - Method fixAsString added
The XMScript standard methods has a new method: fixAsString. The new method provides the ability to return a double precision floating-point number as a string.
ACTION REQUIRED: Refer to the XMScript Programming Reference for information on the new method.
##
Issues Corrected in this Release
All hotfixes from release 8.5.0, and prior releases, are included in this release. Refer to the release notes for each prior release for a list of the issues fixed in that release.
SR-02062008-0019 (PF1268) Message-to-file transfer results in a zero byte file when there are no messages on the queue. The sample MQ policies have been updated to include the option onRead. This option will now cause an exception to be thrown when no messages are found.
SR-04282008-0003 (PF1414) ftf and ftfping ignored the -lqm parameter in some cases. The -lqm was ignored as long as -sqm and -dqm were specified. This has been resolved.
SR-09022008-0014 (PF1610) Immediate mode transfers, with numerous batches, fail when the syncpoint limit is reached. When this condition occurs, the File Transfer Service on the sender side generates the message "syncpoint limit reached".
SR-01202009-0005 (PF1830) File Transfer Service receiver-only instance experiences high CPU utilization. On Nodes where there is a high rate of send operations and very few receive operations, the receiver-only instance cycles through the control message queue repeatedly, looking for messages containing receive operations. Two new parameters are introduced to assist in controlling the amount of CPU utilization the receiver-only instance consumes: putBackTimeDelayMilliseconds putBackTimeThresholdSeconds The parameters are defined in the FTS configuration file XMOFTS.xml and XMOFTS\_Client.xml. Refer to chapter File Transfer Service in the MIM System Administration Guide for information on these parameters.
SR-04092008-0013 (PF1867) When the Directory Monitor Service restarts, in some cases it may encounter a WebSphere MQ error opening the recovery queue for exclusive access. The service will then wait and retry opening the queue. The time between retries and the number of retries was not configurable. Now these settings are configurable through the two new parameters: recoveryQueueInUseWait recoveryQueueMaxRetries The parameters are defined the Directory Monitor Service configuration file DirectoryMonitorService.xml. Refer to chapter Directory Monitor Service in the MIM System Administration Guide for information on these parameters.
SR-02252009-0021 (PF1870) Transfers writing to /dev/null would fail with an errno 22 (EINVAL) on some systems. SR-09302008-0005 In some circumstances, an error in activity scripts cause the Coordinator to fail.
SR-04022009-0004 (PF1903) A long-running immediate transfer receives a WebSphere MQ error (2195 - MQRC\_UNEXPECTED\_ERROR) at the end of the transfer.
SR-05222009-0005 (PF1924) Transfers using the destination list option do not show the destination queue manager (DQM) or destination path (DPATH) in the auditor data until the receive has completed. For transfers that are in progress, or possibly stalled, it is not possible to see which destination is experiencing the delay. The auditor will now display the DQM:DPATH while the receive activity is in progress.
SR-03162009-0008 (PF1926) When older versions of the product initiate file transfers from Directory Monitor, the transfer request results in an error due to a missing WfDescriptor.userIdentifier in the workflow XML.
SR-06182009-0006 (PF1966) File transfers to Windows UNC paths (\\\\server\\share\\directory\\file) result in an error.
PF2007 xmosyspm fails executing operating system commands on some platforms.
PF2152 Disabling pass identity context results in an error sending data.
