Cloud Portal ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (16.3.0) 16.2.0 16.1.0 16.0.0 15.4.0 15.3.0 15.2.0 15.1.0 14.5.x 13.9.x 13.8.x 13.7.x 13.6.x 13.5.0 13.4.x 13.3.x 13.2.x
User Community Service Desk Downloads

Remote Execution Direct Communication Configuration

When you run the remote execution jobs on a secured cloud server, sometimes you might experience performance issues, such as:

  • A long delay between job successful finish and execution SUCCESS.

  • A similar message in the console output: [WARN] Status tracking issue.

You can open these warnings in Run Results and see the error details.

Console output
Run results
Warning

This page describes a workaround that helps avoid such issues.

Solution

As a prerequisite, you should already have in place the ONE Platform launch environment (env01) with the Ataccama ONE Platform server that has a public address as shown in the images.

Server configuration
Environment configuration

  1. Navigate to File Explorer.

  2. Select Environments > New Environment.

  3. Create the new ONE Platform launch environment (env02).

  4. Navigate to the new environment (env02).

    Create a new environment

  5. Right-click Servers and select New Server.

  6. Select Ataccama ONE Platform as Implementation.

  7. Use the following options:

    • Web URL (Optional): Same as the public server used in env01.

    • User:: Same as the user for the public server used in env01.

    • Password: Same as the password for the public server used in env01.

    • Authentication: Basic.

    • GraphQL URL: http://mmm-be-svc:8021/graphql.

    • ONE Metadata Server Port (Optional): 1.

    • ONE Data Processing Port (Optional): 1.

      Create a new server

  8. Select Finish.

    New server added

    After you finish configuring the solution, keep in mind the following:

    • Always use this new environment (env02) for remote execution.

    • Always clear the Validate plans before plans execution option in Run Configurations. You need to do this separately for each plan.

      Validate plans before execution
The original environment (env01) should still be selected when doing anything other than remote executions while the environment (env02) should be used only for remote executions.

Was this page useful?