Military Communications and Information Technology: A Trusted ...

Military Communications and Information Technology: A Trusted ... Military Communications and Information Technology: A Trusted ...

22.01.2015 Views

16 Military Communications and Information Technology... A. Centralized logging From usage point of view, a system admin requires to keep all the system logs centrally view them through a central interface. Such a logging mechanism needs to behave in the same manner, with the same interfaces for different parts of the system such as client and server side application codes, integration module (including BizTalk capabilities) and SharePoint portal module. AirC2IS logging system (LOGS) provides necessary logging mechanisms for all these participants with the assistance and correct utilization of a collection of reusable components like Microsoft Enterprise Library (EntLib) [6] Logging Application Block which is designed by Microsoft Patterns and Practices team as a best practice implementation of an enterprise level logging system. Architecture of this centralized logging system supporting SOA logic is given in Fig. 4. Figure 4. AirC2IS logging system architecture Having a centralized logging architecture in such a system gives the system the benefit of managing all logs of the system from one location. General logging flow for AirC2IS components and the components in the figure are explained below: 1. Logging Utility: Logging Utility is a utility for the Silverlight client which is responsible for caching Silverlight client logs for a specified size and sending them to Remote Logging Service. 2. Remote Logging Service: Remote logging service is responsible for sending operational logs. Using this service, all operational logs are passed on to the LOGS architecture, giving the system the advantage of managing all logs from a single location.

Chapter 1: Concepts and Solutions for Communications and Information Systems 17 3. MSMQ: Microsoft Messaging Queue (MSMQ) [7] is a message queuing implementation provided by Microsoft in Windows operating systems which allows applications running on separate servers/processes to communicate in a failsafe manner. MSMQ stores the messages in its own store. The maximum limit of this store is configurable and this will be configured according to the performance of Log Storing Service, 4. Log Storing Service: The log storing service is a local windows service for reading logs from MSMQ periodically and writing them to the Log database. 5. AirC2IS Log & Audit DB: AirC2IS Log & Audit Database is an independent database for storing logs and audits. 6. Log Management Service: Log Management Service is a service for viewing and managing logs located in AirC2IS Log & Audit DB. LOGS is composed of three main components at the server side Remote Logging Service, an MSMQ and Log Storing Service. The logging flow of LOGS can be seen in Fig. 5. Figure 5. Logging flow at the server side In Fig. 5, (1) Remote Logging Service passes operational logs into an MSMQ. Since AirC2IS provides a centralized logging architecture, MSMQ is located here to avoid concurrency and locking issues. (2) This MSMQ is configured so that it passes the logs to Log Storing Service periodically. (3) After these logs are read from the queue, they are written by the Log Storing Service to the log & audit database. Of course LOGS includes all the necessary capabilities expected from and enterprise level system like configurable logging levels or log categorization. With such a modular approach we have achieved to build a SOA based modular logging system that can be consumed centrally by AirC2IS applications, portal module and integration module. This design gives necessary flexibility while maintaining the system since all the logging behavior can be configured and managed centrally.

Chapter 1: Concepts <strong>and</strong> Solutions for <strong>Communications</strong> <strong>and</strong> <strong>Information</strong> Systems<br />

17<br />

3. MSMQ: Microsoft Messaging Queue (MSMQ) [7] is a message queuing<br />

implementation provided by Microsoft in Windows operating systems<br />

which allows applications running on separate servers/processes to communicate<br />

in a failsafe manner. MSMQ stores the messages in its own store.<br />

The maximum limit of this store is configurable <strong>and</strong> this will be configured<br />

according to the performance of Log Storing Service,<br />

4. Log Storing Service: The log storing service is a local windows service for<br />

reading logs from MSMQ periodically <strong>and</strong> writing them to the Log database.<br />

5. AirC2IS Log & Audit DB: AirC2IS Log & Audit Database is an independent<br />

database for storing logs <strong>and</strong> audits.<br />

6. Log Management Service: Log Management Service is a service for viewing<br />

<strong>and</strong> managing logs located in AirC2IS Log & Audit DB.<br />

LOGS is composed of three main components at the server side Remote<br />

Logging Service, an MSMQ <strong>and</strong> Log Storing Service. The logging flow of LOGS<br />

can be seen in Fig. 5.<br />

Figure 5. Logging flow at the server side<br />

In Fig. 5, (1) Remote Logging Service passes operational logs into an MSMQ.<br />

Since AirC2IS provides a centralized logging architecture, MSMQ is located here to<br />

avoid concurrency <strong>and</strong> locking issues. (2) This MSMQ is configured so that it passes<br />

the logs to Log Storing Service periodically. (3) After these logs are read from<br />

the queue, they are written by the Log Storing Service to the log & audit database.<br />

Of course LOGS includes all the necessary capabilities expected from <strong>and</strong><br />

enterprise level system like configurable logging levels or log categorization. With<br />

such a modular approach we have achieved to build a SOA based modular logging<br />

system that can be consumed centrally by AirC2IS applications, portal module<br />

<strong>and</strong> integration module. This design gives necessary flexibility while maintaining<br />

the system since all the logging behavior can be configured <strong>and</strong> managed centrally.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!