Skip to Main Content Skip to Search
Product Documentation

Configuring Polyspace Software

On this page…

Configuring Polyspace Client Software

Configuring Polyspace Server Software

Configuring Polyspace Metrics Web Interface

Troubleshooting Common Errors

Configuring Polyspace Client Software

Initial Configuration

By default, the Polyspace Client is configured to automatically detect a Polyspace Server on the network using port 12427.

Manually Configuring the Polyspace Client

By default, the Polyspace Client automatically detects any available Polyspace Server configured as a Queue Manager on the network. However:

In these cases, you can specify a specific Queue Manager server associated to a specific port number to correct the error.

To manually configure the remote server:

  1. In the Polyspace verification environment, select Options > Preferences.

    The Polyspace Preferences dialog box opens.

  2. Select the Server configuration tab.

  3. In the Remote configuration section, select the Use the following server and port button.

  4. Enter an IP address (or server name) and associated port number (default 12427) for the Polyspace Server. You must use the same port number for all Polyspace clients, Queue Manager and servers.

  5. If you want to configure access to Polyspace Metrics, see Configuring Polyspace Metrics Web Interface.

  6. Click OK.

    The preferences are stored in the polyspace.prf preferences file in %AppData%\Polyspace (C:\Users\username\AppData\Roaming\Polyspace\polyspace.prf on a Windows system).

Back to Top

Configuring Polyspace Server Software

Initial Configuration

You perform initial configuration of the Polyspace Server software during installation (see Configuring the Polyspace Server Software).

After installation, the Polyspace Server becomes the first CPU of the architecture by default.

Updating Configuration of the Polyspace Server

The default Server configuration assumes that the Server is both the Queue Manager and a CPU.

After you install the software, you can configure or update the Queue Manager graphically (on Windows systems) or by using a shell command.

To update your server configuration and associated polyspace.conf file:

  1. Open the Remote Launcher Manager as follows:

    • Select Start > All Programs > Polyspace > Remote Launcher Manager

      or

    • Enter the command Polyspace_Common/RemoteLauncher/PSTRLManager.exe

    The Remote Launcher Manager dialog box opens.

  2. Click Stop Daemon to stop the current Queue Manager.

      Note   You must stop the current Queue Manager before you can change any parameters.

  3. In the Common Settings pane, set the port number and location for the Remote Launcher configuration file (polyspace.conf).

  4. In the Queue Manager Settings pane, specify the address of the Queue Manager and all attached CPUs of the Remote Launcher.

    The syntax <describing name/IP address>[:<port number>]" attaches a CPU.

    For example, in the previous figure "SERVER1" is the Queue Manager and "012.123.4.56:12427" represents a CPU with a specific port number.

  5. In the Polyspace Server Settings pane, specify the location of Polyspace products installed on the server, and available languages.

  6. If you have activated more than one license for your server, set the Number of Polyspace verifications that can run simultaneously on this server to the number of licenses you have activated for this machine.

Manual Configuration of the Polyspace Server

A configuration of the Server/Verifier, Queue Manager of the Client/Server architecture has been stored in a standard file. A default configuration is generated during the installation: the current machine is at the same time the Queue Manager, and the distant machine.

The batch command Polyspace_Common/RemoteLauncher/bin/setup-remote-launcher can be used to create or destroy the configuration file. It is called polyspace.conf. It may be found:

The configuration file contains fields which set a Queue Manager and CPU architecture:

Any change in the configuration file except for the cpu= field (for example, to add a new CPU, see next paragraph), the associated daemon/service manager need to be stopped and re started:

If you did not select the Queue Manager as a service (daemon) during installation, use the following commands to install it:

You can then launch the polyspaced service (daemon) using the following commands:

Configuration File and Folder

The Polyspace_RLDatas folder contains the following files and folders:

In this example, the BERGERON cpu has been configured to be a Queue Manager and a CPU of C, CPP and Ada95 code verifications on default port 12427. The product installed in c:\Polyspace\PolySPaceForCandCPP will be used. Moreover, another CPU of address IP 192.168.2.79 has been declared on port 12428.

On a UNIX system, the directory location containing locks and datadir by default is /var/Polyspace.

Installing a New CPU

Installing a new CPU is very simple: just follow the standard Polyspace Server installation. Then, edit the polyspace.conf of the CPU which has been chosen as Queue Manager, and add the new CPU using the field cpu=<describing name/IP address>[:<port number>]

See the following example where there are two declared CPUs. 

