cupm tac overview-architecture

26
Cisco Unified Provisioning Manager Release 1.0

Upload: shobhit-sinha

Post on 02-Jul-2015

46 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: CUPM TAC Overview-Architecture

Cisco UnifiedProvisioning ManagerRelease 1.0

Page 2: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 2

1. Product Overview & System Architecture

2. Installation

3. Call Processor Support

4. Unified Message Processor Support

5. Domain & Service Area

6. Subscriber Management

7. Order Management

8. Provisioning Attributes

9. Configuration Templates

10. Advanced Setup

11. System Administration

Course Flow

Page 3: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 3

Product Overview & System Architecture

Page 4: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 4

OverviewSingle view of subscribers and their services

Simplified management of subscribers, services, and Cisco Unified resources Day 1 – template deployments Day 2 – delegate MACDs

Single provisioning interface to Cisco Unified systems

Policy-based, business oriented

With the speed and accuracy of automation CCM, CCME

Unity, CUE, UC

Page 5: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 5

Features - Multi-Dimensional Policy

Domains Defines groupings of

subscribers for delegation purposes

Service Areas Defines how to map to the

devices and applications in the voice network

Subscriber Types Defines policy related to

type of Subscribers in the organization

Service Areas

Subscriber Types

Domains

Page 6: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 6

Features – Day 1 & Day 2

• Day 1 Template based Infrastructure provisioning

– Define configuration template w/ user defined keyword

Batch processing of total ‘services’ for subscribers

• Day 2 Delegation of MACD functions on a Domain Level

Provisioning Policy settable at several levels

Page 7: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 7

Features – Authorization roles

• Predefined Authorization User Role determines level of access within CUPM

•Two types of Authorization User Roles Global roles: shared on all domains

Domain specific roles: Users with these roles can only perform authorized tasks within their assigned domain

• Access is accumulated if a user has multiple roles

Page 8: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 8

Features – Authorization Roles(Contd.)

User Type User Roles Rights

Global Administration

Maintenance

Full rights except Data Maintenance

Data Maintenance: Configure system cleanup activities

Domain Specific

Policy

Ordering

Advanced Ordering

Advanced Assignment

Approval

Assignment

Shipping

Receiving

Manage phone inventory, manage subscriber types, and set phone button templates

Subscriber management and product ordering

All Ordering privileges plus can set provisioning attributes at time of order

All Ordering privileges plus can assign MAC at time of order

Approves or rejects provisioning requests

Assigns phone (MAC address) to an order

Ensures equipment sent before order processing continues

Ensures equipment received before order processing continues

Page 9: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 9

Features – Role based access

• Administrator role Manages Cisco Unified systems provisioned by CUPM

Partitions domains and service areas based on department or location

Sets up domain level policies including

– Provisioning attributes

– Rules

System administration tasks like managing system users and license

Page 10: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 10

Features – Role based access(Contd.)

•Domain Policy role Manages Policy for a domain

– Subscriber types and products that can be ordered against them

– Phone button templates

Manages phone inventory

• Ordering role Manages subscribers and their services for a single domain

Doesn’t need knowledge of Cisco Unified systems

Page 11: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 11

ArchitectureMulti-Layer/Tier View

Data TierBusiness Logic TierPresentation Tier

Thin Client(HTML/XHTML/XML)

HTTP

Web Server

Postgres

RDBMS

CUPMNICEEngine

CUPMOn JBOSS

J2EE App

Cisco Call Manager Cisco UnityCisco Unity Connection

CCMECUE

J2SE App

AXLSOAP

JDBCCLI over Telnet

SSH

Appache

Currently run on the same server

Currently run on the same server

JDBCRMI

Can be run on a different server

Can be run on a different server

Tools and Technologies: • GUI: based on XML and XSL, XSP • J2EE: Java Enterprise Edition including EJB, Servlet• J2SE: Java Standard Edition• Database: DDL, SQL over JDBC

Tools and Technologies: • GUI: based on XML and XSL, XSP • J2EE: Java Enterprise Edition including EJB, Servlet• J2SE: Java Standard Edition• Database: DDL, SQL over JDBC

Page 12: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 12

ArchitectureComponent View

Common Facilities and API

ServiceActivator

Client

JBOSS J2EE App Server

J2SE

Service ActivatorNICE Engine

InventoryManager

ProcessManager

OrderManager

Common GUI Layer (Cocoon and wizards)

Cisco Call Manager

Cisco UnityCisco Unity Connection

CCMECUE

Page 13: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 13

ArchitectureComponent Interaction View

CUPM based on SEP

Order Manager

CUPM Order Wizard

User

Inventory Manager

CUPM Product Model

CUPM Object Model

Process Manager

CUPM Workflow

Service Activator (NICE)

CUPM Service Action

Subscriber, Order, Subscriber’s

Service

