meshIQ Platform Manage release notes: v11.0.3 hot fix for multiple platforms

• WGS_11.0.3.1.pkg -- Workgroup Server Expert
• webapps\manage.war -- Manage (Navigator) war files (11.0.3.5)
• webapps\manage-server.war -- Manage (Navigator) war files (11.0.3.5)
• webapps\secure.war -- Secure (Navxwsm) war files (11.0.0.7)
• webapps\secure-server.war -- Secure (Navxwsm) war files (11.0.0.7)
• nsqcmace.jar -- IIB/ACE Connection Manager (11.0.3.1)
• nsqcmems.jar -- Tibco EMS Connection Manager (11.0.3.1)
• nsqcmkafka.jar -- Kafka Connection Manager (11.0.3.1)
• nsqcmmq.jar -- MQ Java Connection Manager/Agent (11.0.3.1)
• nsqcmsolace.jar -- Solace Connection Manager (11.0.3.1)
• nsqcmrabbitmq.jar -- RabbitMQ Connection Manager (11.0.3.1)
• WGSRP-11.0.0.pkg -- Workgroup Server Resource Pack
• AP_IBMMQ-11.0.1.pkg -- MQ plugin for WorkGroup Server
• AP_IBMMQRP-11.0.1.pkg -- MQ plugin for WorkGroup Server Resource Pack
• nsqcmace.properties.sample -- IIB/ACE CM sample properties file
• nsqcmems.properties.sample -- Tibco EMS CM sample properties file
• nsqcmkafka.properties.sample -- Kafka CM sample properties file
• nsqcmmq.properties.sample -- MQ Java CM sample properties file
• nsqcmsolace.properties.sample -- Solace CM sample properties file
• nsqcmrabbitmq.properties.sample -- RabbitMQ CM sample properties file

Installation overview

1.     Stop all Nastel processes (including CEP and Domain Server).
2.     Back up the %APWMQ_HOME% directory and existing database tables.
3.     Place Manage_11.0.3.zip in the installation directory (%APWMQ_HOME%).
4.     Unzip the file.
5.     Extract contents 'here', under %APWMQ_HOME% replacing existing content.
6.     Run pkgman to install the latest WGS Expert package
   1.      if a new install, install additional packages such as resource packs, scheduler, experts
7.     Run nsqjdbcmk to upgrade your database tables
8.     Copy the war files from the webapps folder to the Tomcat webapps folder.
9.     Restart Nastel processes
10.     Finalize any setup for WGS operation, including configuration of WGS, REST API, and scheduler

IMPORTANT

This installation requires the meshIQ platform v11.0.x core components to be installed first.

 When upgrading from a version prior to 10.1.x, you will need to review the connection definitions. See this FAQ for details: Why do I have workgroup server definitions that begin with GEN_ ?

In Summary, 10.1.x and higher move the management of Workgroup server connections from a user task to an administrator task. However, since existing definitions may have various attributes, a first step after
upgrading is for an administrator to review the generated ones (names start GEN_), rename them and clean up any that are not required.

If upgrading to Scheduler 1.11 to a later version and you want to preserve currently scheduled jobs, a manual SQL statement must be run. Please contact your Support Representative for help with this step.

Fixes

Hot fix 3

Manage HTML WebGUI 11.0.3.5

NV-128: sorting objects in viewlet not resetting with 'default table sorting'
NV-174: Some entries in request history don't have origin information
NV-193: Getting Manager name twice in Manager, Channel, Topic attribute in EMS display schema settings.
NV-208: Not getting Messages while importing the Exported Text file
NV-209: Expanding user settings colors causes errors

Workgroup Server 11.0.3.1

NV-257: Change how we log discovery started/stopped per qmgr
NV-258: object status refresh for MQ subscriptions sends wrong parameter
NV-270: Maximum Browse Limit changes are not saved
NV-280: If discovery starts and doesn't finish, WGS never tries to run discovery on node again
NV-281: Solace objects are not shown immediately after creating using WGS Rest API.
NV-309: DailyTask runs immediately
NV-310: AgentNode.theKey can be corrupted and accessing it throws NPE

WGS REST 11.0.3.1

NV-213: BUG - IBM MQ Authority Record return HTTP 201 for success and failures
NV-232: If there are no auth records for an object, rest response does not include authRecs[] in response.
NV-308: Inconsistency - Object Already exists not following the same convention
NV-317: WGS RestAPI all PCF responses 2085 will return as 404 response

Solace Administration 11.0.3.1

NV-207: Solace message handling needs to be optimized
NV-274: Solace errors should return complete SEMP Response

Kafka Administration 11.0.3.1

NV-190: timeout issues while browsing kafka msgs

EMS Administration 11.0.3.1

NV-288: EMS Queue current depth is not cached by server when browsing messages

Hot fix 2

Manage HTML WebGUI 11.0.2.3

NV-15: Put message action repeats itself after a timeout
NV-25: Navigator security
NV-39: Unable to create dashboards and viewlets connecting to DB2 ZOS
NV-46: Exception causing to repeat api request
NV-76: Unable to create queue using zos Agent
NV-79: Use sessions so GUI doesn't have to login multiple times
NV-85: Queue status window does not display queue depth for zOS qmgr via remote connection
NV-114: Upon Log-in multiple authorization calls to wgs
NV-145: Not showing up Queue and Channel attributes in EMS Display Schema Settings.
NV-183: Shared storage support for Kafka messages

Workgroup Server Expert 11.0.2.4

NV-48: MQ channel status being misreported
NV-79: Use sessions so GUI doesn't have to login multiple times
NV-87: Connection String information is not shown completely if it is more than 48 characters in navigator QMGR viewlet.
NV-97: Optimize Event SQL when they are unlimited
NV-129: Kafka partition result list includes consumer offsets when system filter is not checked
NV-133: WGS RestAPI improvement to send IMB MQ object operation by qmgr only on first active node
NV-173: Shared storage support for Kafka messages
NV-181: InquireChl and InquireChlNames should return XmitQ details

Kafka Administration 11.0.2.2

NV-56: Kafka messsage handling needs to be opitimized
NV-169: nsqcmkafka: NullPointer on kafka messages browse
NV-188 nsqcmkafka needs to support browse count MMS_UNLIMITED (-1)

EMS Administration 11.0.2.1

NV-113: CM for EMS Improvements to discovery and message management