How to migrate/recreate old domain data to a new domain.

Products	Versions
TIBCO Administrator	-
Not Applicable	-

Description

Description:
The only way would be to recreate the domain and then reimport the applications and users. The steps for the activity are listed in the Resolution section of this KB.

Issue/Introduction

Resolution

Use the following procedure to migrate an old (File/DB based) domain to a new (File/DB based) domain. Using the procedure, you create an administration domain that uses a File/DB based for domain storage and add machines to the domain. After exporting applications and ACLs from the old (file/DB based) domain, you import the same to the newly created (file/DB based) new domain. After migration, you can clean-up the old (File/DB based) domain. The following restrictions apply when migrating an old (File/DB based) domain to a mew (File/DB based) domain:

Application domains are not moved to the NEW (File/DB based) domain. You must recreate application domains in the NEW (file/DB based) domain using TIBCO Administrator. See, "Working With Application Domains" in the TIBCO Administrator User’s Guide for more information.

TIBCO Enterprise Message Service configurations are not moved to the new (File/DB based) domain and must be reconfigured using the TIBCO Domain Utility. See, the EMS Server Plug-in TIBCO Runtime Agent Domain Utility User’s Guide.

Application server configurations (Servlet Engines) are not moved and must be reconfigured using the TIBCO Domain Utility. See, "Adding or Updating a Servlet Engine to a Domain" in the TIBCO Runtime Agent Domain Utility User’s Guide.

Procedure
======

1). Using the TIBCO Domain Utility, create an new administration domain that uses a File/DB for domain storage. The domain name must be unique among domains running on the host machine. See, "Creating a Domain that Uses a Database" in the TIBCO Runtime Agent Domain Utility User’s Guide for details.

2). Using TIBCO Domain Utility, add the machines that will host TIBCO applications to the new (file/DB based) administration domain. See, "Adding a Machine to a Domain" in the TIBCO Runtime Agent Domain Utility User’s Guide for details.

3). Using the AppManage utility, export all applications in the old (file/DB based) domain to a directory. For example, the next command line exports all applications found in the "myOLDdomain" domain to the c:\test directory.

AppManage -batchexport -dir c:\test -user user1 -pw pw1 -domain myOLDedomain

4). Using the ExportDomainSecurity utility, export the ACLs used in the old (file/DB based) domain to the acls.xml file. For example, the next command line exports all ACLs found in the "myOLDedomain" domain to the c:\test\acls.xml file.

ExportDomainSecurity –file c:\test\acls.xml –acls -user user1 -pw pw1 -domain myOLDedomain

5). Using the AppManage utility, import the applications into the new (File/DB based) domain. For example, the next command line imports all applications found in the c:\test directory to the "myNEWdomain" domain.

AppManage -batchDeploy -nostart -user user1 -pw pw1 -domain myNEWdomain

6). Using the ImportDomainSecurity utility, import the ACLs into the database domain. For example, the next command line imports all ACLs found in the c:\test\acls.xml file to the "myNEWdomain" domain.

ImportDomainSecurity –file c:\test\acls.xml –overwrite -user user1 -pw pw1 -domain myNEWdomain

7). Stop the applications in the old (File/DB based) domain before starting them in the new (File/DB based) domain. Note that you do not need to restart all applications at once. Applications can be stopped individually in the old (File/DB based) domain and started individually in the new (File/DB based) domain .

8). After verifying that all applications are working correctly in the new (File/DB based) domain , you can cleanup the old (File/DB based) domain as follows:

— Undeploy all applications from the old (File/DB based) domain.
— Delete all applications from the old (File/DB based) domain.
— Delete any secondary servers defined in the old (File/DB based) domain using DomainUtility.
— Remove each machine from the old (File/DB based) domain from Admin GUI.
— Delete the old (File/DB based) domain using DomainUtility.

Additional Information

KB:38536

Welcome to "KB Articles"