Optimize Upgrade or Migration

Submitted by Rinku Hazarika, Software AG

Known Issues

Archiving in Optimize tries to access invalid tables

Reason: The error message:
[ADA.1.316] Cannot execute the SQL statement "call dbo.DATA_MGMT_PURGE_DATA". " 
(S0002/208) Invalid object name 'BAM_FACT_PERFORM_V1'." 
Invalid object name 'BAM_FACT_PERFORM_V1'.

In table 'OPERATION_PARAMETER' a few entries for tables present which do no longer exist in 9.6:

Because of which, it’s preventing the archiving from working correctly.
Resolution: Delete the above mentioned parameters from the 'OPERATION_PARAMETER' table. 

Question & Answer

KPI data from the monitored, clustered IS will not be available in Optimize (Upgrade of O4I with Clustered IS Environment)

Question: Why KPI data from the monitored, clustered IS will not be available in Optimize (Upgrade of O4I with Clustered IS Environment)?
Answer: Support for Coherence was discontinued in release 9.0.

If you are monitoring Integration Servers that were clustered using Coherence, stop monitoring them now; you will need to restart monitoring them as part of the Terracotta-based clustering solution after the upgrade as explain below:

I. Make sure all the Optimize 9.5 components are running.
II. In My webMethods, go to the Administration > Analytics > Infrastructure Components > Monitored Components page. In the Monitored Components list, see if the Available column for IS Cluster or IS Cluster Server shows a number greater than 0. If it does, proceed to the next step.
III. Click IS Cluster and then click Add Components. The Add Component Instances window lists the names of the Integration Server cluster nodes you need to remove. Copy the names to a new text file, listing each name on a separate line. For example:
a. com.wm.isextdc.IsCluster:name=is821clustertest discoveryAddress=
b. discoveryPort=39273
c. com.wm.isextdc.IsCluster:name=rdvmvaclustertest
d. discoveryAddress= discoveryPort=16477
IV. Save the text file in DOS format (that is, new line conversion) regardless of the operating system you are using (that is, Windows or UNIX). You can use any name with any extension.
V. Shut down the Analytic Engine.
VI. Open a command window, go to the 9.5_installation_directory\Optimize\analysis\bin directory, and enter this command:
a. cleanupOldClusterComponents.{bat|sh} text_file_name
VII. You will see progress messages in the command window, ending with the message Removed cluster components.
VIII. Restart the Analytic Engine.
IX. Rediscover the Integration Server 9.5 clusters you want to monitor, set up the KPIs you noted before upgrading, and restart monitoring.

Migrating of O4I assets from 8.2 to 9.5 when using a new hardware after upgrade

Question: 8.2 were installed in machine A and it was using DB 1. Optimize for Infrastructure was used to monitor the servers installed in Server A. Now 9.5 is installed in Server B and now planning to move the DB to a new host as well. Customer wants to monitor the 9.5 servers running on Server B and want to use the existing KPIs and Rules.
Deploying of assets from an 8.2 environment directly to a 9.5 is not supported
Exporting and importing rule optimize assets from 8.2 to 9.5 is not supported
Take DB clone of 8.2 DB and restore it to the new location
Install 9.5 servers by pointing to the cloned DB
Perform required file system and DB migration
Bring up your 9.5 servers (MWS, IS, Broker, Analytical engine, Infrastructure Data Collector engine)
You should be able to see all your existing assets (KPIs, Rules etc.). And there will not be any duplicate KPIs, rules etc.
OFI will still try to monitor the servers running on machine A. So you need to make the required changes so that it monitors the servers running on machine B instead of machine A. To do that:
Login to MWS
• Navigate to Application> Administration> Analytics> Infrastructure Components> Discovery
• In the Discovery page, edit the existing discovered assets and point to the correct host
• It will create a new component with hostname server B
• Navigate to Application >Administration> Analytics> Monitored component page and add the new component and delete the old component

BAM KPI migration (Dimension/Fact tables)

Overview: While defining and deploying KPI’s, it creates BAM_DIM_* and BAM_FACT_* tables to collect the information while the process instances are created.

Q1. During migration process, how should these tables be moved?
Ans. Yes, While defining and deploying KPI’s, it creates BAM_DIM_* and BAM_FACT_* tables to collect the information. Apart from the below tables, all BAM_DIM_* and BAM_FACT_* tables gets created during runtime.