Working with server profiles
Following are some common use cases for server profiles. Some of these uses are supported via the use of scripts (see Profile scripts) and may require administrative/root privileges.
Creating a server profile
An SPSS® Modeler Server administrator named Jane uses a script to create a new profile:
- Jane must specify a unique name for the profile (it cannot be an existing profile name). If the profiles directory does not already exist, it is created for Jane. Then a new sub-directory is created in the profiles directory with name Jane specified, containing the directories config, data, log, and tmp.
- If Jane chooses, she can also specify the name of an existing profile to use as a template, in which case the content of the config folder within the existing profile is copied to the new profile. If she does not specify a template, or if the existing profile does not include an options file even though it should, then an empty options file is created in the new profile.
- Jane may also choose to specify a port number for the profile, in which case the port number is
written as the value of the
port_number
property in the profile's options file. If she does not specify a port number, a value is chosen for her and written to the options file. - Jan can also choose to specify the name of an operating system group that will have exclusive access to the profile in which case group configuration is enabled in the options file. In this case, a groups file is created that denies login to all but the specified group.
Configuring a server profile
Server administrator Jane configures a profile either by manually editing the profile configuration files, or by using the IBM® SPSS Modeler Administration Console in IBM SPSS Deployment Manager to connect to the profile service.
Creating a Windows service for a serverprofile
On Windows, the administrator uses a script to create a service for a specified profile:
- Jane must specify the name of an existing profile, and then a service instance is created for
that profile. The command line for the service will include the
profile
argument. The name of the service will follow a standard pattern including the profile name. - Jane might need to use the service administration console later and edit the service properties if she needs to change the user name and password for the service (when running non-root).
On UNIX, there are also ways to create "services" that start automatically when the system boots. The administrator may want to create profile services using these mechanisms, but note they are not offically supported by IBM SPSS Modeler.
Managing Windows services for server profiles
Administrators can use a script to perform the following tasks:
- See which server profile services are running
- Start a particular service
- Start all services
- Stop a particular service
- Stop all services
When starting or stopping all services, the list of profiles is obtained by searching the sub-directories of the profiles directory.
Deleting a server profile's Windows service
On Windows, administrators can use a script to delete a service for a specified profile (if a service exists for the profile). The name of the profile must be specified.
Removing a server profile
After stopping the profile's service, administrators can remove a profile by deleting its folder from inside the profiles directory.
Updating SPSS Modeler Server
When applying a Fix Pack to SPSS Modeler Server, the Fix Pack is applied to all server profiles. On Windows, all profile services are stopped and restarted automatically. On UNIX, you must manually stop and restart them.
Uninstalling SPSS Modeler Server
When SPSS Modeler Server is uninstalled, all server profiles are uninstalled. Note that the profiles directory and any profiles it contains are not removed automatically. They must be deleted manually. On Windows, all profile services are uninstalled automatically. On UNIX, you must manually remove them.
Installing a new version of SPSS Modeler Server
When installing a new version of SPSS Modeler Server, any existing server profiles are not migrated automatically. An administrator must manually copy profiles from one installation to the next (and edit the configurations where necessary) to recreate the services.