Table of Contents. 2

Revisions. 3

Introduction. 4

Startup / Shutdown of the application server 5

Accessing the Wildly administration console. 6

Monitoring the application Server 8

Locating CRM.COM application log files. 12

Overview 

This document provides information and “how-to” procedures to system administrators to be able to monitor and administer the CRM.COM application server.

The following areas are included:

1. Startup / Shutdown of the application server
2. Accessing the Wildly administration console
3. Monitoring the application Server
4. Locating CRM.COM application log files  

Startup / Shutdown of the application server

The application server is installed as a service called wildfly. Therefore, to start and stop Wildfly the following commands are used:

$ sudo service wildfly start 

$ sudo service wildfly stop 

To verify that Wildfly is running you can use the netstat stat command. Widlfy is listening to the following ports:

• For http -> 28080
• For https -> 28443
• For management -> 9990

$ netstat -lnt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:28009           0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:28080           0.0.0.0:*               LISTEN
tcp        0      0 192.168.122.1:53        0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:28443           0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:9990          0.0.0.0:*               LISTEN
tcp6       0      0 :::22                   :::*                    LISTEN
tcp6       0      0 ::1:6010                :::*                    LISTEN

Accessing the Wildly administration console

Wildfly 10.0 offers an admin console which is web based. It can be accessed using the following URL: http://localhost:9990

Note that for security reasons the console is accessible only from the localhost address (127.0.0.1). Therefore, to be able to access it from your PC we need to use the putty tunneling feature:

 Image Added

One the tunnel is configured then the console is accessible using: http://localhost:9990

You will be asked to authenticate using a valid Wildfly username and password. The username is called admin. The password will be given to you at a later stage.

 Image Added

From the home screen, you can navigate to the area of interest. You can also get on-line help using the links at the bottom right.

Monitoring the application Server

From the Home screen click on:

Image Added

And then click on Standalone Server

Image Added

To monitor the Wildfly java process click on JVM and then View

Image Added

From this screen, you can monitor the JVM memory and also view other useful information like the version of java and OS kernel and the server uptime.

Similarly, you can navigate to other areas like Log Files:

Image Added

The log files are historically date time stamped. The current log file is named server.log.

Click to select a log file and then press View:

Image Added

You can use Find to search for a keyword if needed.

You can monitor the data sources by navigating to: Subsystems->Datasources and pressing View

Then select XA DATA SOURCES tab

Image Added

From this screen, you can monitor connection pool statistics and test the database connections. Also, you can flush idle connections if needed.

Locating CRM.COM application log files

CRM.COM application keep log files under the following directory on each app server: /opt/crm.com/crm/logs

There are many log files depending on the module and are usually added by developers to be able to troubleshoot runtime issues.

The files are usually kept for one month. The name of the file (when referring to the non-current file) includes the Day of the month. For example, the log file for the CRM.COM APIs is called: api_log.txt

If today is 27 Nov 2016 then yesterday’s file is called: api_day_26.txt

Some useful log files are the following:

• api_log.txt – Keeps the requests and responses from in-bound CRM.COM APIs
• usage_log.txt – Keeps memory and active user statistics
• query_errors_log.txt – keeps hibernate query errors
• scheduler_log.txt – keeps scheduler batch run logs (start, duration and any errors)
• Providers/Provisioning Providers/verimatrix_log.txt – keeps API logs for the OMI interface. 

Also under /opt/crm.com/crm/logs directory you can find custom log files specifically created for Econet projects:

• sdp/smsoutbound_log.txt – keeps the requests and responses from out-bound SMS requests to the SMS SDP gateway
• cumii/cumiioutbound_log.txt - keeps the requests and responses from out-bound requests to the CUMII system.