Mobile Money V100R003 Log Reference 01

Mobile Money
V100R003
Log Reference
Issue 01
Date 2017-07-28
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2017-07-28) Huawei Proprietary and Confidential i

Copyright © Huawei
Technologies Co., Ltd.
Mobile Money
Log Reference About This Document
About This Document
Author
Prepared by Wang Wei Date 2017-06-20
Reviewed by Chen Hua, Xiaoce, Date 2017-06-20
Shi Xianglu
Tested by Lei Xiaotian Date 2017-06-21
Approved by Li Shaoshao Date 2017-07-28
Purpose
This document describes the report in the Mobile Money system.
Intended Audience
This document is intended for:
 Technical support engineers
 Maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.
Issue 01 (2017-07-28) Huawei Proprietary and Confidential ii

Copyright © Huawei
Mobile Money
Symbol Description

avoided, may result in minor or moderate injury.

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to
personal injury.
Calls attention to important information, best practices
and tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
Privacy Notice
Some functions provided by the product collect certain subscriber data, such as the subscriber
number and consumption records. The subscriber data is used only to locate or rectify faults.
You are obligated to take considerable measures, in compliance with the laws of the countries
concerned and the user privacy policies of your company, to ensure that the personal data of
users is fully protected. For example, you must reclaim the permission when the
corresponding operator's position is changed. The functions require privacy protection
measurements include but are not limited to the following:
 Data backup function
To avoid data change by mistake, which can result in system faults or subscriber data
faults, the product prompts carriers to back up data periodically. The data may involve
subscriber information, such as the subscriber number, account balance, consumption
fees saved in the Oracle database. The backup data can be used only for data recovery,
but not for personal use or other purposes. After the storage period, backup data must be
timely deleted.
 Fault information collection function
To find the fault reasons, necessary service logs may need to be collected, and the logs
may contain subscriber information such as the subscriber number, account balance,
consumption fees. During use, you are advised to use the anonymization tool to hide
subscriber information. When related faults are located, you must delete the logs in a
timely manner.
Issue 01 (2017-07-28) Huawei Proprietary and Confidential iii

Copyright © Huawei
Mobile Money
Huawei support engineers can perform maintenance operations only after being authorized by
the customer, and are forbidden to perform any operations that are not approved by the
customer. In addition, fault-locating data can be transferred out of the customer's network
only when authorized by the customer in strict accordance with local laws and regulations.
After a service is complete, private data must be deleted under the supervision of the
customer.
Database Operation Notice

All database operations are for reference only and can be performed only by Huawei
engineers.
Change History
Changes between document versions are cumulative. Therefore, the latest document issue
contains all changes made in previous issues.
Issue 01 (2017-07-28)
This is the first issue of the document.
Issue 01 (2017-07-28) Huawei Proprietary and Confidential iv

Copyright © Huawei
Mobile Money
Log Reference Contents
Contents
About This Document....................................................................................................................ii

1 Overview.........................................................................................................................................1
1.1 Log Concept...................................................................................................................................................................1
1.2 Log Storage....................................................................................................................................................................1
2 Logs in the Files.............................................................................................................................2

2.1 Log Type.........................................................................................................................................................................2
2.2 Log File List...................................................................................................................................................................5
2.3 Log Level......................................................................................................................................................................29
2.4 Log Content Format.....................................................................................................................................................32
2.5 Log Backup..................................................................................................................................................................33
2.6 Locating a Fault Through Logs....................................................................................................................................34
3 Log in the Database.....................................................................................................................37

3.1 Introduction..................................................................................................................................................................38
3.2 CPS_AUDIT_TXN......................................................................................................................................................38
3.3 CPS_AUDIT_FINANCIAL.........................................................................................................................................40
3.4 CPS_AUDIT_IDENTITY............................................................................................................................................41
3.5 CPS_AUDIT_ACCOUNT...........................................................................................................................................43
3.6 CPS_AUDIT_CONF....................................................................................................................................................44
3.7 CPS_AUDIT_CARE....................................................................................................................................................46
3.8 CPS_AUDIT_TASK....................................................................................................................................................47
3.9 CPS_AUDIT_SECURITY...........................................................................................................................................49
3.10 CPS_AUDIT_QUERY...............................................................................................................................................50
Issue 01 (2017-07-28) Huawei Proprietary and Confidential v

Copyright © Huawei
Mobile Money
Log Reference 1 Overview
1 Overview
About This Chapter

1.1 Log Concept
This topic describes the concept and functions of logs.
1.2 Log Storage
This topic describes the storage method and usage of different logs in Mobile Money system.
1.1 Log Concept

This topic describes the concept and functions of logs.
Logs record the important information during the running of the system and are created and
recorded by automated processes.
Logs record the running status information of the system and exception information, which
are the main source of fault orientation for maintenance engineer and are also the basis of
fault information collected by user. Logs can also be used to track and trace fraudulent
transactions.
1.2 Log Storage

This topic describes the storage method and usage of different logs in Mobile Money system.
According to storage method, logs are divided into:
 Logs stored in files
Including run log, debug log, alarm log, Longsql Log, Tool Log and trace log. These
logs are mainly used to record the application process running status and exception
information.
 Logs stored in the database
Record audit logs for any transaction, activity, action and query in the system.
Issue 01 (2017-07-28) Huawei Proprietary and Confidential 1

Copyright © Huawei
Mobile Money
Log Reference 2 Logs in the Files
2 Logs in the Files
About This Chapter

2.1 Log Type
This topic describes the log types and application scenarios of logs stored in the files.
2.2 Log File List
This topic describes the name of the log file and storage path for all modules in Mobile
Money system.
2.3 Log Level
This topic describes the definition of logs level for all modules in Mobile Money system and
how to adjust the level of logs.
2.4 Log Content Format
This topic describes the format of log content for all modules of the Mobile Money system
and the definition of log fields.
2.5 Log Backup
Roll Over is a way for backing up logs files.
2.6 Locating a Fault Through Logs
2.1 Log Type

This topic describes the log types and application scenarios of logs stored in the files.
Debug Log
The debug log usually record the running path of trace programs, for example, the entry and
exit of logic (function) for trace business and error details. The application scenarios include:
 Development engineer (The developer of this product and of integrated product) locates
problem by debugging program in development process.

Copyright © Huawei
Mobile Money
 Technical supporting engineer locates complicated problem in the project execution or

running and maintenance process.
All logs information must be recorded in the debug log. When the log level is in the DEBUG,
the logs in debug level and non debug level must have records in the debug log: Mapping
WARN, INFO level to the normal message sub type of debug log and mapping ERROR
level to error sub type of debug log according to the format requirement of debug log. For the
division of log level, please see 2.3Log Level.
The main scenarios of printing debug logs in Mobile Money system including:
 The treatment of error in the system or failure process.
 The interface of invoking process or the entry and exit of function.
 The entry and exit of key process.
 The event message of sending or receiving external module.
 The highest-level invoker (top-level function) in the case of recursive invocation.
 The end of cycles.
To improve log readability, debug logs of each module must be configured in the following
formats:
 Log layering
Logs must be displayed by log level. It is recommended that logs be displayed at a
maximum of four levels.
 Logs at each level are configured with unique keywords for identifying logs at each
level. Keywords for logs at each level must be paired ones in the STEP: Enter XXX and
STEP: Exit XXX formats. In the formats, XXX indicates a process name, for example,
STEP: Enter [Begin][Function]SyncServiceExecutor.execute.105[Param]
(requestHeader:RequestHeader).
 Description about error codes is contained in debug logs, which enables operators to
quickly diagnose and rectify faults based on error code description.
Run Log
The run log record the running status of the system and some key information during
execution process of the business in Mobile Money system, the exception status and action
during the system running, the relative information occupied by the key event and system
resource during the system running. The application scenarios including:
 The maintenance engineers know the running status of the system and find the exception
of the equipment.
 Technical supporting engineers or maintenance engineers locate fault and look for the
relative exception information.
The main scenarios of printing run logs in Mobile Money system including:
 Establish persistent connection of the Mobile Money system with the peripheral system.
 Exception status and action during the running process of the system, for example,
database disconnection, persistent connection with disconnection, and failure heartbeat.
 The key events during the system running process, for example: the system start, close
