On This Page:

Configuration Files

After ServiceManager has been installed, it may be desirable or necessary to change some of the configuration parameters that were set during the installation process.

The following list provides details of where these configuration parameters can be found in ServiceManager's configuration files.

Web Application Name

If the ServiceManager application requires renaming then the web application archive (SERVICEManager.war) located within the SVM_HOME/tomcat/webapps directory should be renamed appropriately prior to starting the application server.

Within the Java application server environment it is the name of the application archive (WAR file) that determines the name of the web application. This is case sensitive and the name is reflected in the URL specified by the client browser.

For example if the WAR file were renamed svm-demo.war then the URL would include the application name svm-demo similar to: http://spower:8080/svm-demo. However if the WAR file was renamed to SVM-demo then the connection URL would be similar to: http://spower:8080/SVM-demo.

Note that the WAR file should be renamed and not copied. Java application servers check their respective webapps directory for WAR files. Any such file is assumed to be the archive for a web application, copying the file would result in the application server instance hosting in effect two ServiceManager application instances each with a unique URL.

SOAP URL & User Name

The SOAP URL & user name are specified within the service_manager.properties file, which is located within the sm_properties directory of the installation.

service_manager.properties

###################################################################################################
# Name: service_manager.properties
# Desc: This is an example of the main ServiceManager properties file.  All of the settings within 
#       this file need to be specified in order for ServiceManager to work correctly.
#
#       The location of this properties file is dependent upon the system property:
#       "com.servicepower.servicemanager.propertiesFile" which should be the location of the
#       file in question.
###################################################################################################
# properties for SOAP interaction.  In order for ServiceManager to interact with the ServiceOptimizer
# SOAP server the following information *must* be correct.
#
# soap.server.url - the protocol://server:port_no
# soap.login.dbusername - the user name used by ServiceOptimizer to connect to the database with
soap.server.url=http://www.mycompany.com:18081
soap.login.dbuser=dbuser

Database Connection Details

ServiceManager retrieves most of the information it requires from the ServiceScheduling’s database, to do this the appropriate database connectivity method needs to be defined. Specifically the database type, connection URL, trusted user and password information.

This information must reside within the hibernate.cfg.xml file located within the sm_properties directory of the ServiceManager installation.

The installed version of this file contains two commented out XML definitions for the database connection - one for Oracle and one for SQL Server. Copy, and remove the comments of, the appropriate XML definition and specify the connection URL and username/password combination.

Session Factory

<session-factory>
 
  <!--  
    #########################################################################################
    # The following properties are provided as examples of how to configure SERVICEManager  #
    # for use with either Oracle or Microsoft's SQLServer database products.                #
    #                                                                                       #
    # Uncomment the required section and amend according to the installation requirements   #
    #########################################################################################
  -->

  <!-- 
    #############################
    # Oracle Connection Details #
    #############################
	<property name="connection.url">jdbc:oracle:thin:@<??machine-name??>:1521:<??oracle sid??></property>
	<property name="connection.username">user</property>
	<property name="connection.password">pass</property>
	<property name="connection.driver_class">oracle.jdbc.OracleDriver</property>
	<property name="dialect">org.hibernate.dialect.OracleDialect</property>
  -->
	
  <!-- 
    ##########################################
    # Microsoft SQLServer Connection Details #
    ##########################################
	<property name="connection.url">
      jdbc:jtds:sqlserver://<??machine-name??>:1433;databaseName=<??database name??>;sendStringParametersAsUnicode=false
    </property>
	<property name="connection.username">user</property>
	<property name="connection.password">pass</property>
	<property name="connection.driver_class">net.sourceforge.jtds.jdbc.Driver</property>
	<property name="dialect">org.hibernate.dialect.SQLServerDialect</property>
  -->
 
</session-factory>

Database Pooling

ServiceManager utilises the Hibernate Object Relational Mapping framework to retrieve data from and persist data to the ServiceScheduling database schema. A full specification of Hibernate can be obtained at from the Hibernate Organisation website http://hibernate.org/, but details of configuring Hibernate to employ a connection pooling strategy are described here.

In addition to the connection, administrators should ensure that a suitable pooling configuration is setup in order to achieve optimum performance and scalability. By default ServiceManager is supplied with a generalised connection pool setup. This is achieved by adding the following entries to hibernate.cfg.xml within the <session-factory> section.

When Tomcat is started this will result in an initial number (hibernate.c3p0.min_size) of connections being made to the ServiceScheduling database. Additional connections will be added to the pool up to the hibernate.c3p0.max_size setting when this pool is exhausted. For further details on how to modify these settings for your specific requirements refer to the C3P0 section in the Hibernate Organisation website.

Connection Pool management

<session-factory>
 
  <!--  
    #########################################################################################
    # The following properties configure the C3P0 connection pool used by SERVICEManager    #
    # and *MUST* be configured in accordance with the SERVICEManager projected load.        #
    #                                                                                       #
    # A default configuration is provided. For additional detail refer to the configuration #
    # guide at http://www.hibernate.org/214.html                                            #
    #########################################################################################
  -->
    
  <property name="hibernate.connection.provider_class">
    org.hibernate.connection.C3P0ConnectionProvider
  </property>

  <property name="hibernate.c3p0.min_size">5</property>
  <property name="hibernate.c3p0.max_size">25</property>
 
   <!-- 30 mins idle timeout -->
  <property name="hibernate.c3p0.timeout">1800</property>
  <property name="hibernate.c3p0.max_statements">0</property>
 
  <!-- 10 mins force close any connections that are left open -->
  <property name="hibernate.c3p0.unreturnedConnectionTimeout">600</property>
 
</session-factory>

Single Sign-On

ServiceManager supports Single Sign-On via ServiceBroker.

To configure Single Sign-On, update the application.properties file to set values for the following configuration options:

sso.brokerUrl
sso.reqauthorize
sso.token
sso.scopeId

Speak to your ServicePower consultant for the values to use for these configuration options, as they are specific to your ServiceBroker instance.

Browser not supported