Installing Optima on a Linux server

Important:  You need root privileges to run the script.

1. On the DB server, press Ctrl+Alt+T to open a bash shell.

2. Execute:
   sudo -s

   Then insert the user password or use su - root and the root password. This logs you in with super-user privileges.

3. Execute:
   yum install unzip

4. Execute:
   unzip /opt/optima_zip/ptv-optima-zip-vv.n.xxxxx.zip
5. Execute:
   cd /opt/optima_zip/ptv-optima-vv.n.xxxxx/optima_install/Linux/postgresql
6. Execute the script:
   ./sh installPostgresql-ONLINE.sh

On the DB server:

1. Execute:

   cd /opt/optima_zip/ptv-optima-vv.n.xxxxx/optima_install/Linux

2. Execute:
   sh Configure-HugePages.sh –h hugepages -r 0.7

Tip:  In step 2, we have chosen 70% of the total memory. For details on DB performance configuration: → Performance (support issues).

To check whether the current locale has been set:

1. On the DB server, run the command perl -e exit.

2. If the command fails with a warning message similar to the image, the current locale has not been set.

   

Important:  If the current locale has not been set, you need to install the missing locale (it_IT.UTF-8 in the example) when prompted during the DB setup procedure. The additional locale must not be set as default but must be generated as indicated in Step 4.

1. Run the command for your relevant continent and location:
   timedatectl set-timezone zone

   For example:
   timedatectl set-timezone Europe/Rome

2. Check whether the timezone has been changed correctly by running the command:
   timedatectl

1. On a server with .NET software (v8) installed, open the folder:

   cd /opt/optima_zip/

2. Copy the file
   Optima-vv.n.xxxxx.zip
   to:
   opt/optima_zip/

3. Extract the archive in: opt/optima_zip/Optima-vv.n.xxxxx

   You get a list of zipped files

4. Extract the archive ptv-optima-db.zip

   You now see the folder ptv-optima-db

5. Change the directory:

   cd /opt/optima_zip/ptv-optima-db/creation_scripts

6. Run the script:

   bash create-empty-db.sh

   The script asks you to set three parameters:

   • DB NAME (Default value: optima)

   • DB USER (Default value: postgres)

   • DB HOST (Default value: 127.0.0.1 (local host))

     

     Tip:  You can confirm default values or you can set your own specific values.

     The outcome is the creation of the empty Optima DB schema.

7. Verify the success of the previous step:

   1. Open pgAdmin 4.
   2. Connect to the DB_SERVER_IP address, using the default username and password (→ Installation conventions to follow).
   3. Make sure that there are over 200 tables under Server Groups > Servers > PostgreSQL 17 > Databases > optima > schema > public > tables.

To load the model into the empty database, you can use the Transportation Data Exchange component (TDE).

1. On the .NET server, check whether custom scripts are available ([…]/optima_zip/PTV-Optima-vv.n.xxxxx/Custom_SQL).

2. Use the pgAdmin tool to execute the SQL custom scripts as provided in the folder (e.g. 00-Before_TDE.sql or the script 00-PreFill.sql. Ensure whether it is necessary to run some scripts before (AND after) deploying the model in the database).

3. Extract the archive
   […]/PTV-Optima-vv.n.xxxxx/TDE-vv.n.xxxxxx.zip
   to:
   opt/ptv-optima-TDE

4. Copy all network model files (.net, .dmd, .xml, and tprb.sql for both the simulation model and for the current model) from
   […]/optima_zip/PTV-Optima-vv.n.xxxxx/Visum_Model/
   to:
   opt/ptv-optima-TDE/model_update/