and switch.
 The overloading and recovery message when the system handles business message.

Copyright © Huawei
Mobile Money
Trace Log
The Trace log records detailed information and exceptions for service running (similar to
debug log). This log is generated only when a trace task is configured using the logtool.sh
tool. Trace tasks can be configured for a sender phone number, a service code or an operator
login name.
Alarm Log
The alarm log records the information about alarm occurrence and clearing when an
exception occurs.
Longsql Log
The Longsql Log records the SQL statements whose execution duration is long in the Mobile
Money system. SQL statements whose execution duration is longer than 100 milliseconds are
recorded by default. In AG, SP Portal, and Org Portal NEs, you can configure the execution
duration in $HOME/tomcat/webapps/payment/WEB-INF/classes/conf/cps.das.xml. And
in other NEs, you can configure the execution duration in $HOME/classes/conf/cps.das.xml.
Tool Log
The Tool Log records logs of tool on NEs except for the MQ and Single Sign On (SSO). Such
as logtool.sh, start.sh, startservice.sh, status.sh, stop.sh, stopservice.sh and version.sh.
Access Log
Access logs record information about accesses from external systems to the Mobile Money
system, including IP addresses of external systems, IP addresses of accessed systems, access
time, and information about internal accesses in the Mobile Money system. The access
logging can be enabled or disabled in the log4j.xml file and is disabled by default.
The log level of access logs is INFO.
Statistics Log
Statistics logs record business processing information of each module. The main scenarios of
printing statistics logs include the following:
 Maintenance personnel of carriers understand the key business processing information of
each module.
 Maintenance personnel of the Mobile Money system compare data of the current period
or data of the previous and next periods to analyze problems based on service processing
status on a module
Run logs are recorded if a module processes key businesses, for example, the module collects
statistics on received messages and processes messages by channel.
State Log
Logs record inbound and outbound messages that are generated when exceptions occur in
some services to identify issues.

Copyright © Huawei
Mobile Money
Others
In the Mobile Money system, there are logs which contain non-service information, such as
information about interactions between applications and databases, the start and stop of
applications, bottom level interactions, and the operating status of bottom level platforms. For
the detailed log list, see 2.2Log File List.
2.2 Log File List

This topic describes the name of the log file and storage path for all modules in Mobile
Money system.
For the log list in Mobile Money system, see the following tables.
Table 1.1 Access Gateway (AG) log list

File Name Storage Path Description
ag_debug.lo The path is $HOME/log/debug for Records detailed information for the
g installation user of AG. AG service execution process and
exceptions that occur.
ag_service_b Records the process information and
us.log exceptions for service invocation
and connection establishment
between AG and Service
Registration (SR) as well as other
nodes.
ag_ebus_deb Records detailed execution
ug.log information and errors when
Enterprise Bus (eBus) processes the
WebService and Short Message Peer
to Peer (SMPP) messages.
bpm.log Records errors occurred during the
running of the BPM module and the
process of troubleshooting the
errors.
ag_exceptio Records exception stack information
n_stack.log when errors occur during the
running of the AG NE.
umc_debug.l Records UMC module information.
og
nc_debug.lo Records information for the NC
g module to process SMS messages.
For example, this log records the
process of formatting, sending, and
resending messages.

Copyright © Huawei
Mobile Money
ag_bizapp_c Records service container module

ontainer_deb information.
ug.log
ag_bpmsyste Records run logs of the BPM
m.log module.
ag_statis.log The path is $HOME/log/coldata Records performance statistics when
for installation user of AG. the system is running.
ag_perf.log Records the memory, database
connection pool and thread pool
statistics when the system is
running.
ag_lthread.lo Records the blocked long thread
g information when the system is
running.
ag_datasourc The path is Records all database information
e.log $HOME/log/monitor/datasource when AG is failed to connect
for installation user of AG. database.
ag_monitor.l The path is Records the execution information
og $HOME/log/monitor/run for of monitor daemon in AG.
installation user of AG.
ag_start_mo Records the starting process
nitor.log information of monitor daemon in
AG.
ag_tools.log Records the status of executing
tools.sh script in AG.
ag_tomcat.lo The path is Records tomcat information when
g $HOME/log/monitor/thread for AG network is abnormal.
installation user of AG.
ag_ps.log The path is Records process information about
$HOME/log/monitor/system for all users of the server where the AG
installation user of AG. is located.
ag_psjava.lo Records the time when the user
g process of the server where the AG
is located uses the CPU.
ag_netstat.lo Records network connection status.
g
ag_vmstat.lo Records the server status at an
g interval of three seconds, including
the Mobile Money usage, memory
usage, virtual memory exchange,
and I/O information.
ag_jstack.lo Records jstack information about the
g user process of the server where the

Copyright © Huawei
Mobile Money
AG is located.
ag_iostat.log Records the Mobile Money usage,
system I/O capability, and I/O
request delivery information at an
interval of three seconds.
ag_run.log The path is $HOME/log/run for Records key running information for
installation user of AG. the AG and exceptions that occur
when a timer is created or triggered.
ag- Records information about accesses
nodeID_acce from external systems or other NEs
ss.log in the Mobile Money system to the
AG.
ag_license_a Records request information
gent.log received by the license agent.
ag_async_m Records monitoring logs for
onitor.log asynchronous task mechanism.
bpmRuntime Records run logs of the BPM
.log module.
ag_trace.log The path is $HOME/log/trace for Records service tracing information
installation user of AG. when the AG traces a service by
NOTE initiating a trace task.
Records stored in this path are
generated by the log4j.xml file.
ag_server.lo The path is $HOME/log/server for Records startup information of the

g installation user of AG. AG.
ag_alarm.log The path is $HOME/log/alarm for Records information about alarm
installation user of AG. occurrence and clearing when an
exception occurs.
bcmlib.log The path is $HOME/log/bcm for Records the communication
installation user of AG. information between bcmlib and
bcmagent.
ag_bcm.log Records alarm registration
information (indicating that the
alarm registration is successful or
fails) about the AG NE.
ag_longtime The path is $HOME/log/lsql for Records the SQL statements whose
SQL.log installation user of AG. execution duration is long in the
AG. SQL statements whose
execution duration is longer than
100 milliseconds are recorded by
default.
ag_XXX.log The path $HOME/tools/log for Records the run information of
installation user of AG. different commands in the AG.

Copyright © Huawei
Mobile Money
NOTE
XXX: indicates the tool name on the
current AG.
Table 1.2 Service Registration (SR) log list

sr_debug.log The path is $HOME/log/debug for Records the process for registering
installation user of SR. Mobile Money system application
nodes in SR. The information is
used to locate application node
registration failures and other
exceptions.
sr_service_b Records the process information and
us.log exceptions for service invocation
between SR and other nodes.
sr_ebus_deb Records detailed execution
ug.log information and errors when
errors.
sr_bpmsyste Records run logs of the BPM
m.log module.
sr_exception Records exception stack information
_stack.log when errors occur during the
running of the SR NE.
sr_bizapp_c Records service container module
ug.log
sr_statis.log The path is $HOME/log/coldata Records performance statistics when
for installation user of SR. the system is running.
sr_perf.log Records the memory, database
running.
sr_lthread.lo Records the blocked long thread
g information when the system is
running.

Copyright © Huawei
Mobile Money
sr_datasourc The path is Records all database information

e.log $HOME/log/monitor/datasource when SR is failed to connect
for installation user of SR. database.
sr_monitor.l The path is Records the execution information
og $HOME/log/monitor/run for of monitor daemon in SR.
installation user of SR.
sr_start_mon Records the starting process
itor.log information of monitor daemon in
SR.
sr_tools.log Records the status of executing
tools.sh script in SR.
sr_tomcat.lo The path Records tomcat information when
g $HOME/log/monitor/thread for SR network is abnormal.
installation user of SR.
sr_run.log The path is $HOME/log/run for Records information about key
installation user of SR. events for application nodes, such as
connection to SR, disconnection
from SR, and other exceptions.
sr- Records information about accesses
SR.
sr_license_a Records request information
gent.log received by the license agent.
sr_async_mo Records monitoring logs for
nitor.log asynchronous task mechanism.
.log module.
sr_alarm.log The path is $HOME/log/alarm for Records information about alarm
installation user of SR. occurrence and clearing when an
exception occurs.
sr_trace.log The path is $HOME/log/trace for Records service tracing information
installation user of SR. when the SR traces a service by
initiating a trace task. These log files
are generated by the log4j.xml file.
sr_server.log The path is $HOME/log/server for Records startup information about
installation user of SR. the SR.
installation user of SR. information between bcmlib and
bcmagent.
sr_bcm.log Records alarm registration

