Migrate CCM application from one server machine to another with the same database server in Enterprise deployment topology using WAS
Arun K Sriramaiah 2700076GE8 Visits (1609)
How to migrate a CCM application from one server machine to another with the same database server in Enterprise deployment topology using WebSphere Application Server (WAS).
Example: A distributed environment where we have 5 server machines.
1st server machine for IHS,
2nd server machine for the database,
3rd server machine for DCC + RS,
4th server machine for JTS+RM+CCM and
5th server machine for LQE.
Expectation: CCM and RM are in the same server machine. How to move the CCM application to a new server machine?
Please find the procedure below referencing with the above scope of the requirement as an example.
1) Backup Conf
2) Install RTC in New Server
4) Restore the conf
5) Re-configure IHS for new RTC server.
6) Make sure you have the right JVM configured for the RTC applications.
Note: Two applications sharing the same JVM, needs more JVM to be set.
7) Set the new path to the indices folder in the team
Any feedback or suggestion based on specific scenario and your experience is appreciated.
AcdntlPoet 2700019V2G Visits (8979)
Five keys to successful cloud migration - Moving your business to the cloud helps you focus on your customers and bring new offerings to market in hours instead of months. Yet the journey to the cloud is often bumpy, with half of all migration projects failing. (*1, Worldwide Cloud Infrastructure Services Market Share, Q3 2015)
Romain_Barth 2700076HKB Visits (8380)
You have multiple DOORS databases to organize you DOORS projects.
There is no documentation or feature to do that task.
This can do done via DXL
AcdntlPoet 2700019V2G Visits (10214)
Many developers are familiar with IBM's Configuration Management Version Control (CMVC) system. Some might question whether it's worthwhile to migrate to a newer lifecycle management platform. While it is possible to use CMVC to coordinate tasks and workflow throughout the development cycle, CMVC's relatively simple two-tier architecture lacks many of the features of Rational Team Concert. In addition to the basic version control and management features in CMVC, Rational Team Concert offers continuous builds, iteration planning, and process templates, which make it easy to configure and manage various work item types and workflows.
Migrate your CMVC workflow to Rational Team Concert, Part 1: Set up and configure your migration path with CMVC-RTC Connector Plugin 2.3 - This tutorial is for developers and managers currently using CMVC who are ready to migrate to Rational Team Concert. We'll walk through the complete migration path, including tips for working around synchronization issues between the two platforms for an optimal migration. [Read more...]
Migrate your CMVC workflow to Rational Team Concert, Part 2: Configure the Defect/Feature Importer to migrate CMVC work items to Rational Team Concert - The CMVC-RTC Connector Plugin includes several tools useful for synchronizing CMVC and Rational Team Concert™, including the Defect/Feature Importer and CMVC-Rational Team Concert SCM Importer. In Part 1, you installed and set up the CMVC-RTC Connector 2.3 plugin on your RTC Eclipse client, then prepared your RTC server and client environments for migration. Here in Part 2, you'll begin migrating work items and source code from CMVC to Rational Team Concert. [Read more...]
Migrate your CMVC workflow to Rational Team Concert, Part 3: Extract and import your source code to Rational Team Concert - Moving source code from your current and previous CMVC projects is the final stage in migrating your software development lifecycle to Rational Team Concert™. Learn how to configure the CMVC-Rational Team Concert SCM Importer to safely and efficiently extract your project source code, then import it to your Rational Team Concert client repository. See Part 1 for instructions to install and setup the CMVC-RTC Connector Plugin 2.3. See Part 2 if you need help configuring the Defect/Feature Importer to migrate CMVC work items to Rational Team Concert. [Read more...]
AcdntlPoet 2700019V2G Visits (7380)
Guide to Git for Rational Team Concert users - If you're a user of Rational Team Concert then you know it's a robust, well integrated source code management system. But that doesn't mean it's the right fit for every software development project or team. We've written this article for Rational Team Concert users like us, who want to learn about Git or will be using Git for new projects. We compare the basic and advanced features of Git and Rational Team Concert, so you can see what they have in common and where they differ. We also look at how some common Git flows translate to similar source management patterns in Rational Team Concert. Finally, we point out some pitfalls to avoid when migrating from Rational Team Concert to Git.... [Read more...]
AcdntlPoet 2700019V2G Visits (7682)
Guide to Git for Rational Team Concert users - This article is for users of Rational Team Concert who want to learn more about Git. Find out how these two powerful source control systems differ in terms of capabilities, concepts, and commands, then get tips for successfully migrating a project workflow to Git.
Migrate your CMVC workflow to Rational Team Concert, Part 1: Set up and configure your migration path with CMVC-RTC Connector Plugin 2.3 - Configure the CMVC-RTC Connector Plugin to synchronize work items and source code between CMVC and Rational Team Concert.
Migrate your CMVC workflow to Rational Team Concert, Part 2: Configure the Defect/Feature Importer to migrate CMVC work items to Rational Team Concert - Configure the CMVC-RTC Connector Plugin's Defect/Feature Importer to successfully migrate CMVC work items to Rational Team Concert.
Migrate your CMVC workflow to Rational Team Concert, Part 3: Extract and import your source code to Rational Team Concert - Configure the CMVC-Rational Team Concert SCM Importer to extract and import your source code to Rational Team Concert.
JeffLong 270005B0Q4 Visits (9235)
With the changes delivered in IBM Tririga Platform 3.5.1 there is now a better way to track changes to objects in Tririga and a new naming convention that has been introduced for Object Labels and Revisions.
Here is a great link providing information on this change for Tririga Platform and additional links to related resources:
JeffLong 270005B0Q4 Visits (10100)
Planning for a new install or migration of an existing IBM Tririga install can be a complicated endeavor because there are so many different possible configurations for the IBM Tririga n-Tier architecture. Below are some links that will help you with your planning.
This is a lot of information to go through, but taking the time to review this information during your planning phase of your install or migration will allow you to make informed decisions based on your intended use of the IBM Tririga product and plan accordingly.
Sizing recommendations for planning migration of data from Rational DOORS to Rational DOORS Next Generation
paulellis 270001KTVW Visits (11092)
Are you considering migrating your data from Rational DOORS to Rational DOORS Next Generation(RDNG)?
Are you looking for guidance and best practice before you begin to be successful first time?
If so, then your starting point is definitely the detailed guidance on developerWorks on how to Migr
New Sizing and Best Practice Guide on Jazz.net's Deployment wiki
Since the developerWorks article was published, we realized that more detailed sizing information was required prior to executing the migration of data packages from DOORS 9 to RDNG. We collated pertinent sizing information from the Rati
There are significant improvements to the import timings with RDNG 6.0.2 release, so please refer to this article if you are evaluating an existing or future migration as this could indeed be an influencing factor.
The document details:
Sizing Guidelines for Rational DOORS Next Generation 6.x
Recommendations on the maximum sizes of your modules, projects and repositories so as to maximize your success when importing your packages and working in the future within RDNG.
The considerations for hardware are simplified from guidance published elsewhere in the Deployment wiki, but here they are explained within the context of how to plan for your new world.
Guidance on how to convert your Rational DOORS modules prior to migration
Invariably there will be modules and projects within DOORS 9 which will not match up to the guidance prescribed for RDNG. Use this section to understand how to easily manipulate your data before migrating.
What if the data to be migrated exceeds the recommendations?
The guidance is clearly aimed for the general use cases and is very much our strongest recommendation.
It is understood that there are very large enterprise requirements management estates out there. It is recommended that you contact IBM if this applies to you.
AcdntlPoet 2700019V2G Visits (9059)
Migrate an application from Azure to Bluemix - Bluemix is an implementation of IBM's Open Cloud Architecture, leveraging Cloud Foundry to enable developers to rapidly build, deploy, and manage applications and services. Although Microsoft Azure, another popular PaaS platform, shares quite a few similarities with Cloud Foundry, several elements still need to be addressed when porting Microsoft Azure applications to IBM Bluemix.
This tutorial will take you step-by-step from creating a Node.js app on Azure and then migrating that app onto IBM Bluemix; it will also give you the key differences between Microsoft Azure and IBM Bluemix from a developer's point of view. [Read more...]
AcdntlPoet 2700019V2G Visits (11093)
Migrating data from IBM Rational DOORS to IBM Rational DOORS Next Generation- With the release of IBM Rational DOORS 188.8.131.52 and IBM Rational DOORS Next Generation V6.0.1 the migration has been optimized, now automatically creating a global type system and artifact types in IBM Rational DOORS Next Generation, considering the commonalities of the type system defined in modules within DOORS, as well as links relationships. In addition, you can now incrementally migrate a project, and the two applications will automatically maintain and update link relationships with every incremental migration.
Migration is not interchange of data where data can go from one tool to another and possibly back again. Migration is a one-way move from Rational DOORS to Rational DOORS Next generation, with traceability back to the source.
Using a migration package, migration can include one or more modules and can be incremental, migrating a little at a time, and only what you need. The current version of modules is migrated along with internal external and OSLC links, OLE objects, pictures and so forth.
The history of the migrated data is not migrated however, the migration creates links in Rational DOORS Next Generation that link back to the corresponding records in Rational DOORS.
AcdntlPoet 2700019V2G Visits (10549)
Migrate data from Rational DOORS to Rational DOORS Next Generation- Kim Letkeman, Senior Technical Staff Member, IBM and Martin Henderson, Development Manager, IBM, lead you through planning and implementing a DOORS migration project.
Plan and execute a migration project from IBM® Rational® DOORS® to IBM Rational DOORS Next Generation. This article provides a list of migration terms and definitions (as opposed to interchange) and describes the phases and tasks involved when moving active data into a Collaborative Lifecycle Management environment.