5. If your PTV project manager has given you a TDE configuration file CommandLineTDE.csv, copy this file to: opt/ptv-optima-TDE/

   If you have not been given this configuration file:

   1. Copy the file opt/ptv-optima-TDE/config-templates/CommandLineTDE.csv

      to: opt/ptv-optima-TDE

   2. Open the copy of CommandLineTDE.csv with a text editor.

      For a detailed description of TDE configuration: → Transportation Data Exchange (TDE).

      Important:  Each variable value is given directly below the variable name. All subsequent rows up to the next variable name are ignored. A value of −1 forces TDE to get the value from the DS_MAIN datasource. A value of −2 forces TDE to ignore a specific variable in the configuration file. This makes it possible to skip the import of specific parts of the model.

   3. Configure the main datasource DS_MAIN to connect to the simulation model. For Visum export files named <simmod_filename>.net, .xml, .dmd, insert visum:/.../model_update/<simmod_filename> with no extension.

   4. Configure the output datasource DS_OPUT to connect to the database where the result will be stored:
      postgresql:Server=DB_SERVER_IP;Port=5432;Uid=postgres;
      Pwd=postgres;Database=optima;CommandTimeout=3600

      Replace DB_SERVER_IP with the IP address of the DB server hosting PostgreSQL ver. 17.4.

6. Create a database backup.

   Caution:  Do not skip this step! The DB backup is necessary to restore it in case of unexpected fails.

   1. Open pgAdmin 4.
   2. Click Server Groups > Servers > PostgreSQL 17 > Databases > optima to connect to the DB that you have created in the previous steps.
   3. Right-click and choose Backup.
   4. Choose the backup folder, for example: opt/ptv-optima-DB.xxx.

7. Double-click the executable file: C:\optima\TDE\TDE_GUI.exe

   A dialog box opens. It shows the configuration review panel to run the TDE software.

8. Click Execute.

   The operation can take some time, depending on the size of the model.

9. If the folder model contains additional scripts, such as .sql or .backup, restore them with pgAdmin 4.

   For .sql files:

   1. Open pgAdmin 4.
   2. Press Ctrl+E to open the Query Manager.
   3. On the File menu, click Open to execute the .sql.

   For .backup files:

   1. Open pgAdmin 4.
   2. Browse to the Optima DB.
   3. Right-click the DB or a specific table.
   4. Right-click and choose Restore.
   5. On the Restore Options#1 tab, set the parameter Type of object to only data.

The DB hosts now the network model.

On the .NET server:

1. Open the TDE log file:

   C:\optima\TDE\LogFile_TDE_GUI.log

   Important:  It is MANDATORY to check for the absence of ERROR messages in the log file.

2. Open pgAdmin 4.

3. Click Ctrl+E to open the Query Manager.

4. Execute the following queries to verify basic database integrity (click F5 to execute a query):

   • SELECT COUNT(*) from link must return the number of assignment links of the model (greater than zero).
   • SELECT COUNT(*) from strt must match the number of links in the Navteq network (greater than zero).
   • SELECT COUNT(*) from lkst must be greater than zero.

If all the checks listed have been successful, you get a valid DB.

1. On the Optima AS, copy the folder
   /opt/optima_zip/ptv-optima-vv.n.xxxxx/ptv-optima-as/
   to
   /opt/ptv-optima-as
2. With a text editor, open the configuration file:
   /opt/ptv-optima-as/bin/standalone.conf
   

3. Make sure that the following parameters have been set as recommended in the table below. The minimum setup requires the setting for -Xmx.

   Java parameter	Definition	Values to use
   -Xms	Minimum RAM	-Xms3G Change according to the model size.
   -Xmx	Maximum RAM usage	-Xmx4G Example: -Xmx4G allows the Optima application server to use up to 4 GB of RAM. Change according to the model size. Typical configurations depend on the amount of RAM available on the machine and on the specific Optima installation. Usually 80% of the RAM available is a correct value.
   -XX:+UseG1GC		-XX:+UseG1GC Important:  Enabled by default in Java 11.
   -XX: -UseAdaptiveSizePolicy		Important:  Enabled by default in Java 11.
   -XX:SurvivorRatio=1
   -XX:+UseLargePages		To calculate the parameters for Large Memory Pages see here.

4. Change the folder:
   cd /opt/optima_zip/optima_install/Linux/java

5. Execute:
   sh Configure-HugePages.sh –g hugepages -r 0.7

Important:  You need to perform this task ONLY if you need to run TS (→ Traffic Operator’s Guide TS).

