2

D48291GC10 ORACLE Utilities Customer Care &

Billing Configuration Ed 1

Module 02 Common Concepts

Copyright 2008, Oracle. All rights reserved.

Objectives

After completing this Architecture module, you should be

able to:
Understand the role of the CC&B Administration
account.
Understand the concept of an "environment"
Understand the concept of attaching to an
environment.
Understand the directory structure of an environment.
Understand the common environment variables used in
CC&B.
Understand the basic URL's used for CC&B.

2-2

Copyright 2008, Oracle. All rights reserved.

CC&B Administrator Account

Default CC&B administrator account: cissys
The administrator account is needed to install the product.
Responsibilities:
Owner of structure
Owner of configuration
Start, shutdown and monitor product.
This userid is NOT responsible for:
Does not run CC&B background processes.
Does not access online product.
Treat the account as you would the root account.

2-3

Copyright 2008, Oracle. All rights reserved.

Implementation Tip: Multiple Owners

It is possible to assign an owner per copy of CC&B
Advantages:
Delegation of responsibility for non-production.
Segregation of resources.
Disadvantages:
You must login using that user to manage that copy of
CC&B.
How can this be done?
User/directories must be setup with the correct
permissions.
Access to /etc/cistab must be allowed
Make sure user installs that particular copy of CC&B.

2-4

Copyright 2008, Oracle. All rights reserved.

What is an CC&B environment?

A CC&B environment is
defined as a distinct copy
of CC&Bs database and
Web Application Server
A copy of the base
product
A copy of the
customizations
installed alongside the
base.
Remember the CC&B
Architecture
2-5

Web Application Server

Business Application Server

Database Server

Copyright 2008, Oracle. All rights reserved.

Implementation Tip: Environment Management

Choose an appropriate name/identifier for it.

Assign an environment owner.
Agree de-installation date for environment.
Agree availability of environment (24x7, business hours,
adhoc etc).
Agree maintenance windows for environment.
Agree backup regime for environment.
Agree security procedures for environment.
Record this all somewhere

2-6

Copyright 2008, Oracle. All rights reserved.

Environment Retention

Each environment should have a de-installation date (even

if the value is perpetual).
Negotiate and record the date in your documentation.
Setting dates can force thought on environment
rationalization.
This is important.

2-7

Copyright 2008, Oracle. All rights reserved.

Attaching to an environment

This sets the environment variables necessary for execution of

utilities.
Change to the environments bin directory.
Use the following command to attach to the environment.
splenviron.sh
e (SPLVERSION)
<environment>
[-c <command>] [-q] [-v] [-h]
Version
................
: V2.1.x
Database Type ............... (SPLDB) : oracle
splenviron.cmd e <environment> [-c <command>] [q] [-v] [-h]
ORACLE_SID ............. (ORACLE_SID) : SPLDEMO
NLS_LANG ................. (NLS_LANG) : AMERICAN_AMERICA.WE8ISO8859P15
Environment Name ....... (SPLENVIRON) : CCBTRAIN
Environment Code Directory (SPLEBASE) : /spl/CCBTRAIN
App Output Dir - Logs ... (SPLOUTPUT) : /spl/sploutput/CCBTRAIN
Build Directory .......... (SPLBUILD) : /spl/CCBTRAIN/cobol/build
Runtime Directory .......... (SPLRUN) : /spl/CCBTRAIN/runtime
Cobol Copy Path ......... (SPLCOBCPY) : /spl/CCBTRAIN/cobol/source/cm;/spl/CCBTRAIN/
services;/spl/CCBTRAIN/cobol/source

This must be performed before any administration commands can be performed

2-8

Copyright 2008, Oracle. All rights reserved.

Directory Structure - Environment

CC&B mount point (usually /spl or <drive>:\spl)

<SPLDIR>

$SPLEBASE or %SPLEBASE%

<environment name>

Binaries and utility scripts

bin

COBOL Build directories

cobol

Configuration files

etc
conf
metadata
SF

Meta Data build directory (compilation only)

