* * * New or Improved for 2014.1 * * * Run Program - Remote Host
Remote connections are set up to connect to remote computers using Microsoft Windows remote management protocol. Run program is a way to execute a windows application from the HEAT platform. This is useful when you need to execute a program to accomplish some task that cannot be automated within HEAT itself. Some examples might include running PowerShell scripts to manage Active Directory user passwords, importing information from HEAT into a third party application, or running an XSL transformation using msxsl.exe.
|
Server performance can be severely affected if the Run Program job uses a lot of resources. We recommend that you have a separate Remote Host server and not run it on the Application or database servers. |
How Run Program Works
Run program works utilizing the Microsoft Windows Remote Management protocol. This native service of Windows allows remote requests to run local applications. When enabled on a server, HEAT can make a request to run the specified program on that server, using the credentials supplied in the remote connection. When the program is run, it can pass along details from HEAT as command line parameters, and any output can be returned to the quick action to update HEAT.
|
Windows remote management is not enabled by default. To enable this service in a secure manner, review http://msdn.microsoft.com/en-us/library/aa384372(v=vs.85).aspx. Secure connections use SSL certificates, either self-signed or from a trusted authority. |
Using Run Program
| 1. | Configure Windows remote management on a server. |
| 2. | Create a remote connection in the HEAT Configuration Console. (See Configuring Run Program below.) The remote connection contains all the details necessary to connect to the remote server, including a valid user name and password to access resources on that server. |
| 3. | Create a quick action that specifies the details of the program you want executed and the parameters to be passed to it. (See Run Program Quick Action under default quick actions.) |
|
|
As noted in the diagram, a TCP connection is required between the HEAT server and the remote management server. If these two servers are separated across a wide area network or the internet (such as is the case for HEAT Cloud), additional firewall configuration or a point to point VPN tunnel may be required. |
Configuring Run Program
| 1. | Within the Data Integration WizardUsed to import data from external sources into HEAT. (see Configuring Data Integration), click Start next to Run Program - Remote Host. The Connection page appears. Any configured connections are listed. |
| 2. | Click Add New. The Remote Host Connection Setting page appears. |
Remote Host Connection Setting Page
| 3. | Enter information into the fields. |
--fields--
| Field | Description |
|---|---|
| Connection Name | A unique, descriptive name for this connection. |
| Remote Host | The fully qualified domain name or IP address. For example, pl_computer/NA or 101.12.204.155 |
| Secure Mode | Obtains a secure connection. When this option is selected, the Certificate options appear. |
| Port Number | The default port number appears, based on whether secure mode is checked or not. To override, enter another port number. |
| Allow self-signed |
Bypasses the untrusted certificate notification and prevent an error message. |
| Allow Mismatched Name | Specifies a different remote host name than the HTTPS certificate is for (such as when connecting using an IP address instead of the host name on the certificate). You should not need to check this option if you are using a certificate from a trusted public authority, such as VeriSign and use the fully qualified domain name. |
| Wait for Program | The number of seconds to wait for the program to respond. By default, this is controlled by the integration service client and is 60 seconds. To wait for an unlimited time, enter zero. If the wait time is exceeded, a timeout error occurs. |
| Login | The login user name to the remote host. |
| Password | The password to the remote host. |
| 4. | Click Test Connection to see if you have a good connection. The connection status is noted in the Run Program Log. |
| 5. | Click Save. Your connection is added to the list. |