Configure Jboss 5.1 Server

This section is applicable if you are using JBoss as the J2EE Web container for the setup. Before you begin, you must configure the JBoss Server with the configuration that provides Datasource services or continue with the default configuration provided out of the box.

After you configure the JBoss server, you must perform these operations:

• Configure JBoss Server
• Configure Datasources
• Deploy Kony MobileFabric Engagement Services

Configure JBoss Server

You must configure the JBoss Server to provide the memory arguments and the location of the Kony MobileFabric Engagement Services configuration files.

To configure the JBoss server, follow these steps:

1. Navigate to <JBoss Install Directory>/bin.
2. Modify run.sh file with the following parameters:

   Parameters (for JVM)	Required	Description
   -Xmx2048m	Yes	Minimum Heap size: 2GB
   -Xms2048m	Yes	Maximum Heap size: 2GB
   -XX:MaxPermSize=512m	Yes	One fourth of the main Heap memory assigned
   -XX:UseParallelGC	Yes	This is a recommended setting
   -Dkpns.configLocation	Yes	This is the directory where the configResource.properties, database.properties, and kpns-log4j.properties files must be placed. For example, if the location is/data/kpns-config, then you must specify the property as -Dkpns.configLocation=/data/kpns-config
   -Dhibernate.dialect	Enables you to connect to the database. JDBC has to be configured on the AppServer level.	Oracle= org.hibernate.dialect. Oracle10gDialect

3. -Xms2048m –Xmx2048m -Dkpns.configLocation=/data/kpns-config

4. Save the configuration.
5. Remove the default quart and mail lib from the following path (quartz.jar, mail.jar).

   <JBoss Install Directory>/common/lib

Configure Datasource

To configure the datasource, follow these steps:

1. Navigate to the location where you have extracted the kpns-resources.tar file.
2. From the jboss folder, copy <name>-ds.xmlfile to <JBoss Install Directory>/server/<configuration>/deploy/. If required you can rename this file.
3. Modify the attributes of <name>-ds.xmlfile with the values which are appropriate as per your database configuration.

   For Oracle, DB2, and MySQL, the <name>-ds.xmlfile has the following attributes:

   Attribute	Required	Description
   ndi-name	Yes	Specifies the JNDI name (schema name) under, which the Datasource should be bound
   connection-url	Yes	Specifies the JDBC driver connection url string
   driver-class	Yes	Specifies the JDBC driver class implementing java.sql.Driver
   DatabaseName	Yes	Specifies the name of the database
   user-name	Yes	Specifies the username used when establishing the connection
   password	Yes	Specifies the password used when establishing the connection
   type-mapping	Yes	This element defines a default type mapping for a data source

   For Microsoft SQL Server, the <<name>>-ds.xml file has the following attributes:

   Attribute	Required	Description
   ndi-name	Yes	Specifies the JNDI name (schema name) under which the Datasource should be bound
   connection-url	Yes	Specifies the JDBC driver connection URL string
   driver-class	Yes	Specifies the JDBC driver class implementing java.sql.Driver
   DatabaseName	Yes	Specifies the name of the database.
   user-name	Yes	Specifies the username used when establishing the connection
   password	Yes	Specifies the password used when establishing the connection
   type-mapping	Yes	This element defines a default type mapping for a data source.

   Example Snippets:

   Important: The configurations and examples in this document are provided for a better understanding of the concepts. We encourage you not to copy-paste them for your installation execution as they may not match your settings. For example, user names, passwords, IP addresses, and port numbers.

   <datasources>
       <local-tx-datasource>
           <jndi-name>kpnsdb</jndi-name>
           <use-java-context>false</use-java-context>
   
   <!-- Specify the DatabaseName parameter as KPNSDB for push notifications
   -->
           <connection-url>jdbc:sqlserver://<ipaddress>;
   DatabaseName=KPNSDB</connection-url>
   
   
   <!-- Specify the driver class based on the database selected-->
           <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver
   </driver-class>
   
   <!-- If the target database is oracle, the username would be KPNSDB-->
   	<user-name>dbclient</user-name>
   	<password>kony@123</password>
   	<!-- sql to call when connection is created -->
   	<pool>
   	<min-pool-size>5</min-pool-size>
   	<max-pool-size>50</max-pool-size>
   	</pool>
   	<idle-timeout-minutes>20</idle-timeout-minutes>
   	<statement>
   	<track-statements>false</track-statements>
   	</statement>
   	<metadata>
   	<type-mapping>mySQL</type-mapping>
   <!-- the type mapping values examples are as follows:
   DB2, Oracle10g, MS SQLSERVER2000-->
   	</metadata>
   	</local-tx-datasource>
   </datasources>

   To enable the push configure maintain <<name>>-ds.xmlfile.

   Note: Database schema name should be in capital letters like KPNSDB.

   Note: The Database driver must be placed in the JBoss Server lib directory.

   Note: For Jboss with Oralce database, use ojdbc14.jar as db driver

4. Save the configuration.
5. Remove the default quartz.jar located in the following path

   <jboss_intstall_dir>\common\lib

Deploy KPNS

1. To deploy KPNS on the JBoss Server, copy kpns.war file to the following location:
   <JBoss Install Directory>/server/<configuration>/deploy/
2. After you deploy KPNS, complete the KPNS setup and start the JBoss Server.

Copyright © 2015 Temenos AG. All rights reserved.