KFS, KMM & OOI Operations Guide - Kuali Wiki - Kuali Foundation

boilermakerwrapperΗλεκτρονική - Συσκευές

8 Νοε 2013 (πριν από 3 χρόνια και 8 μήνες)

218 εμφανίσεις










Kuali Finance, Materiel Management and Organization of Interest



Operations Guide






Version:

Draft 1A

Last Updated:

November 8, 2013

Abstract:

An overview of KFS, KMM &
OOI system management procedures

File Ref:

Kuali Finance, Materiel Management, and Organization of Interest Operations
Guide.docx

Location:

EBSP

>
G l o b a l

>
D o c u me n t L i b r a r y

>
Y. P o s t G o L i v e Op e r a t i o n s


© 2011
Mi c hi g an St at e Uni ver s i t y
Boar d of Tr us t ees
, Eas t L ans i ng, MI 48824.

MS U i s an af f i r mat i ve
-
ac t i on, equal
-
oppor t uni t y empl oyer.




CONFI DENTI AL


FOR I NTERNAL USE ONLY












Document Control

Table
1

Document Control


Change Record

Date

Author

Version

Affected Section(s)

Change Reference
Description

05
-
05
-
2011

Scott
Cooley

Draft
1a

All

No Previous Document
































Table
2

Document Control
-

Reviewers

Name

Position / Expertise

Mike Criswell

Lead


Finance Technical Development

Bin Gao

Finance Developer, UC4, KFS

Dennis Shippy

EBSP Consultant

Linda Vernon

Lead


Testing, Project Admin.

Cathy Tan

Finance Developer

Jeff

Domeyer

Interfaces & Conversions
, OOI

Nasr Alavi

Technical


KMM Dev. Mgr.




Conventions Used In This Document


Code
: Coding conventions and example values are offset in Courier New font
with a style that allows for the preservation of proper tag and
syntax
formatting.



Caution
:
Alerts you to important supplementary information that is essential to the completion of a task; or that
failure to take or avoid a specific action could potentially result in data loss or security breach.


Note
:
Alerts
you to supplementary information that is useful to the completion of a task.


Reference
:
Alerts you to hyperlinked references to related or supplementary information either located internally
in this documentation set or externally on another site.


Tip
:
Alerts you to supplementary information that is not essential to the completion of the task at hand, but offers
a helpful hint, conceptual idea, or suggestion.


Task
: A
lerts you to
an activity, typically in the form of process task steps in an ord
ered list which provide step
-
by
-
step instructions.



KFS, KMM & OOI Operations Guide

Contents



v

Contents

Introduction

2

Purpose

................................
................................
................................
................................
......

2

Scope

................................
................................
................................
................................
.........

3

Audience

................................
................................
................................
................................
....

4

Ownership

................................
................................
................................
................................
..

4

Infr
astructure

5

Network

................................
................................
................................
................................
.....

5

Platform and Network A
rchitecture

................................
................................
............

5

Operations

................................
................................
................................
...................

6

Primary Services

................................
................................
................................
..........

6

Security

................................
................................
................................
........................

7

Hardware

................................
................................
................................
................................
...

8

Hardware and Network

Management

................................
................................
..........

8

Procedures

................................
................................
................................
...................

8

Failure Scenarios And Responses

................................
................................
................

9

Servers

................................
................................
................................
................................
.......

9

Server Configuration and Communication

................................
................................
..

9

Operational Support
................................
................................
................................
...

10

System Server Administration

................................
................................
...................

10

Enterprise Mangement Standards and Policies

................................
................................
........

14

System Requirements

................................
................................
................................

14

Production Control

................................
................................
................................
....

15

Monitoring
-

System, Application, and Database

................................
......................

15

Problem Management and Escalation

................................
................................
.......

16

Change Management

................................
................................
................................
.

16

Database System Support

................................
................................
..........................

17

Back
up Services

................................
................................
................................
........

18

Disaster Recovery

................................
................................
................................
......

19

Business Continuity

................................
................................
................................
...

19

System

20

Application and Database Server Architecture

................................
................................
........

20

Operating Systems

................................
................................
................................
...................

21

Red Hat Linux Enterprise

................................
................................
..........................

21

Windows 2003 Server

................................
................................
...............................

21

Server Operating System Code Backups and Recovery

................................
............

21

Database Tier

................................
................................
................................
...........................

22

Data Stage/Web App Servers Overview
................................
................................
....

22

Oracle Server

................................
................................
................................
.............

22

DBA Team Responsibilities

................................
................................
......................

23

Infrastructure Administration Team Responsibilities

................................
................

24

Backup Software Overview

................................
................................
.......................

24

Database Server Backup and Recovery

................................
................................
.....

25

vi



䍯湴e湴n

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e

Security and Access

................................
................................
................................
...

27

Data Protection and Encryption

................................
................................
.................

27

Application Tier

................................
................................
................................
.......................

28

JBoss
................................
................................
................................
..........................

28

Production Application Servers

................................
................................
.................

28

Production Application Server Configuration

................................
...........................

29

Application Web Server Procedures

................................
................................
..........

29

Failure Scenarios and Responses

................................
................................
...............

33

Client Tier

................................
................................
................................
................................

33

Client Desktop Environment Standards
................................
................................
.....

33

Application Access

................................
................................
................................
....

34

Database Access

................................
................................
................................
........

34

System Secur
ity and Accounts Management

................................
................................
...........

34

Access Rights Administration

................................
................................
...................

34

Procedures

................................
................................
................................
.................

34

Operating Systems

................................
................................
................................
.....

37

Databases

................................
................................
................................
...................

38

Applications
................................
................................
................................
...............

38

Authentication a
nd Password Standards

................................
................................
....

39

Protection Against Unauthorized Access

................................
................................
..

40

System Auditing and Logging

................................
................................
...................

40

Remote Access

................................
................................
................................
..........

40

Protection Aga
inst Viruses

................................
................................
........................

41

Communication of New Accounts

................................
................................
............

41

Tools

................................
................................
................................
..........................

41

Failure Scenarios and Responses

................................
................................
...............

44

System Maintenance

................................
................................
................................
................

44

Upgrades

................................
................................
................................
....................

44

Backups

................................
................................
................................
.....................

44

Tools Summary

................................
................................
................................
........................

44

Application

47

Application Security


Identity and Access Management

................................
.......................

47

Institutional Data Policy

................................
................................
............................

48

Release Package Management
................................
................................
...................

49

Kuali Financial System (KFS)

