Adeptia Migration Utility User Guide
Adeptia Migration Utility User Guide
User Guide
Version 3.0
Adeptia Inc.
443 North Clark Ave,
Suite 350
Chicago, IL 60610, USA
Phone: (312) 229-1727
Copyright
Trademarks
The Adeptia logo and Manage, Automate and Optimize Business Processes are trademarks of
Adeptia, Inc.
Statement of Conditions
Adeptia, Inc. provides this publication "as is" without warranty of any kind, either express or
implied. In no event shall Adeptia be liable for any loss of profits, loss of business, loss of use or
data, interruption of business, or for indirect, special, punitive, incidental, or consequential
damages of any kind.
No part of this work covered by copyright herein may be reproduced in any form or by any
means—graphic, electronic or mechanical—including photocopying, recording, taping, or storage
in an information retrieval system, without prior written permission of the copyright owner.
This publication is subject to replacement by a later edition. To determine if a later edition exists,
contact www.adeptia.com .
Contact Information
Sales [email protected]
Support [email protected]
1 INTRODUCTION................................................................................................................................ 3
NEED FOR MIGRATION .............................................................................................................................. 3
ADEPTIA MIGRATION UTILITY................................................................................................................... 3
BENEFITS OF USING ADEPTIA MIGRATION UTILITY ................................................................................ 4
2 GETTING STARTED.......................................................................................................................... 5
PRE-REQUISITES ........................................................................................................................................ 5
STARTING ADEPTIA MIGRATION UTILITY ................................................................................................ 5
3 ENVIRONMENT PROMOTION .................................................................................................... 7
EXPORT ....................................................................................................................................................... 8
PROMOTE .................................................................................................................................................. 13
Generating XML for Retained Objects in the Target System ......................................... 21
Deleting an Object.......................................................................................................................... 29
DEPLOY ..................................................................................................................................................... 31
4 MIGRATION....................................................................................................................................... 34
ONLINE MIGRATION ................................................................................................................................ 35
OFF LINE MIGRATION.............................................................................................................................. 38
Export/Backup ................................................................................................................................. 39
Import/Restore ................................................................................................................................ 41
5 PATCH UPDATE ............................................................................................................................... 48
APPLY PATCH ............................................................................................................................................ 49
REMOVE PATCH ........................................................................................................................................ 52
6 APPENDIX A...................................................................................................................................... 55
SAMPLE CONFIGURATION VALUES ......................................................................................................... 55
SQL Server Database .................................................................................................................... 55
HSQLDB Database.......................................................................................................................... 55
Default Values for Additional Columns in an Upgraded Version................................... 55
7 TABLE OF FIGURES ....................................................................................................................... 57
8 TABLE OF TABLES .......................................................................................................................... 59
Adeptia offers a Migration utility which facilitates you to seamlessly migrate objects in all
situations. It is a comprehensive tool which enables you to:
The benefits of using the Adeptia Migration utility are outlined as:
The Migration utility is either bundled with the Adeptia Server or it can be downloaded or
purchased separately. To run it on a desktop, you need to copy the utility explicitly on the
desktop.
When you run the utility, the system creates a log file in the same location as the utility file.
Each time you run the utility; this log is appended.
This screen displays the three steps used in the Environment Promotion. These are outlined in
the table below.
EXPORT
This step is performed on the source system where the Adeptia Server is installed.
Steps to export objects
1. Select the Export radio button on the Environment Promotion Actions screen
and click Next. The Select Source System screen is displayed. Click Browse
to select the directory where the Adeptia Server is installed (see Figure 3.2)
4. Click Next. The Select Objects screen is displayed (see Figure 3.4).
If you select All Objects option in Select the Action screen, the Select
Services screen is displayed (see Figure 3.6). In Select Services screen
you can select all services or only the required services to export. To
select all services click Select All button. To select the individual
services check the checkbox against the required services.
Some service names have changed across the version and because of
that some service may be shown multiple times with different names.
Following table shows those services and their name.
7. Click Next. The Select Target directory screen is displayed. Click Browse to
select the target location where you want to save the zip file (see Figure 3.7).
This screen displays all logs and confirms whether the export operation is successful or
not. If it is successful, a message stating “Export completed successfully” is displayed in
the View Export Logs screen and as a popup window, and a zip file of the exported objects
is created. In case of failure, it displays an error message in the View Export Logs screen
and as a popup window, and rollbacks the entire operation.
9. Click Finish to complete the export process and exit the Migration utility.
PROMOTE
This step is performed on the target system.
Pre-Requisite
The exported zip file must be available on the target system on which the Adeptia
Server is installed.
5. Click Compare Selected Objects to compare the source and target objects.
It displays the process in running state (see Figure 3.12).
7. The Compare Objects screen displays objects in a tree structure, which shows
a comparison between the source and target objects at both the activity and
field levels. It displays legends at the activity and field levels, which highlight
the comparison and indicate whether the activity or field will be updated or
not. It also displays the Advanced Properties of the object at the field level.
The legends are displayed at the bottom of the screen and are outlined in the
table below.
When the source and target objects are different, they need to be updated at the
target end. This is done by comparing the Activity ID of the objects at the source and
target end. If they match, then the objects are updated, else not.
You can delete an object from the Compare Objects screen. Refer to
the Deleting an Object screen.
8. You can view the changes between the source and target end by right-clicking
each field/activity, and selecting View Changes option (see Figure 3.15).
At times, the Source and Target columns are displayed as empty. If the
Source column is empty, it indicates that the fields are blank at the
source end. The Target column is empty if there is no object at the
target end.
11. Click Close to close this screen and return to the Compare Objects screen.
Similarly, click Close to close this screen and return to Select Group screen.
12. Click Next. The Select Retain XML Location screen is displayed. Click Browse
to select the location where the xml file for the objects to be retained, is
stored (see Figure 3.17 Error! Reference source not found.).
If you are starting the Migration tool for the first time, or you want to
edit the existing xml file, refer to the Generating XML for Retained
Objects in the Target System section.
13. Click Next. This displays a screen, where you need to enter your name in the
specified field. This is just to keep track of who approved the promoted objects
(see Figure 3.18).
17. Save the PDF report and then open it to view its details (see Figure 3.21).
While promoting objects, you may want to retain a few objects at the target end. For
objects that are specific to the environment, or configuration objects such as User ID, you
do not want to promote and overwrite them at the target end. For example, when
promoting data from the Development environment to the Production environment, the
Database Info objects may vary. The objects are the same, but their connection
1. Click Generate Retain XML on the Select Retain XML Location screen to
select the objects to be retained. This displays the process in the running state
(see Figure 3.22).
You can retain objects at both the Service and Field Levels but at a
time you can retain object either at service label or field label.
You can expand the service by clicking [+] against the service. All
fields associated with the activity are displayed. However, they are de-
active and cannot be selected.
2. To retain a specific activity of the service, right-click the service and select
Specific Activity option (see Figure 3.24).
You can either enter values in both the Activity Name and Activity ID
fields, or in one field only. However, it is mandatory to enter value in
one field.
If you do not remember the ID of an activity, you can refer to the
Production environment or go to the Manage section of the Adeptia
Server.
5. Click Insert. This displays the activity name and ID in the Query Information
field (see Figure 3.26).
You can specify one or more activities in this screen. All the specified
activities are listed as comma separated values in the Query
Information field.
You can remove an activity listed in this field, by selecting the activity
and pressing <Delete> on the keyboard.
6. Click Done to complete the query and return to the previous screen (refer to
Figure 3.24).
7. Click Generate Retain XML. This generates the xml file for the retained
service. This implies that when transferring data, the selected service for the
specified activities will be ignored at the source end and not overwritten at the
target end.
You can either enter values in both the Activity Name and Activity ID
fields, or in one field only. However, it is mandatory to enter value in
one field.
If you do not remember the ID of an activity, you can refer to the
Production environment or go to the Manage section of the Adeptia
Server.
5. Click Insert. This displays the activity name and ID in the Query Information
field (refer to Figure 3.26).
You can specify one or more activities in this screen. All the specified
activities are listed as comma separated values in the Query
Information field.
You can remove an activity listed in this field, by selecting the activity
and pressing <Delete> on the keyboard.
The objects that are changed at the Field level are displayed in the
Compare Objects screen with the legend. And if you want to retain
this value of the target side, the changed value is extracted from the
target and transferred to the source, thus implying that the values are
same at the source and target end. For example, if the File Path field of
the File Source service is changed, then the updated value is extracted
from the target end and transferred to the source end of the File Path
field. This field is now displayed in the Compare Objects screen with
the legend.
DELETING AN OBJECT
While comparing the objects, you can delete an object.
Steps to delete an object
1. Right-click the object you want to delete in the Compare Objects screen, and
select the Delete option (see Figure 3.29).
You can delete objects at the Service, Process Flow and Activity levels.
However, you can update only at the Field level.
If you delete an object at the Service level, then the entire service along with its process flows
and activities is deleted. If you delete an object at the Process Flow level, then all process
flows and its objects are deleted. If you delete an object at the Activity level, then the entire
activity along with its fields is deleted.
The Deploy step allows you to apply the promoted changes to target system.
Steps to Deploy objects:
1. Select the Deploy radio button on the Environment Promotion Actions screen
and click Next. The Select Source data location screen is displayed. Click
Browse to select the zip file that was created in the Promote process (see
Figure 3.30)
You can use the Migration process to insert objects from the source
database to the target database. However, you cannot update the
objects in the target database.
ONLINE MIGRATION
Online Migration can be run on any desktop. It facilitates you to migrate objects from the
source database to the target database. Both these databases need to be connected for this
process. For example, if the earlier version of Adeptia Server is on HSQL database, and the
upgraded version is on SQL Server, you can use this process to transfer the objects.
Steps to migrate objects using online migration:
2. Select Online migration radio button on the Migration Actions screen and click
Next. The Configuration Settings screen for Source Database is displayed (see
Figure 4.2).
Refer to Appendix A for sample configuration values for SQL Server and
HSQL databases.
9. Enter the target database information and click Next. The Select Objects
screen is displayed (see Figure 4.4). This screen displays a list of all the tables
of the Adeptia Server.
All tables that are prefixed with ABPM are quartz tables. These tables and the
dt_properties tables and are listed in case of the SQL Server database only. It is
recommended not to migrate these tables, as the migration process is likely to fail in
such a case, as all tables in the source and target databases should be the same.
Similarly, please migrate the log tables (AU_Log and AU_TransactionData), only if you
need the log, as these are big size tables and slow down the migration process
considerably.
11. Click Next. This displays the View Logs screen (see Figure 4.5).
EXPORT/BACKUP
Steps for offline migration (Export/Backup):
1. Select Export/Backup radio button on the Offline Actions screen and click
Next. This displays the Select Source Database screen. Click Browse to select
the source system where the Adeptia Server is installed. (see Figure 4.7).
IMPORT/RESTORE
2. Select the All radio button, when both the source and target databases have
the same version of the Adeptia Server. For example, when migrating objects
from Adeptia Server 4.5 to Adeptia Server 4.5, click this option.
3. Select the Only Database radio button, when the source and target databases
have different versions of the Adeptia Server. For example, when migrating
objects from Adeptia Server 4.4 to Adeptia Server 4.5, click this option. This
displays the Select Source location screen. Click Browse to select the zip file
created in the Export process (see Figure 4.11).
All objects that are prefixed with ABPM are quartz tables. These tables and the
dt_properties objects are listed in case of the SQL Server database. It is recommended
not to restore these objects as the migration process is likely to fail in such a case, as all
tables in the source and target databases should be the same. If they are different then
deselect the log objects such as (AU_Log and AU_TransactionData) as it slows down the
migration process.
7. Click Next. This displays the View Restore Logs screen (see Figure 4.14).
8. Select the Only Configuration Files radio button on the Import Actions screen,
when you want to restore the configuration files only. This displays the Select
Source location screen (refer to Figure 4.11).
9. Click Browse to select the zip file created in the Export process.
10. Click Next. The Select Target Location screen is displayed (refer to Figure
4.12).
11. Click Browse to select the directory, where the target system of the Adeptia
Server is installed.
12. Click Next. The Select Configuration Files screen is displayed (see Figure
4.15). This screen displays a list of all the configuration files for all objects of
the Adeptia Server.
14. Click Next. This displays the View Logs screen (see Figure 2.15).
Before applying patch, make sure that the Kernel and Web Runner are
stopped. Once you have finished the process, you need to start the
Kernel and the Web Runner.
You can run the Patch Update process on SQL Server only.
APPLY PATCH
Apply patch allows you to apply the patch on currently installed Adeptia Server.
The Recovery File is also created as a zip file. Recovery file keeps the
backup of existing files, which will be replaced by patch update.
7. Click Save. This displays the View Apply Patch Logs screen (see Figure 5.7).
REMOVE PATCH
Remove Patch allows you to rollback the changes done by patch update. When you apply a
patch, it asks you to create a recovery file. If you have created a recovery file, you can
remove the patch, which you have applied. When you remove a patch, migration utility asks
you to select the recovery file, which you have created during patch update process and then
roll back all the changes done by patch update. It also rolls back the changes done in the
backend database.
Steps to revert objects using Remove Patch:
1. Select Remove Patch radio button on the Patch Update Actions screen and
click Next. The Select Recovery Patch File Location screen is displayed. Click
Browse to the select the directory where the recovery patch file (zip file) is
saved (see Figure 5.8).
3. Click Next. This displays the View Remove Patch Logs screen (see Figure
5.10).
HSQLDB DATABASE