Copyright © Huawei
Mobile Money
fails) about the SR NE.

sr_longtime The path is $HOME/log/lsql for Records the SQL statements whose
SQL.log installation user of SR. execution duration is long in the SR.
SQL statements whose execution
duration is longer than 100
milliseconds are recorded by
default.
sr_XXX.log The path is $HOME/tools/log for Records the run information of
installation user of SR. different commands in the SR.
NOTE
current SR.
Table 1.3 Bulk Task Scheduler (BTS) log list

bts_debug.lo The path is $HOME/log/debug for Records detailed information for the
g installation user of BTS. BTS service execution process and
bts_service_ Records the process information and
bus.log exceptions for service invocation
between BTS and SR as well as
other nodes.
bts_ebus_de Records detailed execution
bug.log information and errors when
errors.
bts_exceptio Records exception stack information
running of the BTS NE.
bts_bizapp_c Records service container module
ug.log
bts_bpmsyst Records run logs of the BPM
em.log module.
bts_statis.log The path $HOME/log/coldata for Records performance statistics when
installation user of BTS. the system is running.

Copyright © Huawei
Mobile Money
bts_perf.log Records the memory, database

running.
bts_lthread.l Records the blocked long thread
og information when the system is
running.
bts- The path is Records all database information
datasource.l $HOME/log/monitor/datasource when BTS is failed to connect
og for installation user of BTS. database.
bts_monitor. The path is Records the execution information
log $HOME/log/monitor/run for of monitor daemon in BTS.
installation user of BTS.
bts_start_mo Records the starting process
BTS.
bts_tools.log Records the status of executing
tools.sh script in BTS.
bts_tomcat.l The path is Records tomcat information when
og $HOME/log/monitor/thread for BTS network is abnormal.
installation user of BTS.
bts_run.log The path is $HOME/log/run for Records key running information for
installation user of BTS. the bulk task and system tasks and
exceptions that occur when a timer
is created or triggered.
bts- Records information about accesses
BTS.
bts_license_ Records request information
agent.log received by the license agent.
bts_async_m Records monitoring logs for
onitor.log asynchronous task mechanism.
.log module.
bts_trace.log The path is $HOME/log/trace for Records service tracing information
installation user of BTS. when the BTS traces a service by
bts_server.lo The path is $HOME/log/server for Records startup information about
g installation user of BTS. the BTS.
bts_alarm.lo The path is $HOME/log/alarm for Records information about alarm
g installation user of BTS. occurrence and clearing when an

Copyright © Huawei
Mobile Money
exception occurs.
installation user of BTS. information between bcmlib and
bcmagent.
bts_bcm.log Records alarm registration
fails) about the BTS NE.
bts_longtime The path is $HOME/log/lsql for Records the SQL statements whose
SQL.log installation user of BTS. execution duration is long in the
BTS. SQL statements whose
default.
bts_XXX.lo The path is $HOME/tools/log for Records record the run information
g installation user of BTS. of different commands in the BTS.
NOTE
current BTS.
Table 1.4 Backend Core Services (BCS) log list

bcs_debug.l The path is $HOME/log/debug for Records detailed information for the
og installation user of BCS. BCS service execution process and
bcs_service_ Records the process information and
between BCS and SR as well as
other nodes.
bcs_ebus_de Records detailed execution
errors.
bcs_bizapp_ Records service container module
container_de information.
bug.log

Copyright © Huawei
Mobile Money
business_flo Records the process for the BCS to

w.log process each service.
bcs_bpmsyst Records run logs of the BPM
em.log module.
bcs_exceptio Records exception stack information
running of the BCS NE.
bcs_statis.lo The path is $HOME/log/coldata Records performance statistics when
g for installation user of BCS. the system is running.
bcs_perf.log Records the memory, database
running.
bcs_lthread.l Records the blocked long thread
og information when the system is
running.
bcs_datasour The path is Records all database information
ce.log $HOME/log/monitor/datasource when BCS is failed to connect
for installation user of BCS. database.
bcs_monitor. The path is Records the execution information
log $HOME/log/monitor/run for of monitor daemon in BCS.
installation user of BCS.
bcs_start_m Records the starting process
onitor.log information of monitor daemon in
BCS.
bcs_tools.lo Records the status of executing
g tools.sh script in BCS.
bcs_tomcat.l The path is Records tomcat information when
og $HOME/log/monitor/thread for BCS network is abnormal.
installation user of BCS.
bcs_run.log The path is $HOME/log/run for Records information about key
installation user of BCS. events for application nodes, such as
connection to BCS, disconnection
from BCS, and other exceptions.
bcs- Records information about accesses
BCS.
bcs_license_ Records request information
agent.log received by the license agent.
bcs_async_ Records monitoring logs for
monitor.log asynchronous task mechanism.

Copyright © Huawei
Mobile Money
.log module.
bcs_trace.lo The path is $HOME/log/trace for Records service tracing information
g installation user of BCS. when the BCS traces a service by
bcs_server.l The path is $HOME/log/server for Records startup information about
og installation user of BCS. the BCS.
bcs_alarm.lo The path is $HOME/log/alarm for Records information about alarm
g installation user of BCS. occurrence and clearing when an
exception occurs.
installation user of BCS. information between bcmlib and
bcmagent.
bcs_bcm.log Records alarm registration
fails) about the BCS NE.
bcs_longtim The path is $HOME/log/lsql for Records the SQL statements whose
eSQL.log installation user of BCS. execution duration is long in the
BCS. SQL statements whose
default.
bcs_XXX.lo The path is $HOME/tools/log for Records the run information of
g installation user of BCS. different commands in the BCS.
NOTE
current BCS.
Table 1.5 SP Web Application (SWA) log list

swa_debug.l The path is $HOME/log/debug for Records detailed information for the
og installation user of SWA. service execution process and
swa_service Records the process information and
_bus.log exceptions for service invocation
between portal and SR as well as
other nodes.
swa_console Records logs not recorded in the
.log category.
swa_ebus_d Records detailed execution

Copyright © Huawei
Mobile Money
ebug.log information and errors when

swa_excepti Records exception stack information
on_stack.log when errors occur during the
running of the SWA NE.
swa_statis.lo The path is $HOME/log/coldata Records performance statistics when
g for installation user of SWA. the system is running.
swa_lthread. Records the blocked long thread
log information when the system is
running.
swa_datasou The path is Records all database information
rce.log $HOME/log/monitor/datasource when SWA is failed to connect
for installation user of SWA. database.
swa_monitor The path is Records the execution information
.log $HOME/log/monitor/run for of monitor daemon in SWA.
installation user of SWA.
swa_start_m Records the starting process
SWA.
swa_stop_m Records the ending process
SWA.
swa_tools.lo Records the status of executing
g tools.sh script in SWA.
swa_tomcat. The path is Records tomcat information when
log $HOME/log/monitor/thread for SWA network is abnormal.
swa_netstat.l The path is Records network connection status.
og $HOME/log/monitor/system for
swa_ps.log Records process information about
all users of the server where the
SWA is located.
swa_vmstat.l Records the server status at an
og interval of three seconds, including
swa_iostat.lo Records the Mobile Money usage,
g system I/O capability, and I/O
request delivery information at an
swa_jstack.l Records jstack information about the

Copyright © Huawei
Mobile Money
og user process of the server where the

SWA is located.
swa_psjava.l Records the time when the user
og process of the server where the
SWA is located uses the CPU.
swa_run.log The path is $HOME/log/run for Records information about key
installation user of SWA. events for application nodes, such as
connection to portal, disconnection
from SWA, and other exceptions.
swa- Records information about accesses
SWA.
swa_async_ Records monitoring logs for
swa_license Records request information
_agent.log received by the license agent.
swa_ssoclien Records the portal login status. If no
t.log operation is performed on the portal
for a long time or the portal login
fails the verification, related
information is recorded in this log
file.
swa_trace.lo The path is $HOME/log/trace for Records service tracing information
g installation user of SWA. when the portal traces a service by
swa_server.l The path is $HOME/log/server for Records startup information about

