• No results found

bootconfig/admin folder.

config.names=rc-default

config.rc-default.deploy.dir=<Location of the apps folder> Example:<middleware.home>/apps

app.store.type=FILE

app.store.location=<Location of the appstore folder> Example:<middleware.home>/appstore

Un comment as displayed below: config.rc-default.type=Weblogic

config.rc-default.host=<Managed server IP address>

config.rc-default.port=<Managed server HTTP port number> config.rc-default.deploy.dir=/home/core/install/apps

3.5.5 Access Admin Module

Perform the following steps to access Admin Module.

1. Open a web browser and type

http://<Host Name or IP

address>/admin/console

.

2. Login to the console by providing theadminusername and password for authentication.

3.6 Install Reporting Agent

To install the reporting agent, perform the following steps:

n Copy reporting agent files n Configure the files

3.6.1 Copy reporting agent files

1. Create a folder with the name

konylogdaemon

under

/home/core.

2. Extract

konylogconfig.tar

and

logdaemon.tar

files in

/home/core/konylogdaemon

folder.

3.6.2 Configure the files

Perform the following steps to configure the files.

1. Navigate to

/home/core/install/konylogdaemon

folder.

2. Edit the file

logdaemon-jndi.properties

and make the following changes: The below changes are for reading the log messages from the JMS queue.

#-- START - Specific weblogic JMS Server context properties. server=weblogic

java.naming.factory.initial=weblogic.jndi.WLInitialContextFacto ry

logdaemon.topic=jms/KonyLogTopic

logdaemon.connectionfactory=jms/KonyConnectionFactory hibernate.config.xml.dir=

failover.retries=100 failover.duration=10000

### Start - Database Test Query for testing DB connection #Oracle and MySql server database query for

database.query=select 1 from dual #database query for MS SQL Server #database.query=select 1

#DB2 database query

#database.query=select current_timestamp from sysibm.sysdummy1; ### END - Database Test Query for testing DB connection

#size of each batch before updating it to DB Server. metrics.update.batchsize=50

csr.update.batchsize=10 logger.update.batchsize=25 download.update.batchsize=50

#LOG Listener ID and Kony log listener ID

kony.logging.listener.clientid=KonyLoggingListener logging.listener=LoggingListener

#Specify delimiter here Eg.ndc.delimiter=\\t ndc.delimiter=\\n

The above configuration is applicable only if development and Quality Analysis servers are in theDeployment Configuration 1,

3. if your are intended to use Deployment Configuration 2, then you can follow the given example where multiple Connection Factories, Topics, each targeted on different JMS Server. Each Connection Factory, Topic,

kony.logging.listener.clientid and logging.listener have a different JNDI name. so, They should be pointed appropriately as displayed in the following example:

Note:For example if you need to configure the Multiple managed servers, multiple JMS servers, you need to modify the below properties in Logdaemon- jndi-properties of logdaemon. • First logdaemon logdaemon.topic=jms/KonyLogTopic logdaemon.connectionfactory=jms/KonyConnectionFactory kony.logging.listener.clientid=KonyLoggingListener logging.listener=LoggingListener • Second logdaemon

logdaemon.topic=jms/KonyLogTopic1 logdaemon.connectionfactory=jms/KonyConnectionFactory1 kony.logging.listener.clientid=KonyLoggingListener1 logging.listener=LoggingListener1 • Third logdaemon logdaemon.topic=jms/KonyLogTopic2 logdaemon.connectionfactory=jms/KonyConnectionFactory2 kony.logging.listener.clientid=KonyLoggingListener2 logging.listener=LoggingListener2

To improve the performance of the reporting agent, sql inserts are batched based on the number given below:

For metrics info batch:

metrics.update.batchsize=50

Valid for Mobile Web - When any exception occurs in jsp page, a message is logged:

csr.update.batchsize=10

General logs:

logger.update.batchsize=25

Comment the line below:

download.update.batchsize=50

Unique IDs specific to the reporting agent. In theDeployment Configuration 2, we configure multiple JMS Servers each targeted on one Managed Server. In this case, we have to run multiple Reporting Agents and ensure that each agent has a unique clientId.

kony.logging.listener.clientid=KonyLoggingListener logging.listener=LoggingListener

NDC Delimiter is specific to logging in debug and non debug mode. This

specifies the separator between the log messages. Traditional values used are \n for new line and \t for tab. This property should match the delimiter set for ndc.delimiter in middleware.properties file.

ndc.delimiter=\n

4. UnderJNDI servicessection, enter the topic and connection factory information. The topic and connection factory is previously created under Configure JMS Serversection.

5. Edit the file

hibernate.cfg.xml

and provide the IP address, database user ID and password in the following lines. This configuration is to ensure that the messages are stored to the database.

$ vi hibernate.cfg.xml

<property name="connection.driver_class">oracle.jdbc.driver. OracleDriver</property>

<property name="connection.url">jdbc:oracle:thin:@<IP address>: 1521:<DBName></property>

<property name="connection.username">Kony LogDB Username</property>

<property name="connection.password">Kony LogDB Password</property>

<property

name="dialect">org.hibernate.dialect.Oracle10gDialect</propert y>

<!-- These properties are specific to MySql Database -->

<property name="connection.driver_

class">com.mysql.jdbc.Driver</property>

<property name="connection.url">jdbc:mysql://<IP address>: 3306:<DBName>?&amp;rewriteBatchedStatements=true</property> <property name="connection.username">Kony LogDB

Username</property>

<property name="connection.password">Kony LogDB Password</property>

<property

name="dialect">org.hibernate.dialect.MySQLDialect</property>

<!-- These properties are specific to DB2 Database -->

<property name="connection.driver_ class">com.ibm.db2.jcc.DB2Driver </property> <property name="connection.url">jdbc:db2://<IP address/hostname>:50000:DBName</property> <property name="connection.username">Kony LogDBUsername</property> <property name="connection.password">Kony LogDBPassword</property> <property name="dialect">org.hibernate.dialect.DB2Dialect</property>

<!-- These properties are specific to SQL Server Database -->

<property name="connection.driver_ class">com.microsoft.sqlserver.jdbc.SQLServerDriver</property> <property name="connection.url">jdbc:sqlserver:// <DBIPADDRESS:port;databaseName=DBNAME</property> <property name="connection.username">DBUSERNAME</property> <property name="connection.password">PASSWORD</property> <property name="default_schema">konylogdb</property>

<property name="dialect">org.hibernate.dialect. SQLServerDialect</property>

6. Edit the file

rundaemon.sh.

i. Ensure that the JAVA_HOME is set properly as per Sun JDK or JRockit. ii. Set the

-Dkonylogdaemon.home

property to point to the location of the

property files and XMLfiles. In our case, it is

-

Related documents