Single Fix build directory (compilation only)
Active logs

logs
system
product
runtime
scripts
services
splapp
2-9

Web Application configuration files

System startup/shutdown logs

Other product subdirectory (Perl, Ant, Tomcat)
Business object runtimes
Custom scripts for batch jobs
Source for Services/Plugins
Web Application Server files

Copyright 2008, Oracle. All rights reserved.

Directory Structure Output

<SPLOUTPUT>

Application output mount point (e.g. /spl/sploutput or <drive>:\spl\sploutput)

<environment name>

$SPLOUTPUT

Directory for all application and log files in this environment

2 - 10

Copyright 2008, Oracle. All rights reserved.

Implementation Tip: Multiple Environments

On non-production you will

have multiple environments.
All separated by directories.

/spl
TEST1
TEST2
TEST3
sploutput
TEST1
TEST2
TEST3

2 - 11

Copyright 2008, Oracle. All rights reserved.

Common Environment variables

2 - 12

Variable

Usage

SPLADMIN

CC&B Administrator account for this environment

SPLADMINGROUP

CC&B Administrator group for this environment

SPLBUILD

COBOL Build directory (used for compilation)

SPLCOBCPY

COBOL Copy book path (used for compilation)

SPLDB

Database type used for this environment

SPLEBASE

Root location of the CC&B software

SPLENVIRON

Name of environment used for installation

SPLOUTPUT

Root location of CC&B output files

SPLRUN

CC&B Runtime

SPLSOURCE

COBOL source (used for compilation)

SPLSYSTEMLOGS

Location of CC&B Log files

SPLVERSION

Framework Version

SPLVERSIONFILE

Location of Application Framework Version file

SPLWAS

Web Application Server type

Copyright 2008, Oracle. All rights reserved.

Implementation Tip: Adding your own settings

It is possible to add your own environment settings

when splenviron.sh or splenviron.cmd is run.
Locally:
Create cmenv.sh or cmenv.cmd and place it in the
scripts directory under SPLEBASE.
Globally:
Set the CMENV environment variable prior to
running splenviron to point to a global script.

2 - 13

Copyright 2008, Oracle. All rights reserved.

Important URLs

The following URLs are important to remember:

CC&B main URL
http://<machine>:<port>/SPLApp/cis.jsp

CC&B with debug facilities

http://<machine>:<port>/SPLApp/cis.jsp?debug=true

Where:
<machine> - Web Application Server Machine
<port> - Port number allocated to an environment for Web
application Server.

2 - 14

Copyright 2008, Oracle. All rights reserved.

Administration of the cache

2 - 15

URL

Usage

flushAll.jsp

Clears the whole cache

flushDropdownCache.jsp

Clears ALL the Drop Down data from cache

flushDropDownField.jsp

Clears specific Drop Down data (needs Field

name)

flushFieldAndFKMetaData.jsp

Clears Literals and FK relationships from

cache

flushMenu.jsp

Clears Menu items from cache

flushMessageCatalog.jsp

Clears Message texts from cache

flushMessaging.jsp

Clears XAI Sender information from cache

flushNavigationInfo.jsp

Clears Navigation Keys from cache

flushPortalMetaInfo.jsp

Clears Portal information from cache

flushSystemLoginInfo.jsp

Clears security information from cache

flushUI_XSLs.jsp

Clears style sheets from cache

Copyright 2008, Oracle. All rights reserved.

Summary

In this Common Concepts module, you should have

learned how to:
Understand the role of the CC&B Administration
account.
Understand the concept of an "environment"
Understand the concept of attaching to an
environment.
Understand the directory structure of an environment.
Understand the common environment variables used in
CC&B.
Understand the basic URL's used for CC&B.

2 - 16

Copyright 2008, Oracle. All rights reserved.

Any Questions?

2 - 17

Q&
A
Copyright 2008, Oracle. All rights reserved.

2 - 18

Copyright 2008, Oracle. All rights reserved.

2 - 19

Copyright 2008, Oracle. All rights reserved.