og installation user of SWA. the SWA.
swa_alarm.l The path is $HOME/log/alarm for Records information about alarm
og installation user of SWA. occurrence and clearing when an
exception occurs.
installation user of SWA. information between bcmlib and
bcmagent.
swa_longtim The path is $HOME/log/lsql for Records the SQL statements whose
eSQL.log installation user of SWA. execution duration is long in the
SWA. SQL statements whose
default.
swa_XXX.lo The path is $HOME/tools/log for Records the run information of
g installation user of SWA. different commands in the SWA.

Copyright © Huawei
Mobile Money
NOTE
current portal.
Table 1.6 Organization Web Application (OWA) log list

owa_debug.l The path is $HOME/log/debug for Records detailed information for the
og installation user of OWA. service execution process and
owa_service Records the process information and
_bus.log exceptions for service invocation
between portal and SR as well as
other nodes.
owa_console Records logs not recorded in the
.log category.
owa_ebus_d Records detailed execution
ebug.log information and errors when
owa_excepti Records exception stack information
on_stack.log when errors occur during the
running of the OWA NE.
owa_statis.lo The path is $HOME/log/coldata Records performance statistics when
g for installation user of OWA. the system is running.
owa_lthread. Records the blocked long thread
log information when the system is
running.
owa_datasou The path is Records all database information
rce.log $HOME/log/monitor/datasource when OWA is failed to connect
for installation user of OWA. database.
owa_monito The path is Records the execution information
r.log $HOME/log/monitor/run for of monitor daemon in OWA.
installation user of OWA.
owa_start_m Records the starting process
OWA.
owa_tools.lo Records the status of executing
g tools.sh script in OWA.
owa_tomcat. The path is Records tomcat information when
log $HOME/log/monitor/thread for OWA network is abnormal.

Copyright © Huawei
Mobile Money
installation user of OWA.

owa_run.log The path is $HOME/log/run for Records information about key
installation user of OWA. events for application nodes, such as
connection to portal, disconnection
from OWA, and other exceptions.
owa- Records information about accesses
OWA.
owa_async_ Records monitoring logs for
owa_license Records request information
_agent.log received by the license agent.
owa_ssoclie Records the portal login status. If no
nt.log operation is performed on the portal
for a long time or the portal login
fails the verification, related
information is recorded in this log
file.
owa_trace.lo The path is $HOME/log/trace for Records service tracing information
g installation user of OWA. when the portal traces a service by
owa_server.l The path is $HOME/log/server for Record startup information about the
og installation user of OWA. OWA.
owa_alarm.l The path is $HOME/log/alarm for Records information about alarm
og installation user of OWA. occurrence and clearing when an
exception occurs.
installation user of OWA. information between bcmlib and
bcmagent.
owa_longtim The path is $HOME/log/lsql for Records the SQL statements whose
eSQL.log installation user of OWA. execution duration is long in the
OWA. SQL statements whose
default.
owa_iostat.l The path is Records the Mobile Money usage,
og $HOME/log/monitor/system for system I/O capability, and I/O
installation user of OWA. request delivery information at an
owa_psjava.l Records the time when the user
og process of the server where the

Copyright © Huawei
Mobile Money
OWA is located uses the CPU.

owa_jstack.l Records jstack information about the
og user process of the server where the
OWA is located.
owa_ps.log Records process information about
all users of the server where the
OWA is located.
owa_netstat. Records network connection status.
log
owa_vmstat. Records the server status at an
log interval of three seconds, including
owa_XXX.l The path is $HOME/tools/log for Records the run information of
og installation user of OWA. different commands in the OWA.
NOTE
current portal.
Table 1.7 Data Integration Platform (DIP) log list

dip_debug.lo The path is $HOME/log/debug for Records detailed information for the
g installation user of DIP. DIP service execution process and
dip_service_ Records the process information and
between DIP and SR as well as
other nodes.
dip_console. Records logs not recorded in the
log category.
dip_ebus_de Records detailed execution
dip_statis.lo The path is $HOME/log/coldata Records performance statistics when
g for installation user of DIP. the system is running.
dip_datasour The path is Records all database information
ce.log $HOME/log/monitor/datasource when DIP is failed to connect

Copyright © Huawei
Mobile Money
for installation user of DIP. database.

dip_monitor. The path is Records the execution information
log $HOME/log/monitor/run for of monitor daemon in DIP.
installation user of DIP.
dip_start_mo Records the starting process
DIP.
dip_tools.log Records the status of executing
tools.sh script in DIP
dip_tomcat.l The path is Records tomcat information when
og $HOME/log/monitor/thread for DIP network is abnormal.
installation user of DIP.
dip_run.log The path is $HOME/log/run for Records information about key
installation user of DIP. events for application nodes, such as
connection to DIP, disconnection
from DIP, and other exceptions.
dip_async_ Records monitoring logs for
dip_trace.log The path is $HOME/log/trace for Records service tracing information
installation user of DIP. when the DIP traces a service by
dip_server.lo The path is $HOME/log/server for Records startup information about
g installation user of DIP. the DIP.
dip_alarm.lo The path is $HOME/log/alarm for Records information about alarm
g installation user of DIP. occurrence and clearing when an
exception occurs.
dip_longtim The path is $HOME/log/lsql for Records the SQL statements whose
eSQL.log installation user of DIP. execution duration is long in the
DIP. SQL statements whose
default.
dip_XXX.lo The path is $HOME/tools/log for Records the run information of
g installation user of DIP. different commands in the DIP.
NOTE
current DIP.
Table 1.8 Message Queue (MQ) log list

bme.log The path is $HOME/logs/debug Records detailed information and

Copyright © Huawei
Mobile Money
for installation user of MQ. exceptions for Business

Management Engine (BME)
container startup and execution.
javaoamlib_ Records the information about
oamlib.log. interconnect network management.
XXX
NOTE
XXX:
indicates the
roll number.
spring.log Records detailed information about

spring osgi deployment and bundle
startup.
Performance The path is $HOME/logs/coldata Records performance statistics when
.prf for installation user of MQ. the system is running.
interface.log The path is $HOME/logs/interface Records the interface information
for installation user of MQ. about BME component.
cps_start_m The path is Records the starting process
onitor.log $HOME/log/monitor/run for information of monitor daemon in
installation user of MQ. MQ.
operation.lo The path is Records the operation information
g $HOME/logs/operation for about BME component.
installation user of MQ.
runtime.log The path is $HOME/logs/run for Records information about key
installation user of MQ. events for application nodes, such as
connection to MQ, disconnection
from MQ, and other exceptions.
security.log The path is $HOME/logs/security Records the security information
for installation user of MQ. about BME component.
state.log The path is $HOME/logs/state for Records the state information about
installation user of MQ. BME component.
user.log The path is $HOME/logs/user for Records the user information about
installation user of MQ. BME component.
jetmq_call.lo The path is $HOME/logs/call for Records the MQ trace calls
g installation user of MQ. information.
jetmq.log The path is $HOME/logs/jetmq for Records the operation information of
installation user of MQ. jet server.
monitor.log Records the execution information
of monitor daemon in MQ.
jetmqsystem Records information about the
.log memory occupied when the MQ is
running.

Copyright © Huawei
Mobile Money
jetmqretrym Records information about MQ

sg.log message resending.
jetmqstartup. Records system parameters for
log starting the MQ.
jetmq_jmx.l The path is $HOME/logs/jmx for Records information about jmx
og installation user of MQ. connection of the MQ.
amqp.log The path is $HOME/logs/restart Records the run state of MQ server.
for installation user of MQ. When the MQ server is shut down,
the log is recorded.
logtrace.log The path is $HOME/logs/trace for Records service tracing information
installation user of MQ. when the MQ traces a service by
initiating a trace task.
Table 1.9 Remote Cache Service (RCS) log list

rcs_start_mo The path is Records the starting process

