Working with Process Servers
Creating a Process Server
The general procedure for creating a Process Server in the RunMyJobs user interface is as follows.
-
Navigate to Environment > Process Servers.
-
Click
.
-
Specify configuration information for the Process Server.
-
If the configuration calls for a Platform Agent, RunMyJobs uses the configuration information to create a preconfigured Platform Agent installer. Download the installer, then copy it to the target computer and run it there.
The specific procedure for creating a Process Server differs for different Process Server types.
-
Linux, UNIX, or Windows; Low Volume; and Monitoring Only: A wizard directs you to configure and download a Platform Agent for the Process Server to communicate with. You must install the Platform Agent for these types of Process Server to work.
-
JDBC: A wizard directs you to create a Database object by providing connection and user information for the database you want to connect to. You can also create such a database by navigating to Environment > Databases.
-
AS/400 (IBM System i), SAP System, and Manual Setup: These types of Process Servers do not provide a wizard. For more information, see Creating a Process Server Manually.
When you create or edit a Process Server, the required services are added automatically to the Process Server based on the Definition Types or the SAP interfaces you select. There is usually no need to change the services assigned to a Process Server. The only exception is for Process Servers that are used exclusively for file events. For these, you do not need to specify a Definition Type, but you must manually add the PlatformAgentService.
Deleting Process Servers
You can delete a Process Server only if no other objects relate to it. For example, if there are processes that have run on the Process Server, the Process Server cannot be deleted until all of those processes have been deleted. You can see all processes that relate to the Process Server in Related Objects, in the detail pane and on the show page. Also, you cannot delete Process Servers that are currently running.
The table in related objects contains three columns:
- Type: The type of an object with a link to the Process Server.
- Related Object: The name of an object with a link to the Process Server.
- Used As: Objects can sometimes be assigned different roles. For example, SAP jobs are forced to run on the Process Server that is connected to the appropriate SAP instance.
Overriding Process Server Default Values
You can override Process Server parameter default values globally by setting the following registry entry:
/configuration/ProcessServerParameters/<name>
The <name>
is the name of the Process Server parameter. Note that this registry entry only affects default values; if you add the Process Server parameter to the Process Server, then that value will have precedence over the value of this registry entry.
Only the scheduler-isolation-administrator
can create/edit these registry entries.
Retrieving Support Files
When you use the action Get Support Files a process is prepared so you can choose which log files to retrieve. You select the files you are interested in and submit the process.
A new tab will open once the process has completed with the output of the process, choose <ID> stdout.log
and a second tab will open with a link to the process, from there you can access the zip file with all the logs.
Context Menu
The following context menu actions are available for Process Servers.
Note: For generally applicable object context menu options, see Object Context Menu.
Action | Description |
---|---|
Start | Starts a Process Server. |
Stop | Stops a Process Server |
Monitor Related Chains | Shows a processes monitor with all processes that have run and are scheduled to run on a Process Server. |
Edit | Lets you edit the configuration of a Process Server. You must restart the Process Server for changes to take effect. |
Edit Security | Lets you specify which users or roles may view, edit, delete a Process Server. |
Delete | Lets you delete a Process Server. You can delete only stopped Process Servers that have no other objects related to them. For example, if there are processes that have run on a Process Server, the Process Server cannot be deleted until all of those processes have been deleted. You can see all processes that relate to a selected Process Server in the Related Objects area of its Detail View. |
Duplicate | Lets you make a copy of a Process Server will all its settings. |
Get Support Files |
Lets you download log files and Operator Messages from a Process Server, so you can inspect logs when something goes wrong. When you choose this option, RunMyJobs displays a pop-up window where you can choose which log files to retrieve. When you click Submit in this pop-up window, a new tab opens with a link to a ZIP file containing the requested log files. Right-click the name of the ZIP file and choose Download from the context menu to download the logs. |
Security Tab
The privileges available in the Security tab are as follows.
For more information, see Security Tab.
Privilege | Description |
---|---|
ProcessServer.Create | Create Process Servers |
ProcessServer.Delete | Delete Process Servers |
ProcessServer.Edit | Edit Process Servers |
ProcessServer.View | Access Process Servers |
ProcessServer.ViewJobs | View the processes in the Process Server |
ProcessServer.Control | open and close the Process Server |
ProcessServer.UseForFileEvents | Use the Process Server for file event processes |
ProcessServer.SubmitOnto | Submit processes onto the Process Server |