About the Default Configuration :: SAS(R) Visual Process Orchestration Server 2.1: Administrator's Guide

Default Ports

SAS Visual Process Orchestration uses the following port numbers by default. You can change some of these port numbers using SAS Management Console. Some of these port numbers are not intended to be changed. Contact SAS Technical Support as needed to change port numbers.

Server	Port
SAS Visual Process Orchestration Design Server	21040
SAS Visual Process Orchestration Runtime Server	21050
SAS Metadata Server	8560
SAS Web Infrastructure Data Server Port (SAS Web Application Server)	5431
SAS Web Application Server	6969–9648 non-inclusive, as delivered
SAS Object Spawner Operator Port	8580
SAS Object Spawner Port Banks	8800–8889
SAS Content Server HTTP Port	SAS Web Application Server Default Port
SAS Job Monitor Database Server	9932 - 9941

Install Path

The Runtime Server is installed in the same directory as the Design Server, on the same host.

The default installation path is specified in this document using the shortened notation install-path. This shortened notation enables this document to specify paths that apply to all supported operating environments (Windows, UNIX, and Linux). The subdirectory identifier is specified with a UNIX forward slash for the sake of simplicity. Actual Windows paths use a backslash (\).

Here is the Windows syntax of the install-path:

SASHome\SASVisualProcessOrchestrationServer\release-number

Here is an example of a Windows install-path:

C:\Program
                     Files\SASHome\SASVisualProcessOrchestrationServer\2.1

The install-path syntax for UNIX and Linux is as follows:

SASHome/SASVisualProcessOrchestrationServer/release-number

A typical install-path for UNIX or Linux looks like this:

/SASHome/SASVisualProcessOrchestrationServer/2.1

Configuration Files

configuration filesRuntime Server configuration files are installed in the directory install-path/etc. The operational configuration files are named *.cfg (app.cfg, dmserver.cfg.) Backup copies of the default configuration files (*.backup) are stored in the same directory. Retain the backup files for possible future reference to the default configuration.

Several configuration files are shared between the Design Server and Runtime Server. Each of the servers also has its own configuration file. The configuration files are read in a specified sequence when you start the servers,

Most of the options that are set in the configuration files receive values at install time. Most of those values should not be changed unless you are directed to do so by your SAS technical support representative. This document describes how to change the values of supported configuration options as needed at your site.

To change the value of a configuration option of the Runtime Server, stop the server, edit the configuration file, and restart the Runtime Server.

To change the value of a configuration option of the Design Server, stop the SAS Object Spawner, edit the configuration file, and restart the SAS Object Spawner.

The following table describes the configuration files in the order in which they are read during server invocation.

Configuration Files in Descending Read Order	Description
app.cfg	The Design Server and Runtime Server both read this file at the beginning of the configuration process. The file contains connectivity options.
dmserver.cfg	Read by the Runtime Server only, to specify internal parameters.
dmposerv.cfg	Used by the Design Server only, to specify internal parameters. Currently contains one option that specifies the location of the server log file.
(macros directory)	The macros directory (/etc/macros) can contain .cfg files. These files are read by the Design Server and Runtime Server at this point in the invocation process. For more information about macros, see Define Macros.
macros.cfg	This file can contain substitution values for orchestration jobs. This file is read by both the Design Server and the Runtime Server.
(environment variables)	The Design Server and Runtime Server read environment values as the last step in the configuration process.

Directory Permissions

The following tables outline the recommended directory permissions for the Runtime Server.

Windows
Directories	Users	Default Permissions
`install-path`	Administrator, Installer	Full Control
`install-path`	Process user	Read and Execute, List Folder Contents
`install-path\var`	Installer	Full Control
	Process user	Read, Write, List Folder Contents
	The user who backs up the server, Backup Administrator	Read, List Folder Contents

UNIX and Linux
Directories	Users	Default Permissions
`install-path`	Installer	Read, Write, Execute
`install-path`	Process user	Read, Execute
`install-path/var`	Installer	Read, Write, Execute
	Process user	Read, Write, Execute
	The user who backs up the server; Backup Administrator	Read, Execute

Note: If the default temporary directory (/TMP) runs out of space while running orchestration jobs, set the TMPDIR environment variable to point to a different directory with greater capacity.