nitor.log $HOME/log/monitor/run for information of monitor daemon in
installation user of RCS. RCS.
redis_start.lo The path is $HOME/tools/log for Records information about rcs
g installation user of RCS. startup.
redis_status.l Records execution result of
og initialization parameters in the
process for the rcs to check the
status.
redis_redisk Records information about rcs
ey.log startup.
redis_getmo Records information about rcs query
dulestatus.lo status.
g
redis_chang Records the list of files whose
emod.log permission is modified in the rcs
directory.
redis_startse Records information about rcs
rvice.log startup.
redis.log The path is $HOME/log for Records RCS server abnormal
installation user of RCS. information.

Copyright © Huawei
Mobile Money
Table 1.10 Single Sign-On (SSO) log list

sso_start_m The path is Records the starting process

installation user of SSO. SSO.
sso_XXX.lo The path is $HOME/tools/log for Records the run information of
g installation user of SSO. different commands in the SSO.
NOTE
current SSO.
Table 1.11 Oracle GoldenGate (OGG) log list

checkoggpro The path is Records the execution result of the

cess.log $OGG_HOME/ogg/tools/log for checkoggprocess.sh script.
installation user of OGG. Information is recorded
incrementally.
checkoggpro Records only the current execution
cess_current. result of the checkoggprocess.sh
log script. The log information is used
by a BCM Agent preprocessing
script to obtain the status of the
OGG process.
checkogglag Records the execution result of the
.log checkogglag.sh script. Information
is recorded incrementally.
checkogglag Records only the current execution
_current.log result of the checkogglag.sh script.
The log information is used by a
BCM Agent preprocessing script to
obtain the latency information the
OGG process.
EX***.rpt The path is $OGG_HOME/dirrpt Records logs of the OGG extraction
for installation user of OGG. process.
DP***.rpt Records logs of the OGG transfer
process.
MGR***.rpt Records logs of the OGG
management process.
RP***.rpt Records logs of the OGG delivery
process.

Copyright © Huawei
Mobile Money
Table 1.12 Repository Portal (Rep Portal) log list

repportal_de The path is $HOME/log/debug for Records detailed information for the
bug.log installation user of Rep Portal. Rep Portal service execution process
and exceptions that occur.
repportal_ser Records the process information and
vice_bus.log exceptions for service invocation
between Rep Portal and SR as well
as other nodes.
repportal_co Records logs not recorded in the
nsole.log category.
repportal_eb Records detailed execution
us_debug.lo information and errors when
g Enterprise Bus (eBus) processes the
repportal_sta The path is $HOME/log/coldata Records performance statistics when
tis.log for installation user of Rep Portal. the system is running.
repportal_pe Records the memory, database
rf.log connection pool and thread pool
running.
repportal_lth Records the blocked long thread
read.log information when the system is
running.
repportal_da The path is Records all database information
tasource.log $HOME/log/monitor/datasource when Rep Portal is failed to connect
for installation user of Rep Portal. database.
repportal_m The path is Records the execution information
onitor.log $HOME/log/monitor/run for of monitor daemon in Rep Portal.
installation user of Rep Portal.
repportal_sta Records the starting process
rt_monitor.l information of monitor daemon in
og Rep Portal.
repportal_sto Records the ending process
p_monitor.lo information of monitor daemon in
g Rep Portal.
repportal_to Records the status of executing
ols.log tools.sh script in Rep Portal
repportal_to The path is Records tomcat information when
mcat.log $HOME/log/monitor/thread for PGM network is abnormal.
installation user of Rep Portal.

Copyright © Huawei
Mobile Money
repportal_ru The path is $HOME/log/run for Records information about key

n.log installation user of Rep Portal. events for application nodes, such as
connection to Rep Portal,
disconnection from Rep Portal, and
other exceptions.
repportal- Records information about accesses
Rep Portal.
repportal_as Records monitoring logs for
ync_monitor asynchronous task mechanism.
.log
repportal_lic Records request information
ense_agent.l received by the license agent.
og
repportal_tra The path is $HOME/log/trace for Records service tracing information
ce.log installation user of Rep Portal. when the Rep Portal traces a service
by initiating a trace task. These log
files are generated by the log4j.xml
file.
repportal_ser The path is $HOME/log/server for Records startup information about
ver.log installation user of Rep Portal. the Rep Portal.
repportal_ala The path is $HOME/log/alarm for Records information about alarm
rm.log installation user of Rep Portal. occurrence and clearing when an
exception occurs.
installation user of Rep Portal. information between bcmlib and
bcmagent.
repportal_lo The path is $HOME/log/lsql for Records the SQL statements whose
ngtimeSQL.l installation user of Rep Portal. execution duration is long in the Rep
og Portal. SQL statements whose
default.
repportal_X The path is $HOME/tools/log for Records the run information of
XX.log installation user of Rep Portal. different commands in the Rep
NOTE Portal.
current Rep Portal.

Copyright © Huawei
Mobile Money
Table 1.13 Configuration Portal (Conf Portal) log list

confportal_d The path is $HOME/log/debug for Records detailed information for the
ebug.log installation user of Conf Portal. Conf Portal service execution
process and exceptions that occur.
confportal_s Records the process information and
ervice_bus.l exceptions for service invocation
og and connection establishment
between Conf Portal and SR as well
as other nodes.
confportal_c Records logs not recorded in the
onsole.log category.
confportal_e Records detailed execution
bus_debug.l information and errors when
og Enterprise Bus (eBus) processes the
confportal_st The path is $HOME/log/coldata Records performance statistics when
atis.log for installation user of Conf Portal. the system is running.
confportal_p Records the memory, database
erf.log connection pool and thread pool
running.
confportal_lt Records the blocked long thread
hread.log information when the system is
running.
confportal_d The path is Records all database information
atasource.lo $HOME/log/monitor/datasource when Conf Portal is failed to
g for installation user of Conf Portal. connect database.
confportal_ The path is Records the execution information
monitor.log $HOME/log/monitor/run for of monitor daemon in Conf Portal.
installation user of Conf Portal.
confportal_st Records the starting process
art_monitor.l information of monitor daemon in
og Conf Portal.
confportal_st Records the ending process
op_monitor.l information of monitor daemon in
og Conf Portal.
confportal_t Records the status of executing
ools.log tools.sh script in Conf Portal
confportal_t The path is Records tomcat information when
omcat.log $HOME/log/monitor/thread for Conf Portal network is abnormal.
installation user of Conf Portal.
confportal_r The path is $HOME/log/run for Records information about key
un.log installation user of Conf Portal. events for application nodes, such as

Copyright © Huawei
Mobile Money
connection to Conf Portal,

disconnection from Conf Portal, and
other exceptions.
confportal- Records information about accesses
Conf Portal.
confportal_a Records monitoring logs for
sync_monito asynchronous task mechanism.
r.log
confportal_li Records request information
cense_agent. received by the license agent.
log
confportal_tr The path is $HOME/log/trace for Records service tracing information
ace.log installation user of Conf Portal. when the Conf Portal traces a
service by initiating a trace task.
These log files are generated by the
log4j.xml file.
confportal_s The path is $HOME/log/server for Records startup information about
erver.log installation user of Conf Portal. the Conf Portal.
confportal_a The path is $HOME/log/alarm for Records information about alarm
larm.log installation user of Conf Portal. occurrence and clearing when an
exception occurs.
installation user of Conf Portal. information between bcmlib and
bcmagent.
confportal_l The path is $HOME/log/lsql for Records the SQL statements whose
ongtimeSQL installation user of Conf Portal. execution duration is long in the
.log Conf Portal. SQL statements whose
default.
confportal_ The path is $HOME/tools/log for Records the run information of
XXX.log installation user of Conf Portal. different commands in the Conf
NOTE Portal.
current Conf Portal.
Table 1.14 Archiving Application Services (AAS) log list

aas_debug.lo The path is $HOME/log/debug for Records detailed information for the
g installation user of AAS. AAS service execution process and

Copyright © Huawei
Mobile Money

