Service Portfolio 1.5

You will learn what you need to run Service Portfolio 1.5 within Processes in this section.

The Service Portfolio is an optional cross-platform module to manage services and service portfolios centrally. This way, you can ensure that your company offers the right compilation of services to meet the needs of your customers.

For Service Portfolio you need a database. You will receive this from your Customer Manager when you install a new system. When updating Service Portfolio, the database must also be updated.

Service Portfolio is used in the context of Serviceware Processes and Serviceware Financial, and forms an interface between both modules.

You can install and configure Service Portfolio as follows:

Use Service Portfolio together with Serviceware Processes. Preparation, installation, and configurations with the support of Serviceware Configurator are described in the following section.
For use in the context of Serviceware Financial, contact your Customer Manager for installation and configuration.

In the mean time, refer to the following installation and configuration instructions:

Warning: Make sure that all Service Portfolio components have the same build number. If this is not the case, see the corresponding FAQ entry on version conflict in Service Portfolio.

Note: Errors may occur when using the Service Portfolio database on a server with named instances.

The connection string for the SQL database must contain the full server name with the domain information.

Note: The Service Portfolio uses port 8543 by default. For the application to be displayed in Serviceware Processes, this port must be enabled on the web server.

Note: The configuration of the Service Portfolio may fail if the server name contains uppercase letters. Use lowercase letters only when entering the server name in the Serviceware Configurator under General settings..

Note: When restarting a server on which both the Service Portfolio and the SQL server are installed, the Service Portfolio service tries to start before the SQL server is fully started and available. Change the startup order.

Note: Under certain circumstances, it may not be possible to stop the Serviceware SPA Server service via the Windows Services console or the command line. In this case, you have to terminate the service or the task behind the service manually via the Task Manager.