................................
................................
................................
.

51

Installation

................................
................................
................................
.................

52

Servers

................................
................................
................................
.......................

53

Configuration Management

................................
................................
.......................

53

Configuration Parameters

................................
................................
..........................

56

Sensitive Data

................................
................................
................................
............

56

Confidential D
ata

................................
................................
................................
......

56

Kuali Materiel Management (KMM)

................................
................................
.......................

57

Installation

................................
................................
................................
.................

57

Servers

................................
................................
................................
.......................

57

Configuration Management

................................
................................
.......................

57

Interfaces

................................
................................
................................
...................

59

Security

................................
................................
................................
......................

59

Sensitive Data

................................
................................
................................
............

59

Organization Of Interest (OOI)

................................
................................
................................

59

Installation

................................
................................
................................
.................

60

Servers

................................
................................
................................
.......................

60

Configuration Management

................................
................................
.......................

60

Security

................................
................................
................................
......................

60

Sensitive Data

................................
................................
................................
............

61

KFS, KMM & OOI Operations Guide

Contents



v楩

Maintenance Process

................................
................................
................................
.

61

Interfac
es Overview

................................
................................
................................
.................

65

Related Components

................................
................................
................................
................

66

Batch Job Scheduling (UC4)

................................
................................
.....................

66

File Transfer (Transport Server)

................................
................................
................

69

File Staging Storage (File Store)

................................
................................
...............

73

Check Writing (Paybase)

................................
................................
...........................

73

Identity Management (IDM)

................................
................................
.....................

74

Security (Sentinel)

................................
................................
................................
.....

74

Development Procedures

................................
................................
................................
.........

74

Applic
ation Development Environment Setup

................................
..........................

74

Software Development Tools

................................
................................
....................

75

Programming Guidelines

................................
................................
...........................

75

Source Control Procedures

................................
................................
........................

75

Configuration of Database Object and Application Files

................................
..........

78

Application Code Backups and Recovery

................................
................................
.

78

Maintenance and Support

................................
................................
................................
........

78

KFS Bucket Listing

................................
................................
................................
...

78

Upgrades and Backups

................................
................................
..............................

78

Planned Maintenance Schedule

................................
................................
.................

78

Training Support

................................
................................
................................
........

81

Issue Reporting and Resolution

................................
................................
...............................

81

Bug Fixes

................................
................................
................................
...................

81

Enhancements

................................
................................
................................
............

82

Service Desk

................................
................................
................................
..............

83

Code Migration

................................
................................
................................
........................

87

Bug Fix

and Code Migration Process

................................
................................
........

87

Production Version Control

................................
................................
.......................

88

Technical Merge Process

................................
................................
...........................

89

Patch Administration

................................
................................
................................
...............

91

Code

................................
................................
................................
..........................

91

Configuration
................................
................................
................................
.............

92

Data Model

................................
................................
................................
................

92

Bootstrap and Demo Data

................................
................................
.........................

92

Syst
em Patch Application Process

................................
................................
............

92

Logging and Reporting

................................
................................
................................
............

93

Server Log Analysis

................................
................................
................................
..

93

Reports

................................
................................
................................
......................

93

Failover and Recovery

................................
................................
................................
.............

94

Operat
ion Support Process

................................
................................
........................

94

Failure Scenarios and Responses

................................
................................
...............

94

Appendix A: Table of Figures

95

Appendix B: Table of Tables

96

Appendix C: Kuali Reference Material

97

Kuali Wiki


Rice Documentation Portal

................................
................................
..

97

Kuali Wiki


KFS Technical Implementation Coll
aboration

................................
....

97

Kuali Subversion Code Repository:

................................
................................
..........

97

Materiel Management Module


Kuali Wiki Space

................................
..................

97

KFS Help at MSU

................................
................................
................................
.....

97

EBSP Sharepoint


Technical Finance Documentation Library

................................

97

viii



䍯湴e湴n

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e

Open and Closed Issues for this Deliverable

98

Glossary of Terms

99

Index

103


Confidential


for internal use only


KFS, KMM & OOI Operations Guide

Introduction



1





Confidential


for internal use only


2



䥮瑲潤tc瑩tn

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e


Introduction


Operations of the Kuali Finance, Materiel Management and Organization of Interest enterprise business systems at
Michigan State University encompasses work across three broad categories


Infrastructure, System, and Application.

To understand how MSU man
ages these systems, it is important to understand all three

areas
, and to understand them in
a particular order. Therefore, this guide is organized accordingly.

The
three main chapters of this guide

are:


Table
3

Document Organization
-

Chapters Within This Guide

Chapter

Brief
Description

Infrastructure

network, hardware, servers, standards and policies

System

architecture; operating systems; database, application & client tiers; security; and administration

Application

KFS, KMM & OOI installation & configuration; related components; and maintenance procedures


Purpose

The purpose of the
Operations Guide

document is to describe the new procedures and tools that have been designed to
assist Michigan State University information systems operations staff with managing the new systems environment.
This interim document is intended to be an initial design doc
ument for procedures that will continue to be refined. It will
serve as a major reference source for the creation of a larger, more comprehensive system management guide, or evolve
to become that guide.

It is intended to serve as a source of

technical

i
nformation about how the related Kuali Finance, Materiel Mangement,
and Organization Of Interest systems are operated at MSU.

Included is confidential information about the EBS technical
environment at MSU. As components are changed, this “living” docume
nt will need to be updated regularly.


The
major subject matter areas

covered in this document include:


Table
4

Operations Guide Content Links & Major Subject Matter Area Descriptions

Chapter

(linked to topic)

Brief
Description

of Content

Confidential


for internal use only


KFS, KMM & OOI Operations Guide

Introduction



3

Chapter

(linked to topic)

Brief
Description

of Content


Infrastructure



Hardware and Networks Management

-

The procedures and tools needed for
management of the hardware and network configuration in the new system.



Capacity Planning and Performance Management

-

T
he procedures and tools needed
for management of the new system performance, and the future planning of capacity.



Server and Network Operations

-

Discusses the services offered by the Server and
Network Operations Centers at MSU.



Enterprise Management Stan
dards and Policies

-

Discusses the standards and policies in
existence for the system management area.




System



Database Tier

-

The procedures and tools needed for managing data and servers in the
database tier of the new system.



Applications Tier

-

The procedures and tools needed for managing servers

in the
applications tier of the new system.



Security and Accounts Management

-

The procedures and tools needed for managing the
access to systems and for managing new user requests.