aas_service_ Records the process information and
between AAS and SR as well as
other nodes.
aas_console. Records logs not recorded in the
log category.
aas_ebus_de Records detailed execution
aas_statis.lo The path is $HOME/log/coldata Records performance statistics when
g for installation user of AAS. the system is running.
aas_perf.log Records the memory, database
running.
aas_alarm.lo The path is $HOME/log/alarm for Records information about alarm
g installation user of AAS. occurrence and clearing when an
exception occurs.
aas_run.log The path is $HOME/log/run for Records information about key
installation user of AAS. events such as sending notifications.
aas- Records information about accesses
AAS.
aas_trace.log The path is $HOME/log/trace for Records service tracing information
installation user of AAS. when the AAS traces a service by
aas_server.lo The path is $HOME/log/server for Records startup information about
g installation user of AAS. the AAS.
installation user of AAS. information between bcmlib and
bcmagent.
aas_longtim The path is $HOME/log/lsql for Records the SQL statements whose
eSQL.log installation user of AAS. execution duration is long in the
AAS. SQL statements whose
default.

Copyright © Huawei
Mobile Money
gds_stop_m The path is Records the ending process

installation user of AAS. AAS.
gds_start_m Records the starting process
AAS.
aas_XXX.lo The path is $HOME/tools/log for Records the run information of
g installation user of AAS. different commands in the AAS.
NOTE
current AAS.
2.3 Log Level

This topic describes the definition of logs level for all modules in Mobile Money system and
how to adjust the level of logs.
For the definition of logs levels in Mobile Money system, please see Table 1.15. The run log
only has three levels: INFO, WARN and ERROR.
Table 1.15 Log Level

Log Level Definition
OFF This level indicates that the system does not record logs. Choose this
option when print logs are not required.
DEBUG The debug message of the system.
INFO The normal running message of the system.
WARN System alarms. When the system status are different with the predicted
status, which does not affect the run of the whole system. For example, a
subscriber manually suspends a service.
ERROR General errors. The logs in this level record the following error:
 Non predicted data or event.
 The errors have a huge influence and can be handled in the module.
 The errors limited in the module.
 The errors have a small influence on other modules. For example, fail to
create statistic task.
 The errors lead to fail to invoke
 Under the situation of fault service logic, record the information of fault
status and the possible reason of error.

Copyright © Huawei
Mobile Money
According to the severity of problem, the log level is divided into four levels, Debug, Info, Warn, and
Error from lowness to highness, and the log in low level contains the log content in high level. For
example: when the log is in Debug level, the contents of log file contain the logs in Debug, Info, Warn
and Error level.
The run log is generally in the INFO status. Owing to the size of the messages which would
occupy a great deal of resource, the debug log is generally in the OFF or ERROR mode. But
logs in the DEBUG level must be exported to locate problems in the debug process of the
system.
After open the debug log, it affects the performance of the system, slows down the run of
business, and occupies the disk space, so not allow to open the log in the commercial usage. If
requires to locate problem, you cannot open the debug log until get the approval of the
maintenance supervisor and close the switch of debug log after once finish.
Adjust the Level of Logs Using a Tool

The methods of adjusting logs level in all modules are the same. Below is an example of
adjusting the debug log bts_debug.log to the DEBUG level in the BTS module to show how
this is configured:
1. Log in to BTS module as the installation subscriber of BTS.
2. Enter the tools directory.
cd $HOME/tools
3. Run the log tool.
./logtool.sh. The system displays the following information:
====================================
eTrace: Main
====================================
[1] Add a new trace task
[2] Delete exist trace task
[3] List all trace task
[4] Query log level
[5] Change log level
[6] Gather log files
[0] Exit
Please select option:
4. Enter 5.
The system displays the following information:
5
[1] DEBUG level
[2] INFO level
[3] WARN level
[4] ERROR level
[5] FATAL level
[6] OFF level

Copyright © Huawei
Mobile Money
[7] RESUME level

[0] Back to main menu
DEBUG level will cost much. Please use it when system is idle, and set to
RESUME level in time.
Please select the target log level option:
5. Enter 1.
The system displays the following information:
0|The debug log's level is set to DEBUG successfully.
The log level is successfully set to Debug.
Adjust the Level of Logs in the Configuration File

In Mobile Money system, logs exported in all modules are defined in the file log4j.xml. This
file is stored in the $HOME/config/local directory in each module.
The methods of adjusting logs level in all modules are the same. Below is an example of
adjusting the debug log bts_debug.log to the DEBUG level in the BTS module to show how
this is configured:
1. Log in to BTS module as the installation subscriber of BTS.
2. Open the file log4j.xml in edit mode.
vi $HOME/config/local/log4j.xml
3. Find the configuration item relative with bts_debug.log.
appender name="DEBUG_LOG"
class="com.huawei.payment.common.log.CPSRollingFileAppender">
<param name="File" value="${home}/log/debug/$
{node_type}_debug.log" />
<param name="CheckInterval" value="30000" />
<param name="MaxFileSize" value="10MB" />
<param name="MaxBackupIndex" value="10" />
<layout class="com.huawei.bme.commons.log4j.BMEPatternLayout">
<param name="ConversionPattern"
value="%t|%d{yyyy-MM-dd HH:mm:ss,SSS}|
%X{level}|%X{moduleName}|%X{traceID}|%m|%X{appendInfo} %n" />
</layout>
</appender>
4. Search key words DEBUG_LOG as the value of parameter appender-ref and find the
following similar configuration item:
<category name="CPS" additivity="false">
<priority value="ERROR" />
<appender-ref ref="DEBUG_LOG" />
</category>
The value of parameter priority indicates the log level.

5. Modify the value of parameter priority to DEBUG, save and exit.
6. Restart BTS module.
a. Enter $HOME/tools.
b. Run restart.sh.
The log level is successfully set to Debug.

Copyright © Huawei
Mobile Money
2.4 Log Content Format

This topic describes the format of log content for all modules of the Mobile Money system
and the definition of log fields.
Table 1.1 describes the log exporting parameters supported by Mobile Money system. For all
the logs in all modules one can select exporting parameters according to the requirement.
Table 1.1 Log Exporting Parameter

Paramete Description Case
r
%d The time of exporting log. 2013-07-15 14:34:17,433 +0800

The format as following:
YYYY-MM-dd HH:mm:ss.SSS Z
%X{level Log levels: DEBUG
}  DEBUG
 INFO
 WARN
 ERROR
For details of log level, please
see2.3Log Level.
%X{mod The module name of generated log. UCC
uleName}
%X{trace Used to trace log ID of once 1356050734908
ID} conversation. When there are many
conversations, you can find log
information of same conversation
according to this ID.
%t The name of thread generating this Trinity-Request-Handler-8
log event.
%X{appe Append information, generally used Not used.
ndInfo} to export the value of parameter.
%m The information specified in the [Enter Function]|
process and is generally used to Param1=TransactionType
export the interface function, or the [content=Content [id=2000000012,],
entry and exit information, parameter, uniqueId=null, isBulk=null,
execution result of function invoking. isIntra=null, isReversal=null,
canbeReversed=null,
status=RELEASED, lastOperId=null,
lastOperTime=null,
createOperId=null,
createOperTime=null,
transParties=null],Param2={null},Par
am3={null}|
TransactionTypeDaoImpl.query.161
%X{exce Exception message. Not used

Copyright © Huawei
Mobile Money
Paramete Description Case

r
ptionMess
age}
%X{fullI The code place of generating log com.huawei.payment.bc.request.facad
nfo} event, including category name and e.impl.BulkTaskPlanQuerierImpl.que
the number of lines in the code. ryBulkPlanList(BulkTaskPlanQuerier
Impl.java:99)
%n Means a newline. -
The content format of log is defined in the log4j.xml file of all modules. Below takes the
example of debug log bts_debug.log in the BTS module to describe how to check the content
format of log.
1. Log in to BTS module as BTS installation user.
2. Open the file log4j.xml in checking mode.
vi $HOME/config/local/log4j.xml
3. Find the configuration items relative with bts_debug.log.
appender name="DEBUG_LOG"
class="com.huawei.payment.common.log.CPSRollingFileAppender">
<param name="File" value="${home}/log/debug/$
{node_type}_debug.log" />
<param name="CheckInterval" value="30000" />
<param name="MaxFileSize" value="10MB" />
<param name="MaxBackupIndex" value="10" />
<layout class="com.huawei.bme.commons.log4j.BMEPatternLayout">
<param name="ConversionPattern"
value="%t|%d{yyyy-MM-dd HH:mm:ss,SSS}|
%X{level}|%X{moduleName}|%X{traceID}|%m|%X{appendInfo} %n" />
</layout>
</appender>
The bold parts define the content format of bts_debug.log log. For the definition of
exporting parameter for common logs, please see Table 1.1.
2.5 Log Backup

