Versions Compared

Old Version 5

changes.mady.by.user Subrat Sandilya

Saved on

compared with

New Version 6

changes.mady.by.user Subrat Sandilya

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Question 1:

...

Why is it important to validate the count of objects in a dataset?

Answer 1: When an error occurs during the migration process, an error message will be displayed in the Migration Utility console window. This message will provide a brief description of the issue.

Question 2: Where can I find more detailed information about the error?

Answer 2: For more detailed information regarding the error, you should refer to the migration.log file. This log file contains comprehensive details about the errors encountered and is located at:

Code Block
\AdeptiaServer\ServerKernel\MigrationUtility\migration.log

...

During this process, it is important to be aware of the possibility of inconsistencies between the entries in the object zip file and those stored in the backend database.

Steps to validate the object count:

  1. Download Utility folder - Click here

  2. Extract the folder

  3. Open migration file

  4. Edit the migration file

    1. DB URL

    2. DB username

    3. Password

    4. Object.zip path

  5. Run the following command  java -jar MigrationValidator.jar

  6. A report, named MigrationValidator_2965487, is generated. This report contains any missing tables, if there are any.

  7. Open the file and check if "Missing Tables" is empty. If it is, all object tables have been successfully deployed.

Question 2: What steps must be completed to update the aistoacverification.properties file before initiating the Checklist Utility?

Answer 2: Before initiating the Checklist Utility, it is essential to complete the following steps to update the aistoacverification.properties file:

  1. Navigate to the .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/MigrationUtility directory.

  2. Open the "aistoacverification.properties" file using a text editor and implement the specified modifications.

  3. Specify the location of the Connect Server Installation directory up to the Adeptia Server folder as ...AdeptiaConnectServerInstallFolder\AdeptiaServer

  4. Define the destination folder for generating reports (e.g., d:/AIS/report).

  5. Save and close the file.

  6. Open CMD in  …Adeptiasuite-6.9\AdeptiaServer\ServerKernel folder

  7. Run the following command to generate a report

       MigrationUtility.bat -aistoacverification migrationutility/aistoacverification.properties

Question 3: How to access the migration.log file?

Answer 3: To access the migration.log file, navigate to the following directory on your system:

...

Locate the migration.log file within this directory and open it using a text editor or a log viewer application.

Question 4:

...

Why is it necessary to manually resolve instances of duplicate email addresses, group admin emails, Sysadmin-created users, projects, and groups?

Answer 4: The migration.log file contains detailed information about the migration process, including:

  • Time and date of the migration attempt

  • Detailed error messages and codes

  • Specific steps or actions that failed during migration

  • Any relevant stack traces or debug information

Question 5: What should I do if I cannot understand the error message in the migration.log file?

Answer 5: If you are unable to understand the error message or need further assistance, consider the following steps:

...

Check the documentation: Refer to the official migration utility documentation for guidance on common errors and troubleshooting steps.

...

It is crucial to handle any instances of duplicate email addresses, group admin emails, Sysadmin-created users, projects, and groups manually. Objects deployed in the current AIS version may cause issues if exported directly to AC without addressing these duplications.

Here are the steps to eliminate duplication in the dataset:

  1. Collaborate with the client to manually adjust entities that share the same name.

  2. Work with the client to manually update duplicate email addresses for different users.

  3. Generate a new user, project, and group as necessary to resolve duplicity issues.

Question 5: What steps must be taken to determine which application's activities, Connect or Suite, you need to migrate before starting the migration process, and how do you proceed if using Suite as a standalone application?

Answer 5: Before embarking on the migration process, it is essential to first identify whether you will be migrating activities from Connect or Suite. If you are utilizing Suite as a standalone application, ensure that you choose Adeptia Suite on the screen to migrate activities tailored to this specific application. Conversely, opt for Adeptia Connect if you intend to migrate activities associated with Connect.

Question 6: How can I prevent errors during the migration process?

Answer 6: To minimize the risk of errors during migration, ensure the following:

  • Compatibility: Verify that the source and target systems are compatible and meet all prerequisites for migration.

  • Backup: Always create a backup of your data and configurations before starting the migration process.

  • Follow guidelines: Adhere to the guidelines and best practices provided in the migration utility documentation.

  • Test environment: Perform a test migration in a staging or test environment to identify potential issues before executing the migration in the production environment.

Question 7: Can I perform multiple migrations simultaneously?

Answer 7: It is generally recommended to avoid performing multiple migrations simultaneously to prevent potential conflicts and ensure each migration process receives adequate resources. If multiple migrations are necessary, ensure they are executed in a controlled and sequential manner.

Question 8: What should I do if the migration process is interrupted?

Answer 8: If the migration process is interrupted:

  1. Check the console: Look for any immediate error messages in the Migration Utility console window.

  2. Review the log: Examine the migration.log file for detailed information on where and why the interruption occurred.

  3. Resolve issues: Address any issues indicated in the log before attempting to restart the migration process.

  4. Restart migration: Once issues are resolved, restart the migration process from the beginning or from a safe checkpoint if supported.

Question 9: Can a user extract an object from a higher version and deploy it on a lower version?

Answer 9: No, the migration process only allows objects to be migrated from a lower version to a higher version. For example, objects extracted from AC4.X cannot be deployed to AC3.X.

Question 10: During the AIS to AC migration process, can a user deploy the client's objects to any version of AIS?

Answer 10: No, as part of the migration process, the user needs to install AIS and upgrade it to the latest version available before deploying the client's objects.

Question 11: Can the DBCleaner utility create tables in all databases, such as MySQL, SQL, and Oracle?

Answer 11: The DBCleaner utility can create tables only for MySQL and SQL databases. It does not support table creation for Oracle databases.

Question 12: If the DBCleaner utility does not work for Oracle database creation, what should be done?

Answer 12: For creating databases for Oracle, you need to create the backend and log databases for both AIS and AC in RDS (Relational Database Service).

Question 13: Should the aistoacverification utility be run for both AIS and AC in the AIS to AC migration process?

Answer 13: Yes, the aistoacverification utility should be run to correct the objects' data provided by the client before extracting the final corrected objects from AIS.

Question 14: What should be done if the admin's password changes after deploying an object, and you cannot log in?

Answer 14: It is possible that the SysAdmin has The SysAdmin may have modified the password for the admin user. To obtain the updated password:

...