Tools Summary

-

Summarizes the tools selected to help manage the production systems.



Application



Software Management

-

The procedures and tools needed for management of all the
software components of the new systems.



Planned Maintenance Schedule
s

-

Gives a summary of all the planned main
tenance that
will affect the system, and whether this will result in a full or partial system outage.







Key Concept /
Reliability
Disclaimer
: When attempting to understand the purpose of a deliverable document
such as this, it is important to keep in mind the way modern wiki technology has an impact. The key concept here
is that the type of information typically written and maintained in a d
ocument such as this is in fact more efficient
to author, maintain and view in a shared online wiki space as a series of organized pages within that space, which
can also be easily exported and/or printed on demand. Due to this fact, the audience/maintain
ers of this document
will have a preference to maintain this information in a single wiki location rather than update the same
information in two places


瑨攠wik椠f楲s琬t慮d th敮 愠word do捵men琠tuch 慳⁴a楳 on攮 qh敲敦or攬 瑨攠w楫椠
楮form慴楯n is 汩k敬y

瑯 b攠mor攠up
J

J
d慴攠and r敬楡e汥l qhe m慪or楴i of inform慴楯n 捯n瑡楮敤 h敲敩n r敳楤敳⁨敲攺e
h瑴ts㨯⽳h慲数o楮琮tbspKmsuK敤u⽔⽔散hn楣慬⽗楫i┲Mm慧敳⽈em攮慳ax