Roll Over is a way for backing up logs files.
In Mobile Money system, logs Rolling in all modules are defined in the file log4j.xml.
The Mobile Money system supports two rolling policies:
 Rolling based on file creation time
In this policy, the system periodically backs up log files.
In the current system, rolling at full hour is used to back up run logs, alarm logs and
longsql logs. The rolling interval is configurable, and set to 2 hours by default. For
example, if an xxx.log file is generated on 12:00 20131221, the system backs up the file

Copyright © Huawei
Mobile Money
as xxx_20131221140000.log at 14:00 the same day, and deletes the backup file generated
three days ago.
 Rolling by file size
In this policy, the system automatically backs up a log file after the file size exceeds a
certain value.
In the current system, rolling by file size is used to back up trace logs, tool logs and
debug logs. By default, the system backs up a log file when the file size reaches 10 MB.
For example, when the size of xxx.log reaches a configured value, the system backs up
the file as xxx_20131212103111.log. If the number of backup files for xxx.log exceeds
the default value 10, the system automatically deletes the earliest backup file.
The maximum size of an access log file is 20 MB. If the number of files for xxx.log exceeds the default
value 10, the system automatically deletes the earliest log file.
2.6 Locating a Fault Through Logs

General procedure for Locating a Fault
Figure 1.1 shows the general procedure for locating a fault.

Copyright © Huawei
Mobile Money
Figure 1.1 Procedure for locating a fault
Procedure for Locating a Fault Through the Debug logs

Figure 1.1 shows the procedure for locating a fault through the debug logs.

Copyright © Huawei
Mobile Money
Figure 1.1 Procedure for locating a fault through the debug logs
1. Receive a task for locating the problem.

2. Analyze the problem.
3. Evaluate the problem cause according to cases and experience.
4. Perform the service operation again to obtain the debug logs.
5. Search for the logs information of the error level.
6. Analyze the information and troubleshoot the problem according to the error logs.
If you find the error code in the logs, refer to Mobile Money Error Codes to locate and
solve the problem according to the error code.
7. Check whether the problem is solved.
− If the problem is solved, the operation is complete.
− If not, go to 8.
8. Submit the problem to Huawei engineers.

Copyright © Huawei
Mobile Money
Log Reference 3 Log in the Database
3 Log in the Database
About This Chapter

3.1 Introduction
The Mobile Money system records audit log for all transaction, activity, action and query
happened in the system and saves audit log in the database. You can query in the GUI
provided by Portal.
3.2 CPS_AUDIT_TXN
Audit log for transaction.
3.3 CPS_AUDIT_FINANCIAL
Audit log for financial reconciliation.
3.4 CPS_AUDIT_IDENTITY
Audit log for identity management.
3.5 CPS_AUDIT_ACCOUNT
Audit log for account management.
3.6 CPS_AUDIT_CONF
Audit log for configuration management.
3.7 CPS_AUDIT_CARE
Audit log for customer care.
3.8 CPS_AUDIT_TASK
Audit log for task.
3.9 CPS_AUDIT_SECURITY
Audit log for security.
3.10 CPS_AUDIT_QUERY
Audit log for query.

Copyright © Huawei
Mobile Money
3.1 Introduction
The Mobile Money system records audit log for all transaction, activity, action and query
happened in the system and saves audit log in the database. You can query in the GUI
provided by Portal.
The SP operator can log in to the SP Portal and enter menu My Functions > Reporting >
Audit log to query the audit log in the system. The query period can be configured in the My
Functions > Operational Configuration > System Parameter > Generic > Default Days
for Querying Audit Log menu. The default query period is 31 days.
According to recording contents and scenarios, the audit Log is divided into different types.
The audit logs in each type are recorded in the different tables as indicated in the Table 1.1.
Table 1.1 Audit Log

Category Table Name
Transaction CPS_AUDIT_TXN
Financial CPS_AUDIT_FINANCIAL
Identity Management CPS_AUDIT_IDENTITY
Account Management CPS_AUDIT_ACCOUNT
Configuration CPS_AUDIT_CONF
Management
Customer Care CPS_AUDIT_CARE
Task CPS_AUDIT_TASK
Security CPS_AUDIT_SECURITY
Query CPS_AUDIT_QUERY
3.2 CPS_AUDIT_TXN
Audit log for transaction.
Log Description
Audit logs in this category will record:
 The initiating and changes of the transactions.
 The detailed information of the transaction. For example:
− From and to identities
− From and to accounts
− Before and after balances of each account
− Transaction pricing
− Error code

Copyright © Huawei
Mobile Money
− Error message
− Original transaction (for reversal transaction)
Format
Table 1.1 describes the format of the log.
Table 1.1 cps_audit_txn

Nu Field Name Field Type Description Can
mb Be
er NULL
1 AUDIT_LOG_ID NUMBER(18) Identifier No

2 INITIATOR_TYPE VARCHAR2(64) The type of initiator: No
 SP Operator
 Organization Operator
 Customer
3 IDENTITY_ID NUMBER(18) The identity ID of initiator Yes
4 SP_ORG_ID NUMBER(18) The ID of the organization Yes
or SP to which an initiator
belongs
5 LOG_TIME TIMESTAMP(6) The recording time of log No
6 EVENT_TYPE VARCHAR2(128) The event type No
7 TRANSACTION_ID VARCHAR2(22) The transaction ID No
8 REASON VARCHAR2(512) Event cause Yes
9 TXN_TYPE NUMBER(10) ID of a transaction type No
10 TXN_REASON_TYP NUMBER(10) Reason type ID of a No
E transaction
11 BEFORE_IMAGE VARCHAR2(400 The data before changing Yes
0)
12 AFTER_IMAGE VARCHAR2(400 The data after changing Yes
0)
13 ACCESS_CHANNEL VARCHAR2(5) Access channel Yes
_CODE
14 INITIATING_DEVIC VARCHAR2(2) The device type of an Yes
E_TYPE initiator
15 INITIATING_DEVIC VARCHAR2(32) The device identifier of an Yes
E_VALUE initiator
16 ERROR_MSG VARCHAR2(512) The reason of rejecting Yes
transaction
17 CARE_AUDIT_LOG NUMBER(18) Record the Audit Log ID Yes

Copyright © Huawei
Mobile Money

mb Be
er NULL
_ID of the same Take a Call

event.
3.3 CPS_AUDIT_FINANCIAL
Audit log for financial reconciliation.
Log Description
Audit logs in this category will record financial reconciliation actions. For example:
 Automatically import bank statement
 Manually import bank statement
 Process bank statement entries
 Approve bank reconciliation
 Sign off bank reconciliation
Format
Table 1.1 cps_audit_financial

mb Be
er NULL

 Outside System
 Mobile Money System
 SP Operator
 Customer
3 IDENTITY_ID NUMBER(18) The identity ID of Yes
initiator
4 SP_ORG_ID NUMBER(18) The ID of the Yes
organization or SP to
which an initiator belongs

Copyright © Huawei
Mobile Money

mb Be
er NULL
6 EVENT_TYPE VARCHAR2(12 The event type No

8)
7 START_TIME TIMESTAMP(6) The starting time No
8 END_TIME TIMESTAMP(6) The ending time No
9 REASON VARCHAR2(51 The event reason Yes
2)
10 BANK_REC_ID NUMBER(18) The reconciliation Yes
recording table ID of
bank
11 TASK_ID VARCHAR2(22) The task ID Yes
3.4 CPS_AUDIT_IDENTITY
Audit log for identity management.
Log Description
Audit logs in this category will record the creation and modification of identity, and some
operations performed on the identity such as change PIN, change MSISDN.
Format
Table 1.1 cps_audit_identity

mb Be
er NULL

 1000: Customer
 2000: SP Operator
 3000: Organization
Operator
 6000: Till
 8000: SP

Copyright © Huawei
Mobile Money

mb Be
er NULL

belongs
9 REASON VARCHAR2(512) The event reason Yes
10 ON_IDEN_TYPE VARCHAR2(128) The type of operated Yes
identity:
 1000: Customer
