PTM installation

Due to modifications in the XML schemas used in the web services used for communication at the T1 interface there has been a new subfolder (ptm/opensource-tgw-compliant) in the svn that contains the adapted service assemblies indicated below

Install  Glassfish ESB.
During the installation you will be asked for providing an admin user name and password (you may select the default values). Once the installation is complete you can start the AS by invoking start_glassfish_domain from the directory where you have installed it.
You will be asked for the admin credentials and also for another master pwd.

Credentials and security related material

Use credentials: user=admin, pass=adminadmin, masterpwd=changeit
The master password is the passphrase required to administer the certificate repositories:

• glassfish/domains/domain1/config/keystore.jks
• glassfish/domains/domain1/config/cacerts

The first one contains the private key and certificate for the AS. This is created during installation.
The second one contains all the trusted certificates of the AS.

mySQL Server

You need to have a mysql server running on the machine. Create a database with name: pii by using the  db.sql script to generate the tables and also store some data in the types table. In the script there is an entry regarding the identifier of the PTM (octo, eict, uop, fhg, etc.) replace it appropriately (it should be the same with the one used in Teagle).

Configuring Glassfish

Connect to the admin web i/f of glassfish by pointing to  http://{host address}:4848/ and log in with the admin credentials.

Installing mysql-connector-java

• For a mysql database you need the appropriate database connector.
• Go to the  MySQL website and download the Java connector for your platform, e.g. for Linux from  here
• Extract and install the archive according to the selected version's installation instructions, e.g. under /usr/local/mysql-connector-java
• In the Glassfish management web console, click on Application Server and the JVM Settings tab.
• The Path Settings tab allows customization of the classpath variables used by Glassfish
• Add the directory, where your mysql-connector-java JAR archive is located at, to the system classpath by adding the following line: /usr/local/mysql-connector-java/mysql-connector-java-5.1.x-bin.jar
• click Save to make your configuration changes permanent

alternatively you can copy the jar file mysql-connector-java-5.1.x-bin.jar into the jre/lib/ext folder of your Java installation that Glassfish has been configured to use.

Installing a JDBC connection pool element

On the left hand side of the console you will locate the "resources" menu, expand it until you reach the JDBC elements. From the root of the connection pools (select new from the right frame) create a new connection pool (mySQL_local) as indicated in the figure



In the Additional Properties you may have to configure "username" and "password" properties depending on the mySQL server settings and user privileges. Once you save it, select ping from the General tab to ensure that the configuration is valid. Normally absence of credentials or of the mySQL connector causes a failure.

Just above the pool select JDBC Resource and submit a new one as indicate in the figure (jdbc/mySQL_local)

Install PTM Core Application Assemblies

From the menu JBI->Service Assemblies deploy:

•  PTM-CORE-RAL-CA and
•  T1-Adapter-CA

IMPORTANT: There is a case that some service units in either CA may be in unknown state, try redeploying the CA to ensure that they appear as "started" (see figures).

Configuring Secure T1

The T1 Connection the communication link between the TeagleGW and a PTM. This is established over a TLS channel that requires mutual authentication of the two ends. T1Adapter is already configured to expose an https based interface at port 9181 (see [wiki:CorePTM). In order to enable allow for mutual authentication you have to switch "(SSL)Client authentication enabled" to true from the configuration of the sun-http-binding JBI component(JBI> Components> sun-http-binding configuration tab):



Additionally you have to insert into glassfish/domains/domain1/config/cacerts the  Teagle GW Certificate. This is done by use of the following Java command (it must be on the path):

keytool -import -file {path_to}/TeagleGW.crt -alias teaglegw -keystore  {path_to}/glassfish/domains/domain1/config/cacerts.jks

IMPORTANT Use the correct keytool for your installed JVM. If you have multiple java builds (GNU, blackdown, SUN) installed, you should use the correct keytool from your version. Otherwise, strange things may occur. Note that the default CA certificate file is named cacerts.jks with the java keystore extension .jks.

You have to restart Glassfish so that the new entry is enumerated. Check again the status of the two Service Assemblies to be in the Started State.

Now the core PTM is up and running.

Install PTM Manager

Download the  PTM Manager and deploy the war file as a new web application (Applications> Web Applications)

Resource Adapter Layer Installation

Setup the RAL environment on the same machine. Download  Oscar and extract it. Create a .oscar directory in your home folder and extract there the  Oscar Profile. This archive contains the basic installation of the RAL.

launch oscar (java should be in the path) from the oscar_install dir using the oschar.sh script. Select pii-ral-cmd when prompted for a profile.

Use the PTM Manager interface to administer RAL as described in Resource Adaptation Layer.