product=c:\Polyspace\PolyspaceForCandCPP
product=c:\Polyspace\PolyspaceForAda
lang=Ada95
lang=C
lang=CPP
datadir=c:\Polyspace\Polyspace_RLDatas
username=bard
cpu=BERGERON
cpu=192.168.2.79:12428

Files and Folders Created When Installing the Queue Manager for Polyspace Server

When you install the Polyspace daemon/service, the software creates the following items (UNIX):

You must have write access to all of these locations to successfully install the Queue Manager service.

Specifying Port Number of Polyspace Metrics Web Server in Queue Manager

If you change or specify a non-default value for the Web server port number of your Polyspace client (see Configuring Access to Polyspace Metrics), you must manually configure the same value for your Queue Manager.

In <Polyspace_Common>/../Polyspace_RLDatas/tomcat/conf/server.xml, edit the port attribute of the Connector element: 

<?xml version="1.0" encoding="UTF-8"?>
<Server port="8005" shutdown="SHUTDOWN">
  <Service name="Catalina">
    <Connector port="8080"/>
    <Engine name="Catalina" defaultHost="localhost">
    <Host name="localhost" 
appBase="C:\Polyspace\Polyspace_Common\RemoteLauncher\lib\
apache-tomcat-5.5.28\webapps"/>
    </Engine>
  </Service>
</Server>

Back to Top

Configuring Polyspace Metrics Web Interface

Polyspace Metrics is a Web-based tool that allows you to evaluate and monitor software quality through the lifecycle of a project.

To configure access to Polyspace Metrics:

  1. Specify the Queue Manager server on which Polyspace carries out the verification and creates the results repository. See Configuring Polyspace Client Software and Configuring Polyspace Server Software.

  2. Select Options > Preferences to open the Polyspace Preferences dialog box.

  3. Select the Server configuration tab.

  4. In the Metrics configuration section, specify a locally accessible folder for downloading result files from the Polyspace Metrics Web interface.

  5. Select the Download results automatically check box. When you click on an item in Polyspace Metrics to view the item in the Polyspace verification environment, the software downloads results to the verification launch folder. However, if this folder does not exist, the software downloads results to the folder that you specify in the Folder field, which by default, is C:\Temp.

  6. If you do not select this check box, then when you click on an item in Polyspace Metrics, a dialog box opens. Using this dialog box, you can specify your locally accessible folder.

  7. The folder and its contents are not deleted when you exit the Polyspace verification environment.

  8. In the Port number field, specify the number of the port for communication between the Polyspace verification environment and the Polyspace Metrics Web interface. The default is 12428.

  9. In the Web server port number field, specify the number of the web server port. The default is 8080. You must configure the same number for the Queue Manager server. See Specifying Port Number of Web Server in Queue Manager Specifying Port Number of Polyspace Metrics Web Server in Queue Manager.

Back to Top

Troubleshooting Common Errors

This section contains information on troubleshooting the following common errors:

Errors Concerning the polyspace.conf File

If you receive any of the following errors:

  1. Stop the polyspacedservice (daemon).

  2. Update the polyspace.conf file.

  3. Restart the service (daemon).

The following errors concern the polyspace.conf file.

Errors Concerning Problems with Write Access

If you receive any of the following errors, check right accesses with username declared in the polyspace.conf file in the folder <dir>, <file name> or <path> (given in the error message).

Check also that you have not changed anything linked to "polyspaced" service (daemon) without stopping it.

Java Not Found Errors

When installing a Polyspace_Common product on a 64 bit Linux machine, the installation program may end with the following error message: 

exec: 2433: /tmp/install.dir.880/Linux/resource/jre/bin/java: not found

This error occurs because the Polyspace installer is itself a 32-bit binary using 32-bit binaries, which may cause problems on a 64-bit machine. It needs 32-bit libraries installed.

To solve this problem, install the 32-bit libraries. For example, on an Ubuntu 64-bit Linux machine, install the package "ia32-libs" from your Linux distribution.

Refer to the documentation for your Linux distribution for more information on installing these libraries.

Other Errors

Other errors may concern OS system, network and standard command available (for example "tar", "gzip", etc.).

Double check that these standard commands exist in your system. Error messages are detailed enough to know which command has failed.

Back to Top

  

Launching Installation from Command LineLaunching Installation from Command Line Configuring Polyspace Server to Support Multiple Versions of Client SoftwareConfiguring Polyspace Server to Support Multiple Versions of Client Software

 © 1984-2012- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS