Notes from IoT Support

The developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this blog will no longer be available. More details available on our FAQ.

with Tags: rdm

All posts

DB2 license expired after 90 days for IBM IoT CLM, RQM, RTC, RDM, JTS, RELM, IBM DOORS Next Generation – what can you do?

UtaUiAlmhain Visits (10977)

Each valid client license of IBM CLM, CLM, RQM, RTC, RDM, JTS, RELM or IBM DOORS Next Generation includes a license to run one instance of DB2 Workgroup Server Edition (excludes z/OS).

If you get a message that your DB2 license is expired you might have installed a trial license – for example a trial license for DB2 Enterprise edition).

You can remedy this by extracting the license file for the bundled DB2 Workgroup Server edition.

To do so, please follow the steps provided in the technical document: CLM, RQM, RTC, RDM, JTS, RELM, IBM DOORS Next Generation – DB2 license expired after 90 days, what can I do?

Tags: db2_license rqm ibm-iot jts iot-support clm relm rdm rtc supce licensing dng technotes

Now you can upgrade Rhapsody Design Manager from v5.0.2 directly to v6.0.1

AE91_SHINJI_KANAI Visits (8925)

If your current version of Rhapsody Design Manager (RDM) is v5.0.2, you can now directly upgrade to v6.0.1; previously you must upgrade to v6.0 first. Note that the direct upgrade process is only supported from version 5.0.2 interim fix (so called iFix) 011 or higher, so you still need to apply the latest iFix for RDM v5.0.2 prior to commencing work. Interactive User Guide was recently updated with instructions for direct upgrade from v5.0.2 to v6.0.1, you will no longer see the warning below when you select v5.0.2 as your source version. See this blog for upgrading Rhapsody Client for using with RDM v6.0.1.

Tags: iot-support supce techtips ibm-iot rdm techtip rational-rhapsody

3 Key Steps to upgrade Rhapsody Design Manager Server and Client from v6.0 to v6.0.1

AE91_SHINJI_KANAI Comments (2) Visits (12785)

Overview:

Upgrading Rhapsody Design Manager Server (RDM) is not straight forward as it often involves upgrading other CLM tools and there is no one place to obtain all migration guidance or fixes needed to complete the complicated migration process. Even worse, Rhapsody Client & Server interoperability is highly dependent on RDM and iFix versions, requiring extra efforts in keeping Client and Server compatible. This blog will break down the whole migration process for DM into 3 Key Steps and show you the direction for what to do at each steps. Also, check out this page for new features of RDM v6.0.1!!!

Step-1:
Apply iFix005 to RDM v6.0

The upgrade process to v6.0.1 is only supported from version 6.0 interim fix (so called iFix) 002 or higher. If your current version is any release of v5.x or v6.0, you must first upgrade your server to 6.0 iFix002+, and then upgrade to 6.0.1. As of this writing, the latest DM iFix is iFix005, which you can download from this page at Jazz.net. In addition, you should apply the latest CLM iFix for your JTS or other CLM applications if any are integrated. The CLM iFix includes fixes for both JTS and CLM applications. As of this writing, the latest CLM iFix for v6.0 is iFix005, which you can download from this page at Fix Central. Follow readme.txt for installation steps. Watch the 5-min video (*1) to walk through this step.

(*1)

In this video, CLM iFix002 was used instead of iFix005.

Step-2:
Migrate RDM v6.0+iFix005 to v6.0.1+iFix001

RDM v6.0.1 introduced two significant changes, they are:

1. No more VVC!!!

Starting in version 6.0.1, RDM is based on Jazz Foundation versioning instead of VVC, to be aligned with other CLM applications. The removal of VVC makes the whole DM architecture simpler and less error prone when it comes to migration, data synchronization, indexing etc. Furthermore, the simpler architecture achieves additional performance and scalability improvements.

2. Websphere Liberty replaces Tomcat Server!!!

Starting in version 6.0.1, WebSphere Liberty is provided as a default application server. Select this option if you used Apache Tomcat server in your previous CLM installation and like to migrate your previous Apache Tomcat configuration files into WebSphere Liberty.

As result of these changes, upgrade procedure for RDM has slightly changed from previous as such involving the export and import of VVC data. Read Upgrade Guide very very carefully, which now includes RDM (*2). Note that, you will be instructed to install the new RDM v6.0.1 (RDM is also delivered as part of IoT Continuous Engineering Solution package) and apply the latest iFix for applications immediately; as of this writing, RDM v6.0.1 iFix001 is available from this page at Jazz.net (*3). You will separately need to apply the latest CLM iFix (iFix001 as of this writing) for your JTS and/or any CLM applications that share the same JTS with RDM. Consult the upgrade guide.

(*2)

(*3)

Step-3:
Apply iFix001 to Rhapsody Client and DM Client Extension.

To connect to RDM Server v6.0.1+iFix001 and edit models on the server from the local client, you MUST do two things.

1. Apply iFix001 to Rhapsody v8.1.4 (Stand-alone)

Do not skip applying iFix001 or higher to your Rhapsody Client (Stand-alone)!!! If you forgot applying it, you will see Rhapsody crash when you open a model from Server due to Error:400 Illegal Unquoted Character exception (*4). Download "IBM Rational Rhapsody 8.1.4 IFix 1" from this page.

2. Install DM Client Extension v6.0.1 iFix001

You have to install Client Extension that is the exact same version and patch level with RDM server, that is v6.0.1 iFix001. If you forgot applying iFix001, you will see an error at connection (*5). Download "Rhapsody Design Manager Client Extension v6.0.1 iFix001" from this page. Grab the fix for Simulink and Import Engine if needed (*6).

If you're on Rhapsody v8.1.3 release, you need to first obtain Rhapsody v8.1.4 from Passport Advantage site or download a 90-days trial version from this page at Jazz.net and install any of 4 editions. Once you have Rhapsody v8.1.4 installed, follow the 2:30-min video (*7) to install both binaries in one go.