Security Server Installation (Akka)

Installation

The installation of the SecurityServer is fairly easy. As it is shipped as a ZIP file, you only have to extract it into a location of your choice. Keep in mind that the application uses java, so you must not use blanks within your SecurityServer path.

The following steps are necessary to install the SecurityServer prerequisites:

  • Install a Java JDK
  • Install the Java Cryptography Extension “unlimited strength”
  • Install necessary JDBC / database drivers
  • Create Tables
  • Installation as service

After the installation has been completed, the securityserver must be integrated into B2B. The integration is not part of this chapter.

Install a Java JDK

A supported Java JDK may be downloaded from http://www.oracle.com/technetwork/java/javase/downloads/index.html. Follow the installation instructions that will guide you through the installation process. Configure the used jdk within the start-script or the service-wrapper.

Install the Java Cryptography Extension

It is important to install the Java Cryptography Extension “unlimited strength” to the JVM of the SecurityServer to ensure compatibility to other systems. It is important to install the version that matches your JDK version. Typically, the Extension is available at http://www.oracle.com/technetwork/java/javase/downloads/index.html, listed under Additional Resources.

The downloaded archive needs to be extracted to a temporary folder. Then, the following files must be copied to the specific JDK’s embedded JRE, to the folder \lib\security:

Install Database Driver

Analog to your B2B-Installation, your JDBC/database driver has to be placed into the lib folder of the SecurityServer.

Create Tables

The database tables can be created via SQL-Scripts. You get the current scripts from our support.

Serviceinstallation

The SecurityServer can also be installed as a windows service, do this with the “service install”-command within the bin-folder.

Configuration

The following steps are necessary to set up the SecurityServer in a way that it matches your environment:

  • Change the hibernate configuration file to provide access to your database
  • Change the Akka configuration file to match your local settings
  • Change the application configuration to set up the communication ports
  • Load or update the database structure

Change the Hibernate configuration

The Hibernate configuration takes all properties that are needed to communicate with a given database. The SecurityServer manages all installed certificates and private key in that database. From there the application initializes the appropriate keystores at start-up. You need to change the following settings of hibernate.cfg.xml mentioned in the table below.

Attribute Value Description
connection.driver_class e.g. oracle.jdbc.OracleDriver Full qualified classname of the jdbc driver for your database
connection.url jdbc:oracle:thin:@b2bp:1523/B2BP JDBC Url, based on the specification of your jdbc driver
connection.username Admin Username, that needs to connect to the database
connection.password ** password
Dialect com.nextlevel.security.persistence.dialect.  
Oracle10gSecServerDialect Dialect to use for datatype mappings and SQL optimization. SQL Dialects  

Advanced dialect settings

There may be specific settings necessary regarding certain database technologies. Those settings will be described here.

  • Oracle database users: It is recommended to use the following Hibernate dialect: com.nextlevel.security.persistence.dialect.Oracle10gSecServerDialect
  • MS SQL Server database users: It is recommended to use the following Hibernate dialect: com.nextlevel.security.persistence.dialect.MSSQL12SecServerDialect

Change the Akka Configuration

Before you can start the SecurityServer, you must also change the following configuration file conf/common.conf. Please change the hostname settings to the correct value of the SecurityServer host name.

Change the Application ports

The SecurityServer akka port (remote.netty.port) is defined in conf/application.conf. The value needs to be set to a value that will interact with the corresponding B2B by practice installation.

Load or update the database structure

The SecurityServer needs several tables. If you integrate the SecurityServer into an application that already uses a database, you can add the tables there.

The needed database scripts can be aquired from our support team.

View Me   Edit Me