Beruflich Dokumente
Kultur Dokumente
Purpose: This document provides an overview of features and enhancements included in CRM 8.0. It is intended solely to help you assess the business benefits of upgrading to CRM 8.0. Disclaimer: This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.
Agenda
Business Needs Functional Overview Technical Architecture Demonstration Troubleshooting Limitations Q&A
Agenda
Business Needs Functional Overview Technical Architecture Demonstration Troubleshooting Limitations Q&A
Agenda
Business Needs Functional Overview Technical Architecture Demonstration Troubleshooting Limitations Q&A
Scale of Problem
Deployments not only to Production Most deployments are to non-production environments Development, Test, Training, etc Often daily drops between development systems Typically multiple Production drops each year Each drop can take hours to deploy Often hundreds or even thousands of drops per year in total
9 Copyright 2006, Oracle. All rights reserved.
Whats Needed?
Automated deployment Re-usable deployment Decreased deployment time Decreased down-time Greater insight to whats being deployed
10
Agenda
Business Needs Functional Overview Technical Architecture Demonstration Troubleshooting Limitations Q&A
11
Provides consistent framework to migrate just about all types of Siebel customizations Changes can be bundled into re-useable packages Can deploy to multiple servers with a single command
12
Initially released in Siebel 7.7 Enhanced in Siebel 7.8 Additional data types (objects) supported Major Enhancements in Siebel 8.0 Packaging Automation Many new data types Backup/restore Activation Development will continue through later Siebel releases
13 Copyright 2006, Oracle. All rights reserved.
7.7
Functions Import Export Objects* Price Lists Custom Products
7.8
Functions Export Import Objects*
8.0
Functions Enhanced Export Packaging Automated Deployment Activation, Backup, Restore Smart Scripts WF Policies Proposal Templates SRF Web templates Workflow Processes Applets Views
Repository Objects
14
Functional Overview
Package Deploy Activate Recover
Bundle objects into single package One package can contain multiple different data types Can include objects based on Repository (i.e. BC)
Exported through Siebel Tools Exported as SIF file
Deployment/Activation
Automated deployment and activation Activation-only support (e.g., for objects deployed via dev2prod) Staged deployment by category / server / step Deployment orchestration stop/restart Deployment status and history Command line interface for deployment Limited high-availability deployment support (online deployment/activation, staged server deployment)* Validation for deployment registry, profile, package and target enterprise
*Limitations apply, some downtime expected
16
Deploy
Activate
Recover
Framework-Generic
Detailed logging for deployment operations Extensible and meta-data driven deployment framework Integration CLI interface for third-party change management tools Support for non-Siebel App Servers as deployment targets (e.g., Report Server) Support for multiple Siebel Enterprises from one ADM installation
17 Copyright 2006, Oracle. All rights reserved.
Deploy
Compile SRF
Sync Schema
Activate
Target Enterprise
Startup
Deploy
Activate
DB Records
18
Import
Sync Schema
Activate WF & Task
Test Enterprise
Startup
Deploy
Activate
19
Agenda
Business Needs Functional Overview Technical Architecture Demonstration Troubleshooting Limitations Q&A
20
Deploy / Activate package Verify deployment (perform any recovery actions) Acknowledge, to terminate session
Automated process
21
Deployment Steps
Deployment
valent load create validate backup copy activate * manual step optional
22 Copyright 2006, Oracle. All rights reserved.
Recovery
delete acknowledge Verify* restore_activate
restore_copy
restore_session
Deployment Diagram
Source environment
Orchestration environment
Deployment Package
Management Server
Target environment
Siebel enterprise
23
Client Environment
RMI JMX Remote (OEM) Target Profile (XML) ADM Registry (XML) Local database JMX Remote (OEM)
Management Server
Deployment Deployment Package Package Management Functions (includes ADM modules)
RMI
Orchestration Environment
JMX Agent (MBeans)
Siebel Server
Source Environment
Target Environment
24
Technologies
Agent - JMX
The Java Management Extensions (JMX) technology is an open technology for management and monitoring that can be deployed wherever management and monitoring are needed. By design, this standard is suitable for adapting legacy systems, implementing new management and monitoring solutions and plugging into those of the future.
Deploy to SiebSrvr
Notify Status
Management Agent
ADM OM
ADM Processor
Activate Siebel Server Note: Separate execution for Deployment and Activation
26
Package
Copy to SiebSrvr
Notify Status
Management Agent
27
Deployment Architecture
28
Agenda
Business Needs Functional Overview Technical Architecture Demonstration Troubleshooting Limitations Q&A
29
Agenda
Business Needs Functional Overview Technical Architecture Demonstration Troubleshooting Limitations Q&A
30
31
MgmtServer INFO 2006-11-13 04:27:38 new connection to [ name=SDCHS22N002_1199 url=service:jmx:rmi://SDCHS22N002/jndi/rmi://SDCHS22N002:1199/jmx/siebe l/agent state=online ]
32
Ignore messages Agent not online or name is invalid as long as there is a final online message Ignore message AlertManager already started with a long stack trace!
33
34
Session Number
35
<PackageName>_<Session_Number>.log
Application Server, StatusDetail=This notification is for performance purpose only, not for status reporting!, Session Number=510, Status=MIGRATION_RUNNING, Server Host Name=sdchs22n002}'. Session-510 INFO 2006-11-13 04:55:55Successfully updated unit status in deployment group 'File Group - Reports - Application Server'. Session-510 INFO 2006-11-13 04:55:56Submitting unit 'database/42-5FNZY_Responsibility.xml' to agent 'SDCHS22N002_1199' succeeded. Session-510 INFO 2006-11-13 04:55:56Start processing status message: '{Group Name=File Group Reports - Application Server, StatusDetail=This notification is for performance purpose only, not for status reporting!, Session Number=510, Status=MIGRATION_COMPLETE, Server Host Name=sdchs22n002}'.
36
2006-11-13 04:55:52 -0700 FileMBean INFO 2006-11-13 04:55:53 Copying from source file 'D:\20302MS\Packages\sample\file\AppServer\reports\ENU\sample.rox'. FileMBean INFO 2006-11-13 04:55:53 Backing up destination file 'D:\20302\ses\siebsrvr\REPORTS\ENU\sample.rox'. FileMBean INFO 2006-11-13 04:55:53 Deploying to destination file 'D:\20302\ses\siebsrvr\REPORTS\ENU\sample.rox'. FileMBean INFO 2006-11-13 04:55:54 Results from action 'DEPLOY_COPY':file/AppServer/reports/ENU/sample.rox DEPLOYMENT_COMPLETE
37
2006-11-13 04:55:53 -0700 DataMBean INFO 2006-11-13 04:55:53 Submitting deployment request starts, parameters are: Category=Database Package Name=sample Group Name=Database Group Unit Name=database/42-5FNZY_Responsibility.xml Session Number=510 Execution Id=1 Enterprise Profile Parameters: DestinationRoot=d:\20302\ses\siebsrvr PerformDeployment=Yes PerformBackup=Yes PackageLocation=D:\20302MS\Packages ServerConnectString=siebel://SDCHS22N002:3320/siebel/ADMObjMgr_enu PerformValidation=Yes Password=****** DegParallelism=1 User Name=SADMIN WFPolicyActSrvr=SDCHS22N002_1199 PerformActivation=No StopOnError=Yes ADMBackupDir=\\SDCHS22N002\upload DataMBean INFO 2006-11-13 04:55:56 Output from Siebel server are: Status=NOT_STARTED reqId=88-25C14 DataMBean INFO 2006-11-13 04:55:56 Deployment request successfully submitted.
38
39
2021 2006-11-13 05:30:14 2006-11-13 05:30:14 -0700 000001a7 001 003f 0001 09 ADMProc 9437198 304 5512 d:\20302\ses\siebsrvr\log\ADMProc_0009_9437198.log 8.0 SIA [20302] ENU ObjMgrLog Error 1 0000000845580158:0 2006-11-13 05:30:14 (eaiobjinst.cpp (2208)) SBL-EAI-13011: Field 'Name' in the integration component 'Responsibility' contains value 'ADM Sample Responsibility 1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx', which is longer than allowed length of 50 characters. ObjMgrLog Error 1 0000000845580158:0 2006-11-13 05:30:14 (adptutils.cpp (1222)) SBL-EAI-04397: No user key can be used for the Integration Component instance 'Responsibility'. EAISiebAdpt EAISiebAdptErr 1 0000000845580158:0 2006-11-13 05:30:14 [0] No user key can be used for the Integration Component instance 'Responsibility'.(SBL-EAI-04397) (IDS_ERR_EAI_SA_NO_USERKEY) ObjMgrLog Error 1 0000000845580158:0 2006-11-13 05:30:14 (stepexec.cpp (1540)) SBL-BPR-00162: Error invoking service 'UDA Service', method 'Sync Transaction Property Set' at step 'Import Data'. ADM Event ADM Event UDAGenericError UDAGenericError 1 1 0000000845580158:0 0000000845580158:0 2006-11-13 05:30:14 2006-11-13 05:30:14 Failed to deploy eai data. Deployment failed.
40
Agenda
Business Needs Functional Overview Technical Architecture Demonstration Troubleshooting Limitations Q&A
41
ADM Limitations
Data Volumes (database) ADM is not designed as a volume data transfer tool ADM is based on the EAI architecture Each data type is loaded as a single EAI transaction Subject to the normal performance limits Data Volumes (repository) Same limitations as database data types DEV2PROD should be used where extensive repository changes have been made DEV2PROD runs outside ADM control
42
ADM Limitations
Restore Will replace current image with image at time of backup Will lose any changes made since backup Should only be used prior to going live with new deployment
43
ADM Limitations
44
ADM Limitations
Downtime Not a zero-downtime solution Any repository changes require server restart (for SRF) Some other changes require user logout System Impact shows the impact of deploying specific data types
Information only field, cant be changed
Defined in ADM Registry for each data type Accessible through package definition
45 Copyright 2006, Oracle. All rights reserved.
System Impact
46
Agenda
Business Needs Functional Overview Technical Architecture Demonstration Troubleshooting Limitations Q&A
47
Thank You
Thank You