Eb_卐㹔
敡ms[q散hn楣慬it楫椠
m慧敳㹆en慮捥FK


Scope

This document covers the management and operations of the following systems, applications and technical
infrastructure:

Confidential


for internal use only


4



䥮瑲潤tc瑩tn

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e



Kuali Financial



Materiel Management



Organization Of Interest

This document does
not

include the management and operations of the following related systems:



Basis/SAP



Business Intelligence



Research Administration


This document summarizes and references more detailed information that exists in separate documents that are
maintained by
technical experts and stored in shared drives, on web sites, and in wikis.


Audience

The target audience for this document is Michigan State University (MSU) Enterprise Business Systems (EBS) staff
members who are involved in the
operation, administration, and maintenance of the Kuali Financial System (KFS), Kuali
Materiel Management (KMM) and Organization of Interest (OOI) systems. Job titles are typically Information
Technologist, but the roles vary, and may include Software Dev
elopers, System Administrators, Database Administrators
(DBA), Security Analysts, Technical Services, and Infrastructure Administrators. These individuals may be members of
teams such as Development KFS (Finance), Infrastructure Administration, Interfaces

& Conversions, Technical, and/or
Data Warehouse within the Enterprise Business Systems Projects group; and may also include members of the
Production Services, Operations Control Center, Technical Services, Data Administration and Security, and
Department
al Systems and Services teams with the Administrative Information Services (AIS) department.

Ownership

The EBSP
Technical
Finance
De
velopment Team

(
EBSP.DevelopmentKFS
.Expanded@ais.msu.edu)

is
primarily

responsible for ensuring this document is necessary, reflects actual practice, and supports University policy.

However,
due to the wide scope of this document, responsibilities are sh
ared amongst the many teams and departments listed in the
preceding Audience section.





Confidential


for internal use only


KFS, KMM & OOI Operations Guide

Infrastructure



5

Infrastructure

The KFS, KMM and OOI systems operate by using network and server hardware and software that is governed by
enterprise
-
wide standards and policies.

Thi
s infrastructure is installed and maintained by MSU support staff in a variety
of locations who are employed in several departments within the Libraries, Computing and Technology unit. This
chapter identifies the componets, their connectivity, and the exp
erts involved in their ongoing support.

In this chapter
:



Network



Hardware



Servers



Enterprise Mangement
Standards and Policies

Network

The Academic Technology Services (ATS) department provides internet communication technology for the MSU
campus; implements MSU’s backbone network architecture; and provides wired net
work connections in offices that
house users of MSU’s Enterprise Business Systems (EBS), including Kuali Finance, Materiel Management, and
Organization of Interest.

Platform and Network Architecture

EBS data is stored on two high
-
performance storage area networks (SAN) which are physically separated to aid
redundancy and physical security. SANs provide the benefit of guaranteed high performance and advance business
continuity and disaster recovery

abilities for EBS’s mission critical applications and databases.

The SAN
consists of two Dell EMC CX4
-
960 systems distributed between the AIS
data center

and the ATS data center,
with 116 terabytes of 7200 RPM SATA disks

in total
. Servers and storage sys
tems are connected to two redundant SAN
fabrics through Brocade Fibre Channel switches and directors. Available features of High Performance SAN storage
include LUN snapshots and clones, Quality of Service (QoS) performance guarantees, and synchronous mirr
oring
between data centers.

Only production and mission critical databases and systems are replicated to the SAN in ATS. All servers are
redundantly connected to each SAN fabrics via a dual
-
port host bus adapter.


Confidential


for internal use only


6



䥮晲慳瑲畣瑵牥

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e


Figure
1

EBS SAN

Architecture depicting ATS & AIS switches with EBSP Server Connections


Operations

The Academic Technology Services (ATS) department manages the organization’s network. A series of committees,
and network groups help determin
e the direction and scope of the network. The two groups charged with managing the
core network are Libraries, Computing and Technology unit, the ATS department, and the Administrative Information
Services (AIS) department. In facilitating the evolution o
f network, ATS seeks to fulfill the requirements of MSU. ATS
responsibilities include:



manage and maintain the organization’s Internet links



maintain network monitoring systems



maintain domain name service (DNS) for organization's domains.



maintain e
-
mail

alias and postmaster functions

Primary Services

The primary services supported by ATS are:



design of the network in conjunction with advisory groups



network management, operations, monitoring, and network event reporting

Confidential


for internal use only


KFS, KMM & OOI Operations Guide

Infrastructure



7



maintena
nce and configuration of the routers, bridges, and VPN equipment.



maintenance and documentation of the fiber and other cabling physical plant



design and monitoring of the Internet connections



maintain the master DNS for the organization’s domains



maintain

e
-
mail alias subsystem and mail hubs



performance of postmaster functions



maintain network monitoring systems



security and event monitoring and management



MSU Network
-

MSUnet



network consulting and installation



network security



virtual private networking



wireless management and installation



web hosting



network security



virtual private networking



MSU ID provisioning and security management

Security

Network security includes hardware firewall protection and anti
-
virus software protection software.

Firewall Protection

Both hardware and software firewalls exist within the network, some administered by Administrative Information
Services (AIS) and some by Academic Technology Services (ATS).



For more information, contact Jim Smith
(manager) or Brad Fears (supervisor) from the Infrastructure and
Network Support Group of the AIS Technical Services Team
.

Virus Protection

The AIS Technical Services and Departmental Systems & Services (DSS) teams are responsibl
e for the usage of
Kaspersky Anti
-
Virus 6.0 for all Windows workstations and servers. Reports are generated from the antivirus
management console that list the latest virus definition file of all workstations and servers. All anti
-
virus settings are
lock
ed by policies that are applied to prevent users from changing settings, and newly installed workstations and servers
are added to security groups for proper application of file, web & registry protection against viruses, network attacks,
spyware and other

malicious programs.

Confidential


for internal use only


8



䥮I
牡r瑲畣瑵牥

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e


Figure
2

Kaspersky Anti
-
Virus Management Console


Events Report Example


Hardware

Hardware and Network Management

Virtual Server Overview

To maximize performance and configuration flexibility while keeping costs moderate, the EBS architecture utilizes
“commodity server” hardware. The use of standardized, high
-
performance server modules across the entire physical
architecture provides the nec
essary level of performance and service flexibility and allows easy scalability and
configuration flexibility as system needs change over time.
All virtual servers run on Dell VM Base
-
8 R710 servers each
with 72Gb of memory and 8 CPUs.


The architectur
e also makes extensive use of VMWare virtual servers rather than dedicated hardware server. Server
virtualization provides a high level of flexibility in the allocation and use of physical hardware resources and
configuration changes. The servers in the
EBS architecture are all virtual servers except in cases where VMWare is not
supported by the application vendor or performance expectations could not be met.

Procedures

Change Management Procedure

This section describes the procedures for managing changes to the hardware and networks.

Configuration Testing Procedure

This section describes the procedures for testing configurations.

Confidential


for internal use only


KFS, KMM & OOI Operations Guide

Infrastructure



9

Network Printers

This section describes procedures for managing networked printers.

Tools

This section describes the tools that will be used for managing hardware and networks.

Failure Scenarios And Responses

<Failure Type>

<Failure Type>

Servers

Server Configuration and Communication

The Administrative Information Services (AIS) department’s

Production Services and Technical Services teams, in
conjunction with the EBSP Infrastructure Administration team, provide the technical home for many of the computer
systems used to support the administrative applications of MSU. These include financial

systems, payroll, human
resources, and others. Some of these systems reside on a large mainframe computer while the rest reside on a
heterogeneous mix of servers and virtual servers. They are primarily housed in the Computer Room of the Hannah
Administrat
ion building.

Under the Enterprise Business Systems (EBS) project, many of these systems and applications have been or will be
replaced by new, more robust core administrative systems. The architecture for the new systems is described in the
Platform and
Network Architecture and Application and Database Server Architecture sections of this document.

The EBSP Infrastructure Administration team provides a comprehensive set of services including technology acquisition,
systems management, operations, technica
l support and services. The following provides a description of these services:

Operational Support

The EBSP Infrastructure Administration team provides physical facilities for the location and operation of large
computer systems and the majority of admin
istrative processing servers. Operational support includes enterprise
-
wide
applications monitoring, backup and recovery, database monitoring, problem determination and resolution, trouble ticket
generation, notification of problems via e
-
mail, problem esc
alation, and performance monitoring of computer resources.
These services are provided on a 7x24x52 basis (7 days a week, 24 hours a day, and 52 weeks a year) by a dedicated
staff of systems operators.

Systems Administration
-
Servers

The EBSP Infrastructur
e Administration team has a technical support staff providing support and maintenance of the
operating systems and servers. Systems administration functions include capacity planning, security administration,
hardware and software change management, and O
S maintenance.

Database System Support

The EBSP Infrastructure Administration team provides technical support for the Oracle database servers. The staff
installs, monitors, and tunes the Oracle software and hardware, and provides related applications serv
ices, including web
access to the databases and support of web servers.

Disaster Recovery

The EBSP Infrastructure Administration team plans and tests the recovery of primary administrative applications. The
plan is a technical recovery plan and does not
address the recovery of business processes which use the administrative
applications that would be recovered in the case of a technical or physical disaster at Michigan State University.

Confidential


for internal use only


10



䥮晲慳瑲畣瑵te

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e

Backup Services

The EBSP Infrastructure Administration team provides
remote backup and recovery services for servers and client
devices located throughout the organization.

Production Control

The EBSP Infrastructure Administration team provides a complete production control and job scheduling service. This
service ensures
that production cycles are completed in a timely and accurate fashion. Production control provides the
quality and scheduling required to ensure that financial controls are maintained throughout the business processes.

Operational Support

The EBSP Infrastructure Administration team works with the AIS Production Services team to manage the operations of
the physical facilities where the servers are located. This is staffed 24 hours per day, 7 days per week. Critical events
and

scheduled maintenance for services provided by ATS and AIS are monitored using Service Status, where Libraries,
Computing & Technology unit help desks receive automatic notifications of critical events such as power failure alerts.

Computer operations a
nd operational support services include:



Client interaction for production job scheduling and report printing



Computer room environmental equipment, hardware/software systems



Hardware/software systems monitoring on a 24/7 basis



Disaster Recovery assistance



Data backups



Incident and Problem tracking resolution associated with processing production batch jobs and AIS computer
room hardware/software systems



Job Scheduling and Monitoring



MSU Service Alert publication and update for

data center
-
related alerts



Problem Determination for First and Second Level Support



Print/Output Services



Special Job Processing Coordination






Tape movement



Change Management



Comput
er Room Security Access



Data Center Facilities and Stockroom Management



IT Service Desk Administrator Functions



Second Level Problem Determination and Resolution



Tape Library Management



UC4 Project (New Scheduling System)

System Server Administration

EBS uses five separate technical envir
onments:

Confidential


for internal use only


KFS, KMM & OOI Operations Guide

Infrastructure







The
Sandbox/Dev

environment is used for the initial development of system changes and updates. Changes in
Sandbox/Dev are migrated to Test for testing.



The
Test

environment is used for the testing of new code and system changes. Changes to the T
est
environment are migrated to the QA environment for testing.



The
QA

environment is used to perform Quality Assurance testing prior to migration of code and system
changes into the production or training environments. Once changes and updates have passed the Quality
Assurance process they are migrated to either Production

or Training, as necessary, for use.



The
Production

environment is the EBS production system.



The
Training

environment is used for system training and other non
-
production uses.


Figure
3

Finance Landscape Environments Matrix



Confidential


for internal use only


12



䥮晲慳瑲畣瑵te

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e

D
ual Finance Landscapes

Two separate landscapes

are used to support KFS, KMM, and OOI activities.



Production Support Landscape



code under this landscape is primarily used for supporting fixes to
production releases of the above applications. The goal should be to use this landscape to maintain existing
functionality. Minor enhancements may be pushed through. Requirements: Low
risk with minimal impact to
other functionality, will not hold up important fixes, Functional and Technical Specs still need to be created or
updated.



Alternative Development Landscape



applications deployed in this landscape support code with new
enhance
ments/features that will eventually moved to the Production Support Landscape as a new release.



Figure
4

Dual Finance Landscape Environments




Sandbox/Dev


Table
5

Sandbox Environm
ent Servers List

IP Address

DNS Name

Processors

LPAR

Memory

Confidential


for internal use only


KFS, KMM & OOI Operations Guide

Infrastructure





IP Address

DNS Name

Processors

LPAR

Memory


























































Test


Table
6

Test Environment Servers List

IP Address

DNS Name

Processors

LPAR

Memory


























































QA


Table
7

Quality Assurance Environment Servers List

IP Address

DNS Name

Processors

LPAR

Memory
















Confidential


for internal use only


14



䥮晲慳瑲畣瑵te

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e

IP Address

DNS Name

Processors

LPAR

Memory











































Production


Table
8

Production Environment Servers List

IP Address

DNS Name

Processors

LPAR

Memory


























































Enterprise Mangement
Standards and Policies

Enterprise Management Standards and Policies apply uniformly to most, if not all, systems managed by the
EBSP
Finance Development and Infrastructure Administration teams
. Variance
s may exist for a variety of reasons: the
AIS
Production Services and Technical Services teams do not own all the machines that they manage
, hence some standards
and policies are determined by customer requirements; or the machine or application is not SN
MP compliant (see below
under Systems Requirements).

System Requirements

In order t
o manage customer machines housed in the AIS Computer Room, it is required
that they be SNMP
-
compliant
to allow enterprise
-
wide management
services over ethernet. Customer machines are monitored via intelligent clients on
customer machines that communicate via SN
MP with

enterprise management monitors. A corollary to this is that
Confidential


for internal use only


KFS, KMM & OOI Operations Guide

Infrastructure





m
anaged machines must be network
-
accessible to the enterprise
management systems. Disk storage as well as memory
requirements for the machine will depend on the level of services desired but must be adequate to accommodate the
necessary clients.

Production Control

The EBSP Infrastructure
Administration team provides a complete production control and job scheduling service. This
service ensures that production cycles are completed in a timely and accurate fashion. Production control provides the
quality and scheduling required to ensure t
hat financial controls are maintained throughout the business processes.

Production System Installation


System Startup and Shutdown Steps


Capacity Planning and Performance

Management


Procedures

This section describes the procedures for monitoring performance and proactive capacity planning.

Troubleshooting / Performance Issues

General System Health

Single Issue Health Check

Oracle Issues

Tools

This section describes the tools that will be used for perfor
mance monitoring and capacity planning.

Failure Scenarios and Responses



<Failure Type>



<Failure Type>


Monitoring
-

System, Application, and Database

The EBSP Infrastructure Administration team monitors machines on the enterprise by means of the following tools:



Service Status



WebMon

Confidential


for internal use only


16



䥮晲慳瑲畣瑵te

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e

Systems Monitoring

Event Logging / Pr
oduction Summary Reports

OS Monitoring Parameter/Thresholds

Database Monitoring Parameters/Thresholds

Applica
tion Monitoring Parameters/Thresholds

Problem Management and Escalation

The enterprise system monitoring tools are integrated with problem management and will
generate trouble tickets with
the AIS Customer Help Center and Service Desk when unexpected conditions are trapped. This will initiate problem
escalation depending on severity of the failing components and the appropriate Service Level Agreement. Problem

escalation will comprise a range of actions
-
from notifying responsible individuals via e
-
mail to operator initiated paging
based on a contact list.



For more information, see the
Service Desk

section within the Issue Reporting and Resolution topic in the
Application chapter of this document.

Change Management

All system software, hardware and database changes required by the EBS SupportTeam are requested by the va
rious
EBS Support Teams and performed by the AIS team. Control over these changes is covered within the infrastructure
change control process. Specfic tasks:



Server updates



Direct Updates to Cognos settings in production



KFS Database updates and moves



Co
nnections between systems


All changes to applications, operating systems, and technical infrastructure for production systems must be scheduled.
Changes must be logged as trouble tickets.
Different scheduling and tracking meth
ods are used depending on the type of
change.
Tools used to accomplish these tasks are:



Sharepoint Issue Tracking List






AIS Service Desk






AIS eForms
-


Confidential


for internal use only


KFS, KMM & OOI Operations Guide

Infrastructure





Service Alert Process


Figure
5

EBS Production Change Management
-

Service Alert Process


Database System Support

The Client Server group within AIS Technical Services and EBSP Infrastructure Administration, along with the EBSP
Finance Technical Develo
pment team and the DBA from AIS Data and Security Administration Team are all involved
in providing technical support for the Oracle database servers. Collectively, t
he staff installs, monitors, and tunes the
Oracle software and hardware, and provides re
lated applications services, including web access to the databases and
support of web servers.

Database Infrastructure Roles and Responsibilities

The following RACI chart summarizes the roles of t
he different teams involved in the setup and ongoing support of the
Oracle DB infrastructure in the MSU EBS environment.



For details of the various tasks for which the DBA team is responsible, as well as the participation by and
interaction with other
teams, see the System > Database Tier section
.


Table
9

EBS Data Administration Tasks and Team Responsibilities

Confidential


for internal use only


18



䥮晲慳瑲畣瑵te

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e

Task

DBA
Team

App
Team

UNIX
Team

Backup
Team

Storage
Team

Root
Privileges

Install UNIX O/S, patch O/S,create needed
filesystems on DB servers (Kernel patches)

C

I

R

I

I

Yes

Set up UNIX accounts for DBAs and oinstall
etc.

C


R

C

C

Yes

Server level capacity planning

C

C

R

C

C


Monitor and fix any server level performance
issues, memory issues for DB servers

I

I

R

I

I

Yes

Allocate storage to DB servers

C

I

A


R


Installing /upgrading/patching and configuring
Oracle software (clusterware, rdbms Server and
applications like agents,OMS)

R

I

A



Sudo or
temp root

Set up instance and create database

R

C

C

I

I

No

Development and implementation of database
backup and recovery strategy (RMAN scripts)
(Periodic testing of the strategy)

R

C

C

A


No

Backup, restore/recover production database
(Daily monitoring)

R

I


R


No

Refreshing dev/qa databases (RMAN/Export
import/

R

I

I

A


No

Monitoring and optimizing DB performance

R

A

A


A

No

Naming standards for schema objects
(tablespace naming example)

A

R




No

Oracle Patching for application requirements

R

A

A



No
(Temp)

Tools selection

R

C

C

C

C


Migration to
QA/Prod (Schema changes)

R

A




No

Interacting with Oracle for DB related SRs

R

A

A

C

C

No

Developing server build sheets for new DB
servers

R

C

C



No

Legend: R
-

Responsible (task performer); A
-

Assists (assists responsible team); C
-

Consulted; I
-

Informed


Backup Services

The EBSP Infrastructure Administration team provides remote backup and recovery services for servers and client
devices located throughout the organization.

Backup and
Recovery Tools

CommVault

is used to back up file systems and databases on servers managed by the EBSP Infr
astructure
Administration team and the Client Server group of the AIS Technical Services team.

On customer request, these
backup tapes may be stored offsite.



For more information, see
Backup Software Overview

in System > Database Tier.


Confidential


for internal use only


KFS, KMM & OOI Operations Guide






Disaster Recovery

Technical Recovery Plan

The Infrastructure Administration team, in conjunction with the AIS Production Services team,
plans and tests the
recovery of primary administrative applications.

The plan is a
technical recovery plan and does not address the recovery of business processes which use the
administrative applications that would be recovered in the case of a technical or physical disaster at Michigan State
University.

KFS, KMM and OOI are considered
critical, high
-
priority business systems. The disaster recovery plan includes an
OPERATIONS RECOVERY TEAM who take responsibility for initiating recovery and performing interim processing
for critical business applications as well as direct the activities

of support teams at the recovery site.

Contact
: Sharon Bennett, Team Leader


Production Services Operations Support

Business Continuity

Functional Recovery Plan

Business processes for KFS, KMM and OOI are recovered as part o
f a functional recovery plan, which is the
responsibility of the Controller’s Office. They acknowledge the need for such a plan, and have a plan in place to
produce one.

Contact
: Vince Schimizzi, Team Leader


EBSP Finance Functional Team


For more info
rmation, see
http://ctlr.msu.edu/combp/

MSU Controller’s Office Web Site


䵡nu慬aof _usin敳s
mro捥dur敳e




Confidential


for internal use only


20



Sys瑥m

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e

System

On top of the infrastructure level is the system level of management, which includes administration of servers, operating
systems, and various software tools that run on the hardware to operate the systems, and provides an overview of how
they are construc
ted and connected.

This chapter describes the architecture, tiers and tools that make up the systems that are used to manage the KFS, KMM,
and OOI applications.

In this chapter
:



Application and Database Server Architecture



Operating Systems



Database Tier



Application Tier



Client Tier



System Security and Accounts Management



System
Maintenance



Tools Summary

Application and Database Server Architecture


KFS/KMM/OOI

All components of the Kuali Financial System, Kuali Materials
Management, and Organization of Interest Systems run
on a cluster of three servers.


Finance Oracle Database Cluster

KFS/KMM/OOI databases reside on a virtual Oracle RAC Server running Oracle 11g.

Confidential


for internal use only


KFS, KMM & OOI Operations Guide

System






Figure
6

EBS Technical Architecture (Production)

Operating Systems

The two primary operating systems used for KFS, KMM and OOI servers (and related applications) are:



Windows 2003 Server



CVS source code repository, MS SQL Server 2005,

MS Internet Information Server,
MS Sharepoint, and Paybase checkwriting system servers.



Red Hat Linux Enterprise



Developer’s application & database servers, main application test, functional unit
test, quality assurance test, end
-
to
-
end test, database,
filestore, and ad
-
hoc applications servers.

Red Hat Linux Enterprise

Operating System Setup

EBS Base Installation
:


Windows 2003 Server

Server Operating System Code Backups and Recovery



Confidential


for internal use only


22



Sys瑥m

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e

Database Tier

This section gives an overview of database management considerations and issues.

Data Stage/Web App Servers
Overview

The EBS production environment has two independent DataStage Server/Web Application Server pairs. Each pair has
the same hardware and software configuration as the other and each may stand in for the other if needed but no failover
or other high availabil
ity measures are used. In general use HCM jobs are executed on one server and Finance jobs on
the other.



IS DataStage Web Application Servers

-

DataStage users connect to the DS Web Application Server to
perform LDAP authentication then to connect with
the associated DataStage Server for job execution.



IS DataStage Servers

-

The DataStage Servers are application servers where DataStage jobs are executed.

Oracle Server

Oracle Real Application Clusters (RAC)

is an option to the Oracle Database Enterpri
se Edition. Oracle RAC is a
cluster database with a shared cache architecture that overcomes the limitations of traditional shared
-
nothing and shared
-
disk approaches to provide highly scalable and available database solutions for all your business applicat
ions. Oracle
RAC is a key component of Oracle's private cloud architecture. Oracle RAC support is included in the Oracle Database
Standard Edition for higher levels of system uptime.

Oracle RAC One Node

is a new option available with Oracle Database 11g R
elease 2. Oracle RAC One Node is a
single instance of an Oracle RAC enabled database running on one node in a cluster. This option adds to the flexibility
that Oracle offers for database consolidation while reducing management overhead by providing a stand
ard deployment
for Oracle Databases in the enterprise.

The current inventory of the Oracle infrastructure is comprised of Grid/Clusterware and Real Application Clusers
(RACs).


Table
10

Grid / Clusterware

#

N
ame

DEV/QA/PROD

# of Nodes

Version

1

EBSPRD100 (KFS)

Prod

3

11.2.01

2

EBSPRD290(SAP)

Prod

3

11.2.0.1

3

EBSPRD390(DW/BI)

Prod

3

11.2.0.1

4

EBSQA100D(CRSHOME)

QA

2

11.2.0.1

5

EBSQA390D(DW/BI)

QA

2

11.2.0.1

6

IDMPRD1

Prod

2

11.2.0.1







Table
11

RAC Databases

#

Name

DEV/QA/PROD

# of Instances

Version

1

BIPRD

Prod

3

11.2.01

2

FINPRD

Prod

3

11.2.0.1

3

IDMPRD1

Prod

2

11.2.0.1

4

MSUDIM

Prod

3

11.2.0.1

Confidential


for internal use only


KFS, KMM & OOI Operations Guide

System





#

Name

DEV/QA/PROD

# of Instances

Version

5

MSUEDW

Prod

3

11.2.0.1

6

HP1 (SAP)

Prod

3

11.2.0.1

7

PP1 (SAP)

Prod

3

11.2.0.1

8

PP2 (SAP)

Prod

3

11.2.0.1

9

BP1 (SAP)

Prod

3

11.2.0.1

10

XP1 (SAP)

Prod

3

11.2.0.1

11

SP1 (SAP)

Prod

3

11.2.0.1

12

BIQUAL

QA

2

11.2.0.1

13

FINQUAL

QA

2

11.2.0.1

14

MSUDIMQ

QA

2

11.2.0.1

15

MSUEDWQ

QA

2

11.2.0.1

16

MSUEDWQ3

QA

2

11.2.0.1







DBA Team Responsibilities

A team of database administrators share the following responsibilities with members of the Application, UNIX, and
Storage teams:



Installing and upgrading the Oracle Database
server and application tools



Allocating system storage and planning future storage requirements for the database system



Creating
database and
primary database storage structures (tablespaces) after application developers have
designed an application



Creati
ng primary objects (tables, views, indexes) once application developers have designed an application



Modifying the database structure, as necessary, from information given by application developers



Enrolling users and maintaining system security



Ensuring c
ompliance with Oracle license agreements



Controlling and monitoring user access to the database



Monitoring and optimizing the performance of the database



Planning for backup and recovery of database information



Maintaining archived data on tape



Backing up
and restoring the database



Contacting Oracle for technical support


Key personnel currently involved in this work from the AIS Data Administration and Security Team include:



John Griffith, Assistant Director



Dan Skinner, supervisor



Srikant Sulibhavi,
DBA
-

primary responsibility

Confidential


for internal use only


24



Sys瑥m

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e


Infrastructure Administration Team Responsibilities

Hot and cold database backups are handled by the Client Server group, which is a part of the AIS Technical Services
team (and EBSP Infrastructure Administration team).

Their group e
-
mail address is
csbackup@ais
.msu.edu

.

Personnel currently involved in this work include:



Jim Smith, manager



Pat Murphy, senior team member



Sergey Dashievsky, primary person responsible



Amy Houghton, secondary support



Pat Bellville, secondary support

Backup Software Overview

The vendor CommVault’s product is used for snapshot, replication and persistent copies that are secure, deduplicated
and managed and accessible through a single, unified platform, using virtualization that bridges physical and v
irtual data
management. It is the primary tool used for backup device and SAN storage.


Figure
7

CommVault Tape Management System Library Network
-

Example

CommVault Capabilities



Common Technology Platform



Virtual Server
Protection



Migration Tools

Confidential


for internal use only


KFS, KMM & OOI Operations Guide

System







Central Management



Capacity Licensing



Cloud Storage connectors



Archive and Search



Gen 3
D
eduplication


Storage Layout

Disk Backup

Restoration Process

Backup Schedule Policy

Data Tape R
etention



Currently, AIS practice dictates that LT04 tapes (1.6 terrabyte) are retained for
8 weeks
.



Typical enterprise data retention policy requirements

are as follows:

Tapes of nightly backups at fiscal
month
-
end

will be retained for
five

years
.

Tapes of nightly backups at fiscal
year
-
end

will be retained for
10

years
.

All other nightly backup tapes will be retained for
60 days
.

Database Server Backup and Recovery


Production vs. Development Servers

Scheduled backups for KFS/KMM/OOI database servers are not scheduled separately for production and development
servers. The schedule consists of a combination of Oracle database hot backups, nightly server file sy
stem backups, and
weekly full backups.

Hot Backups

The database availability requirement is the most restrictive recovery factor. For databases that have a high availability
requirement (7x24), database administrators have to use a ho
t backup methodology. A hot backup (also known as an
online backup) is taken while the database is open to users. A hot backup consists of backing up all the datafiles related
to a specific tablespace, while the tablespace is held in an offline state. Th
e archived redo logs and the control files are
also backed
-
up. The database must be operating in ARCHIVELOG mode.

Daily
Schedule
: The typical start time for nightly
incremental backups

is 6:00pm Eastern Standard Time, and these
typically take two hours t
o complete.


Off
-
Peak Schedule
: Hot backups are performed during off
-
peak times as they increase the load on the database.

Confidential


for internal use only


26



Sys瑥m

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e

The Commvault backup utility and tape management system is used for hot backups. These are currently scheduled to
run in an
automated fashion according to the daily schedule.

Weekly Schedule
: Each Friday night, a
full backup

is scheduled beginning at 11:00pm Eastern Standard Time. This
typically takes more than 24 hours, completing on Saturday night. Approximately 566 backup
s occur, with 75 running at
a time. The database will be shutdown and inaccessible during this process.

Cold Backups

Basic cold backups (also known as offline backups) performed at regular intervals provide reliable data protection.

Cold
backups require shutting down the Oracle database in NORMAL mode and backing up all required database files,
datafiles, the control file, archived redo log files (if they exist), and the parameter file.

An offline backup is similar to a complete syst
em backup, except that it is taken for a subset of the files. All third party
software that may be modifying the Oracle files, should be shutdown first. In most cases the database is brought down in
the IMMEDIATE mode and then is restarted and brought do
wn in the NORMAL mode.

Oracle’s Enterprise Backup Utility and CommVault Tape Management System are used for cold backups.


Procedure


To
perform a cold backup
:

1.

Send an e
-
mail to
csbackup@ais.msu.edu

to formally make the request.

2.

Specify the name of the server the database resides on.

3.

Specify the directories it is in.

4.

Specify the time the backup is needed.


End of activity.


Logical Backups
: A logical backup of the
database involves reading a set of the database records and writing them to
file. Oracle's Export Utility reads the database and writes the export dump file to a binary file. The export utility has a
number of parameters that allow for the export of the f
ull database, the objects of a specific user, or specific tables,
whether or not indexes should be included or not, whether data should be included or not, and so on. The dump file
includes all the commands needed to re
-
create all the exported objects.


KFS/KMM/OOI applications support an export of the entire database, so in this case, a logical backup is a
long process, and the import from the dump export file takes even longer.

Enterprise Manager Backup Tool

Oracle Recovery Manager (RMAN), a command
-
line and Enterprise Manager
-
based tool, is the
Oracle
-
preferred method
for efficiently backing up and recovering an
Oracle database
. RMAN is designed to work intimately with the server,
providing block
-
level corrup
tion detection during backup and restore. RMAN optimizes performance and space
consumption during backup with file multiplexing and backup
-
set compression, and integrates with Oracle Secure
Backup and third
-
party media
-
management products for tape backup.

RMAN takes care of all underlying database procedures before and after backup or restore, removing dependency on OS
and SQL*Plus scripts. It provides a common interface for backup tasks across different host operating
-
systems, and
offers features not avail
able through user
-
managed methods, such as parallelization of backup/recovery data streams,
backup
-
files retention policy, and detailed history of all backups.


Confidential


for internal use only


KFS, KMM & OOI Operations Guide

System





Security and Access

Responsibility: The Application Team (Kuali
Finance Technical Development Team) works in conjunction with the
DBA to determine application security requirements.

Addition and deletion of users and the granting of privileges ultimately governs data security, so this is maintained by
the DBA. Applica
tion IDs for application users must employ role
-
based security to prevent users from altering session
parameters which can have an adverse impact on server resources.

Database Security

Tasks



Keep passwords secure and safe,
establish expiration/change policy



Strict control on all production authorizations and access levels



Periodic Security Audits



Disable remote login from root



Security for DB users oper, sys and dba



Security for R/3 users SID
ADM and ORASID



Access control thr
ough WPA



Separation of schema ID from application ID



Database and external authentication methods


Data Protection and Encryption

The Kuali Financial System source distribution includes a
.properties

file utility to allow for the automated
encryption of va
rious database fields by executing an Ant target against the main build.xml that causes a post
-
load
-
encrypt batch to be run.


For more information, see the
Database
s

topic in System Security and Accounts Management in this document.

Sensitive Data

Sensitive data is protected by different means depending on the syst
em. The database server and tables themselves are
protected by a means of access security restriction, while each application has its own protection methods that employ
built
-
in identity management.

Encryption

The entire database (tablespaces) is encrypte
d.

Secured Sockets Layer (SSL) Traffic to Database servers (ODBC/JDBC) from outside the data center.

Oracle 11G

All Data is encrypted at rest

Confidential


for internal use only


28



Sys瑥m

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e

Application Tier

JBoss

JBoss is a java application server by the vendor Red Hat that is used for port configuration and deployment of the KFS,
KMM and OOI applications at MSU.

Instructions for how to install and configure JBoss based on customizations and settings that are uni
que to EBS systems
are maintained in a separate document (referenced below) and include:



JDK Installation (prerequisite)



JBOSS Installation



Application Build



Server Tuning



For complete information, see the ‘JBoss
J
installation’ document on the EBSP Share
po楮琠wik椠i琠t_卐 㸠q敡ms 㸠
q散hn楣慬i㸠䑯捵m敮ti楢r慲y 㸠䙩can捥 㸠䑯捵men瑡t楯n [ 䭵慬椠䙩nan捩慬cpys瑥m 㸠g_体l
J
䵩gr慴楯n
E
h瑴ts㨯Wsh慲数o楮琮tbspKmsuKedu⽔Lq散hn楣慬⽄icum敮t┲Mi楢r慲y⽆Lnan捥⽄L捵men瑡t楯n⽋u慬椥aM䙩n慮c楡氥
OM卹s瑥m⽊_体l
J
䵩jr慴楯n⽊_oss
J
ins瑡t污瑩lnKdo捸



Production Application Servers


Table
12

EBS Finance Server Environment Details

Environment
Name

Host
Address

URL

Database Server

UC4 Client

FINPRD2

EBSPRD100
A4

https://finprd2.ebsp.msu.edu

EBSPRD100D1

220

PRD File
Store

EBSPRD965
F1




FINPRD
-
Node1

EBSPRD100
A1

https://fin.ebsp.msu.edu

EBSPRD100D1

100

FINPRD
-
Node2

EBSPRD100
A2




FINPRD
-
Node3

EBSPRD100
A3




FINQACI1

ebsqa101a

https://finci1.qual.ebsp.msu.edu

SERVICE_NAME =
FINQAFIX.EBSP.MSU.EDU

200

FINQACI2

ebsqa101a

https://finci2.qual.ebsp.msu.edu

SERVICE_NAME =
FINQAFIX.EBSP.MSU.EDU

200

FINQA
-
Node1

ebsqa100a1

https://fin.qual.ebsp.msu.edu

SERVICE_NAME =
FINQUAL.EBSP.MSU.EDU

200

FINQA
-
Node2

ebsqa100a2

https://fin.qual.ebsp.msu.edu

SERVICE_NAME =
FINQUAL.EBSP.MSU.EDU


FINTST

ebstst100a

https://fintst.ebsp.msu.edu

HOST = ebstst100d.ais.msu.edu

300

FINDEV

ebsdev100a

https://findev.ebsp.msu.edu

HOST = ebsdev100d.ais.msu.edu

400

Confidential


for internal use only


KFS, KMM & OOI Operations Guide

System





Environment
Name

Host
Address

URL

Database Server

UC4 Client

KMMTST

ebstst120a



300

QA FILE
STORE

ebsqa965f1




TRANSPOR
T (DEV)

transport.dev




TRANSPOR
T

transport
















Production Application Server Configuration


Table
13

Production Application Server Configuration

Configuration Option

Settings

Number

of System


3

Number

of CPU's in Each

4

Memory (GB) in Each


32

JAVA OPTIONS in
each

-
Xms28672m

-
Xmx28672m

-
XX:MaxPermSize=2048m

Web Server

maxThreads=400

connectionTimeout=45,000

sessionTimeout=30m

DB Connection per Server

maxPoolSize=300

minPoolSize=25

transactionTimeout=1800

Kuali Rice

session.document.cache.size = 1000

ksb:
threadPool.size=20

transaction.timeout=100000

PB broker pool: maxActive=500







Application Web Server Procedures

Startup

This procedure

Confidential


for internal use only


30



S
ys瑥m

䭆匬K䭍M…⁏ 䤠O灥牡瑩潮s⁇畩 e


To
startup the web server
:

1.


2.


3.


4.


5.


6.


7.


8.


9.


10.


11.


12.



End of activity.


Shutdown