To change the path, you can set up an environment variable named INST_TEMP_DIR, and set its value to the relevant location. If your system does not allow execution from the /tmp directory, you can change the path to any other location. exe file.īy default, the installation extracts the files to the /tmp directory and executes several scripts from that location. (UNIX only) Type the following command for the copied installation file to ensure that it has the necessary authorizations:Įnsure that you are logged on with the same user account as the account used to install Control-M/Enterprise Manager, and run the. This procedure describes how to download and install Control-M Automation API from Amazon S3:Ĭreate a temporary directory where to save downloaded files.Ĭlick the relevant S3 link, and save the PADEV.9.0.21.210 file in the temporary directory: Downloading and Installing from Amazon S3 Storage Use the same steps to upgrade from a previous version of Control-M Automation API.ĭuring an upgrade, the API process (the emrestsrv process) is stopped and automatically restarted. Use the following steps to download and install the monthly release. Monthly releases of Control-M Control-M REST API are available for download from an S3 storage location or from the Electronic Product Distribution (EPD) site. If a difference in version is detected, the CLI is upgraded or downgraded automatically.įor installation instructions, see Installing the Control-M Automation CLI.įor additional setup steps that you must perform after installing the CLI, see Setting up a Control-M Environment for the CLI. The CLI and REST API back-end server version must be the same to initiate a connection. (To use the Provision service) Java 11 or later, 64-bit npm is usually installed together with Node.js You can install the CLI on any platform that supports the installation of the following required software: Minimum 8GB memory allocated to the containerįor your work with the Control-M Automation API, you can choose to use an installed instance of Control-M instead of the Control-M Workbench.įor information about installing Control-M, see the Installation Guide.įor information about configuration of the Control-M Automation API in a Control-M installation, see the Control-M Automation API Administration.Ĭontrol-M Automation Command Line Interface (CLI)Ī Node.js package that exposes the Control-M REST API as a Command Line Interface (CLI). Port 7005 is used by the Provision service. You run Control-M Workbench on your personal computer as a Docker image.įree ports: 84. If, at any point, you install another version of Control-M that contains an older version of the API, the newer API is not overwritten.ĭownload, Install, or Upgrade Control-M REST APIĪ personal Control-M development environment that enables you to build, run, and test your job flows, without the need for a Control-M installation. Specific features that require a later version of Control-M are indicated in the current documentation, and the minimum version of Control-M that is compatible with each feature is specified.ĭifferent versions of the REST API can live side-by-side.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |