Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Work Tasks

Filters

Clear all filters
Product Family
Clear all filters
Current publication
Table of Contents
HomeAVEVA™ Work Tasks...Connectors and Extensions User GuideWork with Connectors for System PlatformMove System Platform Galaxy and AVEVA Work Tasks Repository from Engineering Environment to Production EnvironmentMove System Platform Galaxy And RepositoryMove System Platform GalaxyCurrent page
TABLE OF CONTENTS

Move System Platform Galaxy

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Feedback

Steps to import ArchestrA Galaxy from testing environment to production environment:

  1. Access the engineering environment in your machine.

  2. Go to Start > Run > aaSMC and click Enter.

    The ArchestrA System Management Console is displayed.

  3. Expand the Galaxy Database Manager.

  4. Select the required galaxy instance which has to be moved to production environment.

  5. Right-click the Database and select the Backup option.

    The Galaxy should be in Un-deploy state before taking the galaxy backup in the engineering environment.

    A warning message as shown in the following image appears.

  6. Click Yes.

  7. Select a path where the backup.cab file has to be saved and click Save.

    The Galaxy Database Manager screen appears.

  8. Click Close after the backup is saved and copy the .cab file from the folder in which it was saved.

  9. Access the production machine and create a new galaxy with the same name as in the engineering environment.

  10. Go to the Start > Run > aaSMC and click Enter.

    The ArchestrA System Management Console appears.

  11. Expand the Galaxy Database Manager.

  12. Right-click the galaxy DevToProd and click the Restore option.

  13. Select the ArchestraWorkflowSoftware.cab backup file and click on Open.

  14. After restoring successfully, access System Platform IDE and change the GR_Platform network address to the actual production GR address. Save and close the window.

  15. Open WorkflowGateway (WGO) derived template/instance and re-provision with restored Repository in production environment.

    While re-provisioning let’s keep Unique Environment Name same as existing (specified in the engineering environment)

    If multiple Workflow Gateway objects are present, then each of the Workflow Gateway object needs to be re-provisioned to the Repository.

    In case of derived template instances, only derived template need to be re-provisioned.

  16. After re-provisioning the WGO, deploy the entire platform.

  17. After successful deployment, you can see the all associated workflows under the workflow tab of the respective instances. Now trigger the workflow to test whether it is working or not.

    Ensure you use the same user in engineering and production environment, to see the associated Workflows.

  18. If the Workflow is not triggering, then go to Start > Run > type Services.msc and click the Enter button.

  19. Verify if SkeltaConnectorClientArchestrA service is running or not. If it is not running, then right-click on the service and click the Start option.

  20. Verify again whether the workflow is triggered or not.

See Using Workflow Features Inside System Platform IDE and Runtime to provision a WorkflowGatewayObject and trigger a workflow.

Was this topic helpful?
LikeDislike