1. On the Optima AS, with a text editor open the file:
   /opt/ptv-optima-as/standalone/configuration/standalone.xml
   

2. Search for the node <datasources> and find the row <datasource> that contains enable=TRUE.

   Add the database parameters to the subnode <connection-url>. If you have followed the previous instructions, this is:

   <connection-url>
   jdbc:postgresql_postGIS://DB_SERVER_IP:5432/optima
   </connection-url>

   Replace DB_SERVER_IP with the IP address of the database server on which PostgreSQL has been installed. Should you have set a different port for the database when you installed PostgreSQL, change the port number 5432 according to the port number that you have used.

3. Search for the node <security>.

4. Make sure that both <username> and <password> have been set to postgres:

   <security>
   
   <user-name>postgres</user-name>
   
   <password>postgres</password>
   
   </security>

5. Save the file standalone.xml.

6. If the Traffic Supervisor module is deployed, you need to configure the correct time zone.

   In the file /opt/ptv-optima-as/standalone/configuration/optima/optima-configuration.xml, find the node <TSTimezone> (→ <TSTimezone> tag) where you can set the time zone of the network and model.

   For information on time zones, see https://en.wikipedia.org/wiki/List_of_tz_database_time_zones.

   Example:
   

   <TSTimezone>Europe/Rome</TSTimezone>

   In the subnode <TSTimezone>, set the time zone of the network and model. For information on time zones, see: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones

   Example:
   
   <TSTimezone>Europe/Rome</TSTimezone>

7. Save the file /opt/ptv-optima-as/standalone/configuration/optima/optima-configuration.xml

The AS can be configured to send log errors via e-mail.

The feature can be useful for different goals.

For examples, TomTom and INRIX interfaces can notify the map version changes.

Setting SMTP alerts

In a Windows environment, update the file:

C:\optima\ptv-optima-as\standalone\configuration\standalone.xml

In a Linux environment, update the file:

/opt/ptv-optima-as/standalone/configuration/standalone.xml

The information to be updated is:

• Handler (<custom-handler name="emailHandler"/>).
• E-mail address of the sender ("From").
• E-mail address of the receiver ("To").
• Host name of the SMTP server to send the e-mail ("SMTPHost").
• Port number of the SMTP server to send the e-mail ("SMTPPort").

Example:

<custom-handler name="emailHandler" class="org.apache.log4j.net.SMTPAppender" module="org.apache.log4j">
    <level name="ERROR"/>
    <formatter>
        <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
    </formatter>
    <properties>
        <property name="BufferSize" value="1"/>
        <property name="From" value="name.surname@ptvgroup.com"/>
        <property name="To" value="name.surname@ptvgroup.com"/>
        <property name="Subject" value="Optima Warning"/>
        <property name="SMTPHost" value="${env.MAIL_SMTP_SOCKET_HOST:localhost}"/>
        <property name="SMTPPort" value="${env.MAIL_SMTP_SOCKET_PORT:25}"/>
     </properties>
</custom-handler>

        

1. On the Optima AS, press Ctrl+Alt+T to open a bash shell.

2. To log in with administrator rights, execute:
   su

   When prompted, enter the root password.

3. Change folder:

   cd /opt/optima_zip/optima_install/Linux/java

4. Execute:

   sh as-configure.sh

5. To start the Optima application server, execute:
   service ptv-optima-as start

6. To start a Linux service, run:

   systemctl start ptv-optima-servicename

   where servicename can be:

   • tre

   • hyperpath

   • planning

   • as

   • vt

   • vms

   • other service

Along with the Optima AS, a number of other services should also start automatically, depending on which services are included in your Optima license. These services are:

• ts (Traffic Supervisor) with webcheck: 127.0.0.1:8080/ts <administrator user-name>:<administrator password>
• optima-wsi (Optima Web Server Interface)
• OptimaControl
• harmonizer
• geoserver
• dbworker
• datex2import

You can see whether these services have been correctly deployed in the folder: /opt/ptv-optima-as/standalone/deployments/

1. On the .NET server, run the service of the .NET component that you want to start.
2. Open and check the corresponding log file to verify whether the procedure has been successful.