Cisco Unity

CCMECUE

Cisco Unity Connection

Cisco Call Manager

Page 14: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 14

Architecture CP and UMP Device Setup System Flow

Wizard(GUI)

InventoryManager

Data Access& Persistence

Page 15: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 15

Architecture CP and UMP Synchronization System Flow

Wizard(GUI)

InventoryManager

Data Access& Persistence

NICE Engine

Data Access& Persistence

Sync request

CMECisco Unity Connection (SQL) Server

Cisco Unity (SQL) Server

JDBC

CLI over Telnet

SSH

JDBC

Synchronization is done in two steps:

• Infrastructure Sync• Subscriber Sync

Synchronization is done in two steps:

• Infrastructure Sync• Subscriber Sync

Call Manager (publisher)

AXL/SOAP

CUE

Page 16: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 16

Architecture Overall Order Provisioning System Flow

Order Manager(GUI, Wizard)

InventoryManager

Data Access& Persistence

NICE EngineData Access& Persistence

Activation/Deactivation

CUE/CMECisco Unity Connection (SQL) Server

Cisco Unity (SQL) Server

JDBC

CLI over Telnet, SSH

JDBC

ProcessManager

(Workflow)

Order Submit

Activation Request, and persistence

Order Processing System Flow for products:

• Phone• Line • Voicemail• Email• Unified Messaging

Order Processing System Flow for products:

• Phone• Line • Voicemail• Email• Unified Messaging

Call Manager (publisher)

AXL/SOAP

Page 17: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 17

Device Support

Call Processor Unified Message Processor

CM 4.0(2), 4.1(3), 4.2(1), 5.0(4)

(AXL, SOAP based interface)

Unity 4.0, 4.1, 4.2

(JDBC interface to Unity database)

CME 3.3, 3.4, 4.0

(CLI over Telnet, SSH )

UC 1.1.1

(JDBC interface to UC database)

CUE 2.1, 2.2. 2.3

(CLI over Telnet, SSH)

Page 18: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 18

Authorization User Roles

Page 19: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 19

Authorization User RolesOverview

• Authorization User Role determines level of access within CUPM

• Two types of Authorization User Roles Global roles: shared on all domains Domain specific roles: Users with these roles can only perform

authorized tasks within their assigned domain

• Access is accumulated if a user has multiple roles

• User can not delete, change or add Authorization roles; user can delete, change and add Subscriber roles.

Page 20: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 20

Role-based Access – Authorization Roles

User Type User Roles Rights

Global Administration

Maintenance

Full rights except Data Maintenance

Data Maintenance:

Configure system cleanup activities

Domain Specific

Policy

Ordering

Advanced Ordering

Advanced Assignment

Approval

Assignment

Shipping

Receiving

Manage phone inventory, manage subscriber types, and set phone button templates

Subscriber management and product ordering

All Ordering privileges plus can set provisioning attributes at time of order

All Ordering privileges plus can assign MAC at time of order

Approves or rejects provisioning requests

Assigns phone (MAC address) to an order

Ensures equipment sent before order processing continues

Ensures equipment received before order processing continues

Page 21: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 21

Domain Level Roles

Copied Domain roles

All domain roles are duplicated for each domain

Page 22: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 22

System Debugging

Page 23: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 23

Log File Locations

• Two main logs files in <Install Dir>\sep\logs sep.log (application server log ) nice.01.log (CUPM Nice Engine logs)

• Installation logs: <Install Dir>\install.log

• Cocoon Log: <Install Dir>\sep\deploy\dfc.ear\dfc.war\WEB-INF\logs

• Web server (Apache) logs: <Install Dir>\httpd\logs

• Application Server (JBoss) logs: <Install Dir>\jboss-4.0.3SP1\server\cupm\log

• Database (Postgres) logs: <Install Dir>\pgsql\data\pg_log

• CUPM administrator access is needed in most debugging

Page 24: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 24

Changing Log Levels and Max Size

To change log level for App server and Nice engine Change dfc.log.level=<level> in <Install Dir>\sep\dfc.properties

Restart cupm JBossService and NiceService

To change the log level for NICE only Add dfc.log.level: <level> in file <Install Dir>\sep\nice.properties

Save the file and restart cupm NiceService

To change the log max size of log file before it rotates, Update property dfc.log.maxsize=<size>

Save the file and restart cupm JBossService

Page 25: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 25

AXL Message Logging

Properties to output Call Manager AXL SOAP requests/responses to log dfc.ipt.axl.soap.output.request.enabled: <N/Y>

dfc.ipt.axl.soap.output.response.enabled: <N/Y>

Change these properties in the file <Install Dir>\sep\ipt.properties, save file, and restart CUPM NiceService

Page 26: CUPM TAC Overview-Architecture

© 2006 Cisco Systems, Inc. All rights reserved. 26