Operator
 6000: Till
 8000: SP
11 ON_IDENT_ID NUMBER(18) The ID of operated Yes
identity
0)
0)
14 ACTION_LOG_ID VARCHAR2(36) ACTION_LOG_ID in the Yes
CPS_ACTION_OPER_L
OG table for the current
service action
event.
E_TYPE initiator
E_VALUE initiator
18 ERROR_CODE VARCHAR2(32) The error code. Yes

Copyright © Huawei
Mobile Money

mb Be
er NULL
transaction
3.5 CPS_AUDIT_ACCOUNT
Audit log for account management.
Log Description
Audit logs in this category will record account management activities such as create account
for SP, modify account status.
Format
Table 1.1 cps_audit_account

mb Be
er NULL

 1000: Customer
Operator
 6000: Till
 8000: SP
belongs

Copyright © Huawei
Mobile Money

mb Be
er NULL
10 ON_IDEN_TYPE VARCHAR2(128) The operated identity Yes

type:
 1000: Customer
Operator
 6000: Till
 8000: SP
11 ON_IDENT_ID NUMBER(18) The operated identity ID Yes
12 ON_ACCOUNT_ID NUMBER(18) The operated account ID Yes
13 ON_ACCOUNT_TYP NUMBER(18) ID of the account type to Yes
E_ID be operated
0)
0)
16 ACTION_LOG_ID VARCHAR2(36) ACTION_LOG_ID in the Yes
CPS_ACTION_OPER_L
OG table for the current
service action
event.
E_TYPE initiator
E_VALUE initiator
20 ERROR_CODE VARCHAR2(32) The error code. Yes
transaction
3.6 CPS_AUDIT_CONF
Audit log for configuration management.

Copyright © Huawei
Mobile Money
Log Description
Audit logs in this category will record if any configuration is done in Mobile Money system.
For example:
 Create KYC field
 Create transaction reason type
 Modify action reason type
 Create charge profile
 Create product
Format
Table 1.1 cps_audit_conf

mb Be
er NULL

 Outside System
 SP Operator
 Customer
belongs
0)
0)
12 ITEM_TYPE VARCHAR2(128) The configuration item No
type
13 ITEM_ID VARCHAR2(512) The configuration item ID No

Copyright © Huawei
Mobile Money

mb Be
er NULL
14 ITEM_VERSION VARCHAR2(32) Version of a configuration Yes

item
15 RELATED_WF_ID VARCHAR2(100) ID of a related work flow Yes
task
16 RELATED_WF_TAS VARCHAR2(100) Task ID associated with Yes
KID this event
3.7 CPS_AUDIT_CARE
Audit log for customer care.
Log Description
Audit logs in this category are concerned with customer care aspects of the Mobile Money
system. For example:
 Take a call
 Close a call
 The operations about the identity in the customer care are recorded in Identity Management.
 The operations about the account in the customer care are recorded in Account Management.
 The operations about the transaction in the customer care are recorded in Transaction audit logs.
Format
Table 1.1 cps_audit_care

mb Be
er NULL

 Outside System
 SP Operator
 Customer

Copyright © Huawei
Mobile Money

mb Be
er NULL

initiator
8)
2)
10 ON_IDEN_TYPE VARCHAR2(12 The type of operated Yes
8) identity:
 1000: Customer
Operator
 6000: Till
 8000: SP
12 CARE_REC_ID NUMBER(18) The record ID of No
customer care
13 CARE_AUDIT_LOG_I NUMBER(18) The audit log of accounts Yes
D
3.8 CPS_AUDIT_TASK
Audit log for task.
Log Description
Audit logs in this category are concerned with task management in Mobile Money system.
For example:
 Create task on identity

Copyright © Huawei
Mobile Money
 Approve task
 Cancel task
 Suspend task
Format
Table 1.1 cps_audit_task

mb Be
er NULL

 Outside System
 SP Operator
 Customer
belongs
0)
0)
12 TASK_CATEGORY VARCHAR2(32) Task category: Yes
 Bulk task
 Workflow task
13 TASK_TYPE VARCHAR2(128) The task type Yes
14 TASK_ID VARCHAR2(100) The task ID Yes
15 RELATED_WF_ID VARCHAR2(100) The ID of the workflow Yes
instantiation processed in

Copyright © Huawei
Mobile Money

mb Be
er NULL
this time
3.9 CPS_AUDIT_SECURITY
Audit log for security.
Log Description
Audit logs in this category are concerned with the security of the Mobile Money system. For
example:
 Web user log on successful
 Web user log on failed
 Web user log out
Format
Table 1.1 cps_audit_security

mb Be
er NULL

 Outside System
 SP Operator
 Customer
initiator
8)

Copyright © Huawei
Mobile Money

mb Be
er NULL

2)
10 ON_IDEN_TYPE VARCHAR2(12 The type of operated Yes
8) identity:
 1000: Customer
Operator
 6000: Till
 8000: SP
12 FROM_IP VARCHAR2(16) The sourcing IP address Yes
3.10 CPS_AUDIT_QUERY
Audit log for query.
Log Description
Audit logs in this category will record any querying operations carried out in Mobile Money
system. For example:
 Search criteria
 Type of information viewed
 Flag of sensitive information viewed
 Flag of downloading information
The identities and accounts in the search result will not be recorded, but the search criteria will be
recorded instead.
Format

Copyright © Huawei
Mobile Money
Table 1.1 cps_audit_query

mb Be
er NULL

 CUSTOMER
 SP_OPERATOR
 ORG_OPERATOR
 SYSTEM_ADMINIST
RATOR
 MM_SYSTEM
 OUTSIDE_SYSTEM
initiator
8)
2)
10 DOWNLOAD_FLAG VARCHAR2(16) Whether it is No
downloaded:
 Yes
 No
11 IS_SENSITIVE VARCHAR2(16) Whether contains No
sensitive information:
 Yes
 No
12 SEARCH_CRITERIA VARCHAR2(10 The searching condition No
24)
13 INFO_TYPE VARCHAR2(12 Information query type No
8) (enumeration)
14 CARE_AUDIT_LOG_I NUMBER(18) Record the Audit Log ID Yes
D of the same Take a Call
event.

Copyright © Huawei
Mobile Money

Copyright © Huawei

Mobile Money V100R003 Log Reference 01

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mobile Money V100R003 Log Reference 01

Uploaded by

Copyright:

Available Formats

Mobile Money

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2017-07-28) Huawei Proprietary and Confidential i

About This Document

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 01 (2017-07-28) Huawei Proprietary and Confidential ii

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 01 (2017-07-28) Huawei Proprietary and Confidential iii

Database Operation Notice

Issue 01 (2017-07-28) Huawei Proprietary and Confidential iv

About This Document....................................................................................................................ii

2 Logs in the Files.............................................................................................................................2

3 Log in the Database.....................................................................................................................37

Issue 01 (2017-07-28) Huawei Proprietary and Confidential v

About This Chapter

1.1 Log Concept

1.2 Log Storage

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 1

2 Logs in the Files

About This Chapter

2.1 Log Type

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 2

 Technical supporting engineer locates complicated problem in the project execution or

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 3

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 4

2.2 Log File List

Table 1.1 Access Gateway (AG) log list

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 5

File Name Storage Path Description

ag_bizapp_c Records service container module

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 6

File Name Storage Path Description

ag_server.lo The path is $HOME/log/server for Records startup information of the

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 7

File Name Storage Path Description

Table 1.2 Service Registration (SR) log list

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 8

File Name Storage Path Description

sr_datasourc The path is Records all database information

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 9

File Name Storage Path Description

fails) about the SR NE.

Table 1.3 Bulk Task Scheduler (BTS) log list

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 10

File Name Storage Path Description

bts_perf.log Records the memory, database

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 11

File Name Storage Path Description

Table 1.4 Backend Core Services (BCS) log list

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 12

File Name Storage Path Description

business_flo Records the process for the BCS to

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 13

File Name Storage Path Description

Table 1.5 SP Web Application (SWA) log list

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 14

File Name Storage Path Description

ebug.log information and errors when

Issue 01 (2017-07-28) Huawei Proprietary and Confidential 15

File Name Storage Path Description