weblearning developer demo courses train - ibm training · disclose these training materials are...

WebLearning Developer Demo Courses

Hands-on Training Guide

Copyright © 2007, 2008, Harley-Hayford Courseware. All rights reserved

COPYRIGHT & TRADEMARKS Copyright © 2007, 2008, Harley-Hayford Courseware. All rights reserved.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Harley-Hayford license agreement and/or the applicable U.S. Government contract. Harley-Hayford®, WebLearning®, BusinessObjects, BEA, WebLogic, Cognos, Informatica, SAP, Oracle, JD Edwards, PeopleSoft, Siebel, Hyperion, MicroStrategy, IBM and Microsoft are registered trademarks. Other names may be trademarks of their respective owners All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.

Author

Harley-Hayford Courseware

Technical Contributors and Reviewers Yosi Wilson, R&D Department.

Preface

Profile

Before You Begin This Course

Before you begin this course, you should have the following qualifications:

• Some knowledge of Databases

• Working experience with or SQL

Prerequisites

• None.

How This Course Is Organised

The WebLearning Demonstration ILT course provides step-by-step instructions on how to perform a variety of tasks for activities based on real-life work scenarios. The WebLearning hands-on series reduces the time spent investigating what steps are required to perform a task. Because the step-by-step solutions are built for practical real world situations, not only is knowledge gained through valuable hands-on experience, but also the solutions presented may then be used as the foundation for production implementation, dramatically reducing time to deployment..


Related Publications

WebLearning courseware Publications Title Part Number

Hands on Oracle Peoplesoft Enterprise Portal 9.0 Fundamentals

Hands-on Oracle EBS R12 Human Resource Management

Hands-on Peoplesoft 9.0 HCM Payroll Management

Hands-on Peoplesoft 9.0 HCM CRM HelpDesk for Human Resources

Hands-on Oracle EBS R12 HRMS Performance Management

Hands-on Oracle EBS R12 Financials General Ledger Fundamentals

Hands-on Oracle EBS R12 Financials Payables Fundamentals

Hands-on Oracle EBS R12 Financials Receivables Fundamentals

Hands-on Oracle EBS R12 Financials Purchasing Fundamentals

Hands-on Oracle EBS R12 Self-Service Human Resources

Hands-on Peoplesoft 9.0 HCM eCompensation Manager Desktop

Hands-on Oracle EBS R12 HRMS Time and Labour

Additional Publications

• Hands-on Business Objects Enterprise XI Universe Designer Fast Track

• Hands-on Business Objects Enterprise XI Desktop Intelligence Fast Track

• Hands-on Business Objects Enterprise XI Best Practices Master Class

• Hands-on Business Objects Enterprise XI EPM Fast Track

• Hands-on Business Process Management using Oracle BPA Suite

• Hands-on Oracle11g Database Administration Fast Track

• Hands-on Mastering PMP Project Management

• Hands-on Finance for non-Financial Managers Fast Track

• Hands-on Oracle11g SQL Fundamentals

• Hands-on UML 2.0 Fast Track

• Hands-on SOA Governance Master Class

• Hands-on SOA 101

• Hands-on Business Process Management 101

• Hands-on Software Testing Fast Track

• Hands-on Business Process Management using Websphere Business Modeler

• Hands-on IBM DB2 v9 Data Warehousing Fast Track

• Hands-on Oracle Business Intelligence Server Architecture and Design

• Hands-on Oracle Business Intelligence Server Administration

• Hands-on Oracle Business Intelligence Presentation Services Fundamentals

• Hands-on Oracle Business Intelligence Answers Fundamentals

• Hands-on Oracle Business Intelligence Analytics Fundamentals

• Hands-on Oracle Siebel 8.0 Fundamentals

• Hands-on Oracle Hyperion Performance Management Fast Track


Typographic Conventions

Typographic Conventions in Text Convention Element Example Bold italic Glossary term (if

there is a glossary)

The algorithm inserts the new key.

Caps and lowercase

Buttons, check boxes, triggers, windows

Click the Executable button. Select the Can’t Delete Card check box. Assign a When-Validate-Item trigger to the ORD block. Open the Master Schedule window.

Courier new, case sensitive (default is lowercase)

Code output, directory names, filenames, passwords, pathnames, URLs, user input, usernames

Code output: debug.set (‘I”, 300); Directory: bin (DOS), $FMHOME (UNIX) Filename: Locate the init.ora file. Password: User tiger as your password. Pathname: Open c:\my_docs\projects URL: Go to http://www.oracle.com User input: Enter 300 Username: Log on as scott

Initial cap Graphics labels (unless the term is a proper noun)

Customer address (but Oracle Payables)

Italic Emphasized words and phrases, titles of books and courses, variables

Do not save changes to the database. For further information, see Oracle7 Server SQL Language Reference Manual. Enter [email protected], where user_id is the name of the user.

Quotation marks

Interface elements with long names that have only initial caps; lesson and chapter titles in cross-references

Select “Include a reusable module component” and click Finish. This subject is covered in Unit II, Lesson 3, “Working with Objects.”

Uppercase SQL column names, commands, functions, schemas, table names

Use the SELECT command to view information stored in the LAST_NAME column of the EMP table.

Arrow Menu paths Select File > Save. Brackets Key names Press [Enter]. Commas Key sequences Press and release keys one at a time:

[Alternate], [F], [D] Plus signs Key combinations Press and hold these keys simultaneously:

Typographic Conventions in Code Convention Element Example Caps and lowercase

Oracle Forms triggers

When-Validate-Item

Lowercase Column names, table names

SELECT last_name FROM s_emp;

Passwords DROP USER scott IDENTIFIED BY tiger;

PL/SQL objects OG_ACTIVATE_LAYER (OG_GET_LAYER (‘prod_pie_layer’))

Lowercase italic

Syntax variables CREATE ROLE role

Uppercase SQL commands and functions

SELECT userid FROM emp;

Typographic Conventions in Application Navigation Paths

This course uses simplified navigation paths, such as the following example, to direct you through Oracle Applications.

(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve

This simplified path translates to the following:

1. (N) From the Navigator window, select Invoice then Entry then Invoice Batches Summary.

2. (M) From the menu, select Query then Find.

3. (B) Click the Approve button.

Notations:

(N) = Navigator

(M) = Menu

(T) = Tab

(B) = Button

(I) = Icon

(H) = Hyperlink

(ST) = Sub Tab


Typographical Conventions in Oracle Application Help System Paths

This course uses a “navigation path” convention to represent actions you perform to find pertinent information in the Oracle Applications Help System.

The following help navigation path, for example—

(Help) General Ledger > Journals > Enter Journals

—represents the following sequence of actions:

1. In the navigation frame of the help system window, expand the General Ledger entry.

2. Under the General Ledger entry, expand Journals.

3. Under Journals, select Enter Journals.

4. Review it.

Hands-On Training Guide WebLearning Developer Demo Courses

Copyright © 2007, 2008, Harley-Hayford Courseware. All rights reserved Page ix

Table of Contents WebLearning Developer Demo Courses....................................................................1

SOA Standards.....................................................................................................................1 Web Services Standards................................................................................................................... 4 Implementation Standards ............................................................................................................... 7

Navigating Fusion Middleware Control ..........................................................................11 Accessing FMW Control ............................................................................................................... 11 FMW Control Layout .................................................................................................................... 16 Exploring WebLogic Administration Console .............................................................................. 52

Fusion Middleware Farm..................................................................................................81 Examining a FMW Farm ............................................................................................................... 81

BPM Methodology .............................................................................................................97 BPM Governance and BPM (Project) Methodology ..................................................................... 99 BPM Methodology Use Case ...................................................................................................... 100

Exploring BAM and BPM Suite 11g Components........................................................102 Exploring BPM Studio ................................................................................................................ 103 Exploring BPM Composer........................................................................................................... 135 Exploring BAM Active Studio .................................................................................................... 149

Understanding WebLogic Clusters ................................................................................156 Creating a Cluster of Existing Servers......................................................................................... 157 Starting the Clustered Servers...................................................................................................... 184 Monitoring the Cluster................................................................................................................. 189

Oracle SQL - Working with UNION..............................................................................196 Understanding UNIONS.............................................................................................................. 196


Copyright © 2007, 2008, Harley-Hayford Courseware. All rights reserved Page 1

WebLearning Developer Demo Courses

SOA Standards SOA must be standards-based in order to achieve interoperability. Also for given Enterprise, technologies (in the form of platforms), tools, and engineering practices must adhere to selected standards. Unfortunately there are many standards and simply selecting them all is not a path to automatic success. Many standards are not yet complete, or more importantly, not yet adopted by the tools and infrastructure vendors: in this case an unsupported standard will do nothing for short term interoperability (and in fact, if it is ultimately not adopted, then it also offers no benefit in the long term). So it is important to select the right standards for any given enterprise. This leads to the question "why would standards selection vary between enterprises?". There are a number of relevant considerations when selecting standards, including the industry domain and existing methods and competencies that may already in place within an organisation. Standards may originate from various sources:

• IT industry standards (e.g. W3C XML, OASIS WS-*); • Business industry standards (e.g. HL7, …); • Enterprise standards (engineering standards).

It is important to distinguish standards from policies or regulations (such as HIPA and Sarbanes Oxley): in the case of "enterprise standards", it is important to distinguish from principles, practices, and guidelines (such as "Services must not cross domain boundaries below enterprise level") which may be less strictly defined. Once we have determined what standards may be available to a domain another consideration is which standards are relevant to the architectural style of the organization's engineering practices. The next section outlines the key standards for SOA while the section that follows it deals with the different architectural styles that have a bearing on standards selection. SOA Standards This section introduces standards relevant to SOA, including Service design, implementation, deployment, and management; it does not cover general software engineering and IT standards, nor does it include industry specific standards. The primary benefits of adopting standards are interoperability, technology independence, and rapid integration. By avoiding proprietary protocols, formats, etc. and adopting standards-based strategies the enterprise can avoid vendor lock-in, simplify exchange of information between applications and partners, and take advantage of readily available development skills. Standards are available in many forms and for a variety of different purposes. Core SOA related standards recommended and described in this document are:

• Java API for XML Web Services (JAX-WS) • Business Process Execution Language (BPEL) • A collection of Web Services standards (WS-*)


Page 2 Copyright © 2007, 2008, Harley-Hayford Courseware. All rights reserved

• Simple Object Access Protocol (SOAP) with attachments and Message Transmission Optimization Mechanism (MTOM) (implemented as SOAP with Attachments API for Java (SAAJ)

• HyperText Transfer Protocol (HTTP) • Universal Description, Discovery and Integration (UDDI) • Service Component Architecture (SCA) • Apache's Web Service Invocation Framework (WSIF) • Web Service Interoperability (WS-I) • Some examples of industry specific standards that may be relevant to SOA, but

excluded from this document for brevity, include • HL7 (XML messaging standard for Healthcare for the exchange, integration, sharing

and retrieval of electronic health information) • HRXML (a library of XML schemas developed by the HR-XML Consortium, Inc. to

support a variety of business processes related to human resource management) • Telecoms IMS (IP Multimedia Subsystem, 3GPP Technical Specification TS 22.228)

architectural strategy and standards for decoupling of the technical and organizational constraints of former telecommunications strategies.

• OASIS ebXML work, such as, CPPA (Collaboration Protocol Profile and Agreement) which describes how trading partners engage in electronic business collaborations through the exchange of electronic messages

Standards for SOA can be categorized into four areas of concern:

1. Orchestration and composition; 2. Description and discovery; 3. Messaging; 4. Implementation.

These categories of standards are shown in the diagram along with some of their associated standards abbreviations.

Figure - Categorisation of SOA for standards The categories and their core standards shown in Figure are described in following sections. Orchestration and Composition The Enterprise Service Bus (ESB) is commonly thought of as the primary platform for Service orchestration, however the ESB has no standard definition and although it typically



supports many standards internally the ESB platforms are proprietary. The primary standards for Service orchestration and composition are listed below. WS-BPEL (formerly known as BPEL4WS and commonly abbreviated to BPEL)

• BPEL is a common standard for assembly of processes (business & system) based on Services and defined using WSDL. A BPEL orchestration might contain a single activity, simply invoking a Service, or many activities to accomplish long running tasks involving complex transformations, joins, loops, with synchronous and/or asynchronous processing.

• BPEL infrastructure should accommodate (in addition to current BPEL specifications implementation) manual task workflow and may support alternative Service exposure (besides WSDL with its implicit SOAP/HTTP binding), such as, Apache's Web Service Invocation Framework (WSIF)

Java Business Integration (JBI) (JSR-208)

• Normalized message routing for standardized Service assembly ensuring loose coupling between bindings and Services.

• May be used to deploy Service assemblies on top of BPEL & ESB infrastructure.

Service Component Architecture (SCA)

• A programming model for Service based application development. • Defines Service component and assembly models (unlike WSDL) • Enables specification of dependencies on other Services and policies, such as,

transaction, security, reliable messaging, etc. • Supports a number of data connectivity standards including, JDBC, Java Persistence

API (JPA), Service Data Objects (SDO)

BPEL is the primary focus here for orchestration and composition. It is an OASIS standard for a Web Services orchestration language: it provides property-based message correlation, XML & WSDL typed variables, XPath for expressions & queries, structured programming constructs if-then-else, while, sequence (ordered execution) and flow (parallel execution), fault- compensation- and event-handlers. BPEL is best suited to long-running (business) processes, providing correlation between running processes, orchestration of Web Services, and composition of Services. Although JBI and SCA are listed here they appear in the implementation category in the diagram above: this may seem a little confusing at first, but it is presented this way because they provide composition-like capabilities at a software level. This software level of composition is commonly referred to as Service assembly which is described in the next section. Service Assembly There is no strict definition of the term Service Assembly, but is generally used to refer to low-level Service composition. There is a proliferation of standards work describing the components and patterns of Service assembly. These standards may be broken down into a number of categories:

• Business process definition, represented by BPMN, BPML and others



• Service orchestration, represented by BPEL, XLANG, WSFL and others • Workflow, represented by XPDL, BPXL and others • Service choreography, represented by WSCI and others • Service container technologies, represented by JBI, SCA and others, that have

interactions with orchestration and choreography • Portlets, represented by WSRP and JSR 168, the Java Portlet API Specification

Description and Discovery Service description and discovery refers to the standards based techniques for advertising and finding a Service according to its capabilities. WSDL is the primary means by which a Service is described. A WSDL representation of a Service has separate abstract and concrete parts. The WSDL abstract part describes the Service interface including its operations and message structure; its concrete part describes protocol bindings (the language e.g. SOAP) and endpoints (where to find it). UDDI describes a mechanism for registering a Service to enable it to be discovered by other consumers. Service discovery can occur at either design-time or runtime. During the construction (design-time) of a composite application, for example, a Service registry might be searched for Services and operations matching specific requirements (this typically corresponds to the abstract portion of the WSDL document). At runtime the UDDI registry is generally used to find the location (endpoint) of the current version of a Service. WS-Policy and WS-MetadataExchange are used to further refine the description of a Service. These are described in more detail under the Web Service section of this Section. Messaging Messaging describes the protocols and formats of the information exchanged by Services. HTTP is an application layer protocol at the top of the Internet Protocol (IP) stack. HTTP was used initially for internet browser interaction, but has become more wide used to support a variety of internet functions; it is the most common protocol binding used for Web Services SOAP messaging. SOAP is a protocol specification for exchanging structured information in the implementation of Web Services WS-ReliableMessaging and WS-Addressing are enhancements to message exchange descriptions. These are described in more detail under Section "Web Services Standards" of this section.

Web Services Standards The second generation of Web Services specifications (commonly referred to as WS-*) has a large focus on enabling QoS within an SOA environment, which is one of the reasons Web Services has become the primary way to expose Services. This section presents a high-level description of the Web Service second generation specifications. The standards described in this section do not constitute an exhaustive list, but instead focus on those specifications that are recommended by Oracle. A high level view of the QoS supporting specifications is illustrated below.



Figure - Web Services Specifications The following sections provide an outline of the standards specifications in Figure above. Web Services Transaction (WS-TX) Web Services Transaction (WS-TX) is a collection of related specifications whose purpose is to define a set of protocols to coordinate the outcomes of distributed application actions. Transaction coordination is critical at various levels of Service interactions. Strategies, such as the classic two phase commit, can be used for short-lived Service orchestrations; but more complex methods are often needed in long running business processes in which resources must be committed before the final outcome is know: in these circumstances compensating transactions may be required. WS-TX provides a framework to handle these different scenarios. WS-TX specifies an extensible framework for developing coordination protocols through the Web Services Coordination specification, which in turn, is a framework used by two coordination types: atomic transaction (WS-AT) and business activity (WS-BA) WS-Coordination Enables scenarios in which a number of applications are required to reach consistent agreement in order to complete an operation. This form of coordination is critical to business process orchestrations. The WS-Coordination framework enables an applications to propagate an activity between Services and to register for coordination protocols. The framework enables existing transaction processing, workflow, and other systems to hide their proprietary protocols and to operate in a heterogeneous environment. WS-Coordination defines the structure required to propagate context between cooperating Services, however it does not provide the coordination for transactions between Service: it is only a coordination framework requiring other specifications, such as WS-Atomic Transaction and WS-BusinessActivity, for this purpose. WS-AtomicTransactions Provides agreement coordination protocols for the following transactional types:

• completion • volatile two-phase commit • durable two-phase commit



WS-AT is used in applications that require consistent agreement on the outcome of short-lived, distributed operations. WS-Business Activity Is used in applications that require consistent agreement on the outcome of long-running distributed activities. In particular WS-BA provides compensating transaction support to the BPEL specification. WS-Addressing This specification provides support for enabling messages as autonomous units of communication. This specification allows for the inclusion of the following:

• From Address • Return Address • Return Address if unable to delivery to requested return address

WS-A provides transport-neutral mechanisms to address Web services messages. It defines a set of abstract properties using an XML representation to facilitate end-to-end addressing of endpoints in messages to enable systems to support message transmission through networks endpoint managers, firewalls, and gateways. This is another specification important to BPEL business process orchestrations and other messaging infrastructure products such as the Enterprise Service Bus. WS-Policy This set of specifications is an enabler for other specifications, and is supported by most Web Service technology providers. WS-Policy * is used by other WS-* specifications to pass metadata and enable dynamic policy decisions. Its impact on QoS is that it restricts the delivery of messages to those consumers that conform to the predefined policy rules. This specification has been or is being adopted mostly by vendors that provide for WS-Security based specifications (in particular WS-SecurityPolicy). WS-Security The WS-Security family of Services provides a security framework for securing Web Services and messages passed in an SOA. This specification is being adopted by most Service infrastructure vendors. WS-Reliable Messaging This specification is designed to support the delivery based quality of Services for messages (eg: guaranteed delivery, at most once, etc). Partial support for this specification is provided by most Service infrastructure vendors. WS-Meta Data Exchange This specification enables the ability for Services to communicate the information needed in order to communicate and interact with one another. Requestors can then verify that the correct metadata is in fact being used for their planned message exchanges. This can increase QoS because it tends to avoid a multitude of maintenance problems associated with Service contract changes. This specification has not seen any adoption to date. WS-Eventing & WS-Notification Integration is a key benefit of SOA largely as a result of its platform independence and open standards. EAI, MOM, and other earlier generation architectural strategies have been



generally adapted to offer their capabilities through standards compliant, discoverable interfaces. Many of these adopt the Web Service model (benefiting from technology independence and rapid development) but few ultimately conform to a true SOA definition. WS-I WS-I is an industry consortium (referred to as the Web Services Interoperability Organization) whose charter is to promote interoperability across the Web Services specifications. The WS-I organization does not define standards for Web Services however, instead it creates guidelines and tests for their interoperability

Implementation Standards Enterprise Software Development standards for SOA naturally focus on specific implementation platforms. Java, for example, provides many implementations of standards as extensions to the language or the Java Enterprise platform. These Java implementation standards are typically described by Java Specification Requests (JSR) maintained by Java Community Process (JCP). The collection of Java standards implementations, focusing on the Web Services architectural style (see next section for more information) is referred to as Java Web Services (JWS). JWS is not a standard itself, but refers to implementations included with Java Enterprise Edition 5 & Standard Edition 6. The following is a outline of the JWS standards and their implementations.

• JAX-WS 2.0 (successor to JAX-RPC / XML schema data binding removed to JAXB) WSDL-to-Java mapping (with support for REST endpoints) (JSR224)

• JAXB 2.0 XML schema to Java data binding (JSR222) (separated from former JAX-RPC)

• WS-Metadata (annotation for definition & deployment) (JSR181) • SOAP with Attachments API for Java (SAAJ) (JSR67) • WS for Java EE 1.2 (WSEE) (JSR109) • JAX-R interface fro UDDI repositories (inc. with J2EE 1.4 & Java EE 5)

SOA Implementation Architectural Styles The concepts of encapsulation, separation of concerns, layered architectures, and distributed computing have evolved over the last two decades; these are the core elements of SOA implementation. Due to the history of SOA's evolution some people claim to have been doing SOA long before the term was first coined. In reality the true benefits of SOA can only be realized through adoption of common standards and suitable infrastructure. For example, CORBA promised many of the benefits of today's SOA but, it fell short in fundamental aspects, such as platform independence, not to mention more substantial SOA opportunities like Service composition. REST The unprecedented success of the Internet is largely attributable to Internet Protocol (IP) and within that Hypertext Transfer Protocol (HTTP), the commonest application layer protocol in the four-layer TCP/IP model. HTTP provides a stateless, platform-independent protocol for the exchange of information over a network; it is a standard for a request/response dialogue between clients and servers. From the definition of HTTP (or more accurately its principle author, Roy Fielding) an architectural style emerged called Representational State Transfer (REST). Core to the concept of REST is a resource which it defines as any item of information or capability addressable on a network by a global identifier (its URI in HTTP terms). The REST



architectural style describes any simple interface which transmits domain-specific data over HTTP without involving higher-level messaging, such as, SOAP (see Web Services Architecture below). REST shares architectural principles with HTTP: · Application state and functionality are abstracted into resources · Every resource is uniquely addressable using a universal syntax for use in hypermedia links All resources share a uniform interface for the transfer of state between client and resource, consisting of

• A constrained set of well-defined operations • A constrained set of content types, optionally supporting code on demand

While Fielding's REST was never intended to provide "Web Services" in the context of SOA, some believe that its simplistic model will lead to greater success than the substantially more complex approach of Web Services Architecture While REST shares some of the features that made the Internet so enormously scalable, its simplicity evades some of the more important aspects of today's business computing. It does not provide standardized mechanisms for

• describing the quality of its Service (QoS, including reliability, availability) • transaction management • security

While REST's simplicity supports rudimentary mash-ups by almost any user, it does not easily and comprehensively support the rapid composition of complex business processes. There are some circumstances, however where the simplicity of REST makes it an appropriate choice. For example, in the public domain where consumers are unlikely to be sophisticated enough to conform to richer standards like Web Services. Similarly environments that are not transactional or do not require high levels of security may be suited to a REST architectural style. The choices of architectural style are also not mutually exclusive: REST, Web Services, and potentially other styles can coexist, albeit at a higher cost in infrastructure and engineering skills. Support for REST is also starting to appear in Web Services standards: WSDL 2.0, although not yet widely implemented (by tools vendors), has broadened its binding specification to include all HTTP methods, thus implicitly including support for RESTful Web Services. Remote Procedural Call (RPC) Fundamentally RPC is a means of calling a method or function on another node in a distributed computing environment. Originally RPC's were not standardized in any way and typically comprised mysterious, idiosyncratic, poorly documented Unix socket code. As such the basic RPC offers none of the benefits of SOA. Early examples of standardized RPC's included Sun's RPC, Microsoft's DCOM, Java's RMI, OMG's CORBA, ODBC/JDBC, and SQL*Net. More recent RPC's include XML-RPC, and HTTP.



Although HTTP is itself a form of RPC (its limited set of commonly used method calls are GET, POST, PUT, DELETE) REST is characterized by the exchange of resources (nouns) which differentiates it from RPC's exchange of commands (verbs). RPC is now considered an Application layer protocol in the TCP/IP model. XML-RPC and SOAP The cornerstone of today's platform and technology independence is eXtensible Markup Language (XML) .It is a language definition that yields conversations so verbose that, only modern networks can accommodate it. Due to its simplicity, platform independence, and extensibility a series of rapid steps were taken to exploit XML. These are outlined in the following paragraphs. XML-RPC is an unusually simple RPC standard using XML for its payload. Simple Object Access Protocol (SOAP) evolved from XML-RPC concepts. SOAP is a protocol specification for exchange of structured information using XML and TCP/IP application layer protocols (typically RPC and HTTP) to form the basis for Web Services message exchanges and is therefore a common enabling technology for SOA. Asynchronous JavaScript and XML (AJAX) refers to a group Rich Internet Application (RIA) development techniques that exploit the XMLHttpRequest method of the browser Document Object Model (DOM) using XML-RPC. AJAX is an enabling technology in the loosely defined Web 2.0 realm. Although it is not directly related to SOA, Web 2.0 does offer some composition techniques typically referred to as "mashups". Web Services Architecture (WSA) Many people equate SOA with Web Services or even BPEL. Web Services, BPEL, and a long list of associated specifications describe the commonly used technologies developed in support of SOA. However it is important to separate the implementation technologies from the broader subject of the Architecture itself. The World Wide Web Consortium's (W3C) Web Service Architecture (WSA) provides a definition of Web Services. The WSA requirements document provides background and purpose to the WSA and defines a Web Service that we can use to contrast the definition of a SOA Service. The following definition is taken from the W3C WS Glossary: "A Web Service is a software system identified by a URI [RFC 2396], whose public interfaces and bindings are defined and described using XML. Its definition can be discovered by other software systems. These systems may then interact with the Web Service in a manner prescribed by its definition, using XML based messages conveyed by Internet protocols." The WSA breaks down Web Services into four related models:

• Service oriented model • message oriented model • resource oriented model • policy model

The models describe the aspects of action, message, resource, and policy respectively. Many other RFC's underpin the fundamental definition of Web Services but, more relevant to a SOA RA is the catalog of Web Services standards extensions that support interoperability in the infrastructure. These include:

• WS-I • WS-Security



• WS-Addressing • WS-SecurityPolicy • WS-ReliableMessaging (and WS-ReliableMessagingPolicy) • WS-SecureConversation • WS-Security • WS-Transactions (plus WS-AtomicTransaction and WS-BusinessActivity) • WS-Trust

One of the major inhibitors of SOA adoption, at least in the beginning, was the ability to achieve certain levels of QoS through a Service Oriented Architecture. The initial release of specifications utilizing Services in the form of Web Services had very weak support for various standard levels of QoS based requirements.



Navigating Fusion Middleware Control Fusion Middleware Control is a Web-based interface from which you can monitor and administer a farm. A farm is a collection of components managed by Fusion Middleware Control. It can contain Oracle WebLogic Server domains, one Administration Server, one or more Managed Servers, clusters, and the Oracle Fusion Middleware components that are installed, configured, and running in the domain. Fusion Middleware Control organizes a wide variety of performance data and administrative functions into distinct, Web-based home pages for the farm, domain, servers, components, and applications. The Fusion Middleware Control home pages make it easy to locate the most important monitoring data and the most commonly used administrative functions—all from your Web browser. To display Fusion Middleware Control, you enter the Fusion Middleware Control URL, which includes the name of the host and the port number assigned during the installation. The following shows the format of the URL: http://hostname.domain:port/em Enter the Fusion Middleware Control URL in your Web browser. For example: http://localhost:7001/em The default user name for the administrator user is weblogic. This is the account you can use to log in to Fusion Middleware Control for the first time. The password is the one you supplied during the installation of Oracle Fusion Middleware.

Accessing FMW Control Procedure In this topic you will learn to: Accessing FMW Control



Step Action 1. Enter the desired information into the Search Bookmarks and History field.

Enter "http://voip2003:7001/em".

Step Action 2. Press [Enter].



Step Action 3. Enter the desired information into the * User Name field. Enter "weblogic".

Step Action 4. Click in the * Password field.



Step Action 5. Enter the desired information into the * Password field. Enter "welcome1".

Step Action 6. Click the Login button.



Step Action 7. Summary

In this topic you learned how to: Accessing FMW Control End of Procedure.



FMW Control Layout Procedure In this topic you will learn to: Navigate the FMW Control Layout

Step Action 1. The Farm page is displayed, as shown

Click the object.



Step Action 2. The Farm menu is displayed at the top of the page. From the Farm menu, you

can: Create and delete components and clusters View log messages Specify monitoring credentials The Farm menu is always displayed, even if you have selected other targets. Click the object.



Step Action 3. Click the Expand link.





Step Action 7. Click the object.



Step Action 8. Click the Collapse link.





Step Action 12. Click in the My Preferences field.



Step Action 13. Click the cell.

Step Action 14. Click the cell.



Step Action 15. Click in the Enterprise Manager Help field.



Step Action 16. Click the Maximize button.

Step Action 17. Click the Close button.



Step Action 18. You can view the topology of the domain by selecting Topology. The Topology

Viewer provides you with a high-level view of the topology, including Managed Servers, deployed applications, and the routing configuration Click the Topology link.



Step Action 19. Fusion Middleware Control provides a Topology Viewer for the farm. The

Topology Viewer is a graphical representation of routing relationships across components and elements of the farm. You can easily determine how requests are routed across components. For example, you can see how requests are routed from Oracle BAM, to Oracle HTTP Server, to a Managed Server, to a data source. Click the View list.

Step Action 20. The Topology Viewer enables you to easily monitor your Oracle Fusion

Middleware environment. You can see which entities are up and which are down. Click the Group by Application object.



Step Action 21. The Topology Viewer is displayed in a separate window.

Click the object.



Step Action 22. To see information about a particular target, place your mouse over the target. To

view additional information, click More Click the object.



Step Action 23. With Topology Viewer, you can also:

Search for a target within the topology. This makes it easier to find a target if you have many targets. Enter the name in the Find box. The target is highlighted and the topology is repositioned so you can see the target if it was not previously visible in the viewing area. You can also specify criteria for the search. From Find, choose the one or more types of Status or one or more of Target Type, or both. View the targets by status. Choose Up, Down, or Unknown from the Target Status at the top of the page. Navigate to the home page of a target. Right-click the target, and select Home. Hide or show the status or metrics. Click Status or Metrics in the Overlays section. If you select Metrics, one key performance metric for the component is displayed. (You cannot change the metric that is displayed.) View the routing relationships between components. For example, you can view the routing from Oracle Web Cache to Oracle HTTP Server to Oracle WebLogic Server. Clicking on the line between the two targets displays the URLs used. You can perform operations directly on the target by right-clicking. The right-click target menu is displayed. For example, from this menu, you can start or stop an Oracle WebLogic Server or view additional performance metrics. Click in the Find field.



Step Action 24. Enter the desired information into the Find field. Enter "class".

Step Action 25. Click the Find link.



Step Action 26. Click the Close link.

Step Action 27. Click the Show Nodes Pick List object.



Step Action 28. Click in the Data Sources field.



Step Action 29. Click the Options object.

Step Action 30. Click in the Top Down field.



Step Action 31. Click the Maximize button.



Step Action 32. Click the Options object.

Step Action 33. Click in the Left to Right field.



Step Action 34. Click the Annotations object.



Step Action 35. Click in the Metrics field.

Step Action 36. Click the View list.



Step Action 37. Click the Group by Middleware object.



Step Action 38. Click the Close link.




Step Action 40. Click the FusionMW_domain link.



Step Action 43. Click in the Application Deployments field.

Step Action 44. Click in the Class2010 (AdminServer) field.



Step Action 48. Click in the soa-infra (AdminServer) field.




Step Action 50. Click in the SOA Deployment field.



Step Action 51. Click in the Service Engines field.

Step Action 52. Click in the Security field.



Step Action 53. Click in the SOA Administration field.



Step Action 54. Click in the General Information field.

Step Action 55. Click the Close graphic.




In this topic you learned how to: Navigate the FMW Control Layout End of Procedure.

Exploring WebLogic Administration Console Introduction To log in to the Administration Console perform the following tasks: Enter the following URL in a browser: http://hostname:port_number/console The port number is the number of the Administration Server. By default, the port number is 7001. The login page is displayed. Log in using the user name and password supplied during installation or another administrative user that you created. WebLogic Server Administration Console is displayed:



Procedure In this topic you will learn to: Explore WebLogic Administration Console

Step Action 1. Enter the desired information into the Username: field. Enter "weblogic".



Step Action 2. Click in the Password: field.

Step Action 3. Enter the desired information into the Password: field. Enter "welcome1".



Step Action 4. Click the Login button.



Step Action 5. Click the Home Page - FusionMW_domain - WLS Console

ROLE_SYSTEM_DOCUMENT.

Step Action 6. Click the Home Page - FusionMW_domain - WLS Console




Step Action 7. Click the Environment Expand Node graphic.




Step Action 9. Click the Services Expand Node graphic.



Step Action 11. Click the Interoperability Expand Node graphic.




Step Action 13. Click the Diagnostics Expand Node graphic.



Step Action 17. Click the Deployments link.

Step Action 18. Click the Servers link.



Step Action 19. Click the Clusters link.

Step Action 20. Click the Virtual Hosts link.



Step Action 21. Click the Machines link.



Step Action 22. Right-click the object.

Step Action 23. Press [Escape].



Step Action 24. Click the Environment Collapse Node graphic.

Step Action 25. Click the Data Sources link.



Step Action 26. Click the Messaging link.



Step Action 27. Click the Services Collapse Node graphic.

Step Action 28. Click the Diagnostics link.



Step Action 30. Click the Log Files link.

Step Action 31. Click the Diagnostic Modules link.




Step Action 34. Click the FusionMW_domain link.



Step Action 35. Click the Preferences link.



Step Action 36. Click the Preferences - FusionMW_domain - WLS Console






Step Action 38. Click the Shared Preferences link.

Step Action 39. Click the Extensions link.





Step Action 42. Click the WLST Script Recording link.




In this topic you learned how to: Explore WebLogic Administration Console End of Procedure.



Fusion Middleware Farm A farm is a collection of components managed by Fusion Middleware Control. It can contain Oracle WebLogic Server domains, one Administration Server, one or more Managed Servers, and the Oracle Fusion Middleware components that are installed, configured, and running in the domain.

Examining a FMW Farm Procedure In this topic you will learn to: Examine a FMW Farm

Step Action 1. Fusion Middleware Control displays the target navigation pane on the left and

the content pane to the right. For example, when you first log in to Fusion Middleware Control, the farm home page is displayed on the right.



Step Action 2. Farm Menu, which is above the target navigation pane, provides a list of

operations that you can perform on the farm. The Farm menu is always available. Click in the General Information field.



Step Action 3. Click the Close graphic.

Step Action 4. From the target navigation pane, you can expand the tree and select an Oracle

WebLogic Server domain, an Oracle WebLogic Server Managed Server, a component, an application, or a Metadata Repository. Click the Expand link.



Step Action 10. Click the Scroll bar



Step Action 17. When you select a target, such as a Domain or a component, the target's home

page is displayed in the content pane and that target's menu is displayed at the top of the page, in the context pane. For example, if you select a Managed Server, the WebLogic Server menu is displayed. You can also view the menu for a target by right-clicking the target in the navigation pane. Click in the FusionMW_domain field.

Step Action 18. Dynamic Target Menu, which is above the Content pane, provides a list of

operations that you can perform on the currently selected target. The menu that is displayed depends on the target you select. The menu for a specific target contains the same operations as those in the Right-Click Target Menu. Because the FusionMW_domain was selected, the dynamic target menu listed in the context pane is the WebLogic Domain. Click in the mds-soa field.



Step Action 19. On the right, Content Pane shows the current page for the target. When you first

select a target, that target's home page is displayed. The menu for a specific target contains the same operations as those in the Dynamic Target Menu. Click the Expand link.




Step Action 21. Click in the default field.



Step Action 23. Click the SOA Infrastructure Pick list object

Step Action 24. This Action will Return to the target's home page

Click the Home cell.




In this topic you learned how to: Examine a FMW Farm End of Procedure.

BPM Methodology The BPM methodology is a phased, deliverable-oriented methodology that streamlines implementation projects, minimises risk, and reduces total cost of implementation. BPM takes a disciplined approach to project strategy, project management, organisational change management, solution management, and other disciplines applied in the implementation of BPM BPM solutions. The methodology supports project teams with templates, tools, questionnaires, and checklists, including guidebooks and accelerators. BPM empowers companies to exploit the power of the accelerated features and tools already built into BPM solutions. Benefits of BPM Method includes: · Faster implementations with streamlined and focused methodology · More reliable projects, thanks to proven tools, accelerators, and best practices · Lower risk · More efficient use of resources · Reduced costs · Effective project management based on Project Management Institute standards Phases The BPM methodology delivers the following phases:



1. Strategy and Planning In the Strategy and Planning phase, the project team defines project goals, a high-level scope, and a project plan. Executive sponsorship is secured, and the project standards and organization are set up. The implementation strategy is defined and approved. At the same time, the project procedures, standards, organization, and staffing are finalized. Roles and responsibilities of the entire project team are agreed upon and documented. The objectives of the project are validated, and all initiation activities are documented in the project charter. 2. Analysis & Design During this Analysis & Design phase, solution and technical designs are documented in the Analysis & Design. All available documentation for standard, delivered support for BPM business scenarios and all relevant preconfigured support for best practices are reviewed and discussed with BPM experts. All functional and technical requirements, coupled with project issues and gaps, are documented in the BPM solution. 3. Build In the build phase, the BPM software system is configured and tested in a number of cycles. Initially, the baseline configuration, which represents the core business process settings, is performed, tested, and confirmed. This is followed with a series of configuration and development cycles, to implement the entire end-to-end solution. The solution is tested in a number of cycle tests and in a focused end-to-end integration test. All development such as enterprise services, interfaces, data conversion programs, reports, and any required enhancements are built and documented in Oracle AIA EBS PIP – Process Integration Pack. Legacy data conversion programs are created and tested. The production system is installed during realisation. 4. Deployment Within the Deployment phase, all systems are known to function correctly following the approved integration test. Technically, all integration issues should now be resolved. Detailed transition and cutover plans are created. The customer support organization is put in place. The production system is set up with transports and customer data. At the end of this phase, the production system is switched on and business operations start in the new environment. 5. Go-live support The purpose of the go-live support phase is to move from a preproduction environment to live production operation. An easily accessible production support organization must be in place to support the end-user community, not just for the first critical days of production operations, but also for long-term support. 6. Monitor The primary goal of the Run and Monitor phase is to ensure the operability of the solution. Operability is the ability to maintain IT solutions in a functioning and operating condition, guaranteeing systems availability and required performance levels to support the execution of the enterprise’s business operations. The recommended starting point of the phase is an assessment of solution operation after the go-live support phase to identify the relevant BPM standards for solution operations to be established or improved in the phase. Deliverables



The BPM methodology is structured around the key project work streams. For each work stream, the methodology lists the number of deliverables that are to be produced in each phase of the project. The deliverables in later phases leverage or build upon deliverables completed in earlier stages. The roadmap is structured as a work breakdown structure (WBS) that represents a complete list of deliverables that need to be completed by the project team. The BPM methodology for implementation projects represents a standardized work breakdown structure that provides the foundation for defining implementation project work in a deliverable-oriented, hierarchical manner and managing the project work to completion. BPM methodology contains a standard set of templates, samples, accelerators, guidelines, and checklists for use by project teams in effectively managing and completing BPM solution implementation projects.

BPM Governance and BPM (Project) Methodology Difference between BPM Governance and BPM (Project) Methodology BPM Governance is a management discipline that ensures a company is steered in a process oriented manner. BPM Governance can be seen as the steadily running wheel which defines aspects like process lifecycle management, process responsibilities, change management, modelling conventions and so on. WebLearning delivers a methodology that describes the implementation of BPM Governance within a company. BPM Governance should be coordinated by a well established team within a company. The BPM (Project) Methodology accompanies certain process oriented projects and can be seen as a small wheels spinning for a certain time. Since one characteristic of projects is to have a defined start and end date, the usage of the BPM (Project) Methodology in the context of a concrete project also fits into a defined timeframe. While applying the BPM (Project) Methodology, the following questions might be answered by the department which is responsible for the BPM Governance.

• Is there an existing Process Structure? • Is there an existing modelling convention that needs to be followed for process

modelling? • Is the used BPM (Project) Methodology in line with the requirements stated by BPM

Governance? Maybe the project methodology needs to define additional steps that are currently not part of this methodology. It might also be the case that only a subset of activities is mandatory regarding the given governance.

• Are process models available? And what structure does this model follow (APQC, SCOR, individual etc.)?

• What is the tools landscape for process modelling? • Are there any external requirements for processes (e.g. ISO, SOX compliance?) • Who is responsible for what Software Independent Business Object? For example a

request to add another attribute to the object "customer" might need to go over someone’s desk.

• Who is responsible for Software Independent Process Components which provides functionality around a software independent business object like create, read, update, delete customer?

Who is responsible for a certain process?



• All changes that might affect a certain process need to be discussed with this person. • This person can also give information about preceding or subsequent processes

While running a project, the above stated general conditions need to be followed. Only then the new process can be seamlessly connected to the BPM Governance of the company.

Process Governance To perform the steps of PML you need to know about mandatory and optional BPM processes, tools and conventions. Process Governance provides the framework to ensure corporate efficiency and effectiveness of all process related activities. Process Ownership The establishment of this role as a central point of contact for all information related to a specific business process is a prerequisite to be a process company. Every business process has to be assigned to a particular person that is responsible for the whole Process Management Lifecycle. To ensure an efficient interaction between business and IT, the role of a technical process owner should be available in IT as a counterpart to the business process owner. Organization The management of processes takes place within the boundaries of existing organizational structures. Optimizing an existing process or introducing a new process often indicates a change in the existing organizational structures. Therefore, process management is tightly linked to the management of organizations. People To operate business processes and to perform process management, the right people with the right skills within business and IT units are required. The process maturity largely depends on the process management skills of the employees. Technology The efficient execution of business processes in today's world is largely dependant on IT systems.

BPM Methodology Use Case Customer Service Execution Process



Below is a high level description of an example, which should help to understand the methodology approach. With in each activity of the BPM Methodology, there will be a reference to this example explaining what you would do within the activity with regards to this specific business use case. Business Case WebLearning Consulting has been asked by the Office of the CEO Joe Thompson to provide information about WebLearning BPM Best Practices Method to improve processes. After process analysis WebLearning has maybe the chance to implement the needed software for each process. The storyline includes the following information about the customer: The Company facts The Company we are dealing with is the "WLN Beverages Company", one of the top five producers of beverages. Mr. Thompson provided us some information about his company. Please see the information on the following slides. It is a snap shot of the company, including revenues and the organizational view as shown in the attached overview presentation. Mission & Vision The company's vision is expressed by the four goals shown on the slide below. They focus on the four subjects people, products, partners, and profit. The WLN Beverages Company's mission is "To refresh the world!", "Inspire moments of optimists", and "To create value and make a difference". Resulting Objectives Joe Thompson is convinced that the best strategy to fulfil the mission is to focus is on Quality, Uniqueness and Performance. “We are different, not like everybody else! There are not many witty white horses in the market." Besides that strategic goal, a time line is set to achieve it: 2009. That requires improving their business processes in order to gain the needed effectiveness and flexibility of a process focused company. Market Analysis The beverage industry itself lives of the vital necessity of human beings to drink. The growing world population constantly creates additional demand in the future. Beside that general outlook, a few trends can be identified regarding the relevance of different types of drinks as shown in the overview presentation attached. Current discussions held within the community influence the trends and future demands additionally. Subject to discussions are: tightening laws as a result of rising alcohol consumption by teenagers or market consolidation regarding mineral water producers. Rough overview on the BPM Phases Planning All necessary content for describing the activities within Planning phase is available. The company fact, mission and strategy, and market analysis are available. Additional content that can be used are interviews with: · the CEO Joe Thompson · the Sales Manager · the Research & Development Manager As-Is Analysis The following content is already provided: · GPD for Beverage Industry · RACI & ARIS EPC



The current idea is that we have a manual, low scale customer service process available at the customer. This one is described as RACI. This process will be subject to optimization later on. Therefore the following things need to be done: · Define the appropriate process parameters and classifications · Think of weaknesses and clusters (should be documented within the As-Is-RACI) To-Be Design According to the strategy key note "focus on uniqueness and performance" a key differentiator would be an integrated supply chain to the customer. Some customers were provided with fridges for storing the beverages sold by the WLN Beverages Company. To guarantee the "quality and performance" as stated in the strategy key note, this delivery model using fridges at customer side needs to be supported by a Customer Service process. As a result of the strategy and the importance of the different products, it is recommended to place more fridges at customer site. To guarantee the quality of service for a large scale of customers that are hosting the fridges, it is necessary to improve the service process. The following optimized process has been described as · RACI · Process diagram · BPMN Business Transformation The organizational changes that will result be establishing the new process, needs to be described (enrich the existing organizational diagram). Within Standard Configuration the steps need to be described that are referred to within the "ESEC Implementation Guide". (Configuration settings for additional user status in service notification) Within the SOA / Composition stream, the entities need to be described using an "reverse-engineering-approach" since the solution is already provided as a composite application. Requirements from the implementation colleagues:

• At least one Enterprise Service should not be available in the Discovery Server in order to be described and implemented for the solution (Check if only existing Enterprise Services of the Discovery Server (ERP) are used; identify gap)

A benefit would be, if reference architectures or implementation patterns could be used in order to align with the implementation team

Exploring BAM and BPM Suite 11g Components When the configuration completes and you have started the Administration Server and the Managed Servers, you can view and manage Oracle Fusion Middleware using the graphical user interfaces or command-line tools. For example, to use Fusion Middleware Control to view and managed your environment, enter the Admin Server URL you noted from the Creating Domain screen, with /em appended. For example: http://hostname.domainname:port/em



By default, the port is 7001.

Exploring BPM Studio In this topic, you explore the BPM Studio interface. A successful launch and login to the Studio proves the success of the JDeveloper and Studio installation. It shows you how to build a simple Welcome application using Oracle BPM Suite 11gR1. In order to perform this topic, you must have previously installed Oracle BPM 11gR1 and JDeveloper 11.1.1.5 with both the SOA and BPM extensions. In this section you create the basic starting point for the Welcome process using the JDeveloper Studio. You add two activities - an interactive activity and a service activity. The end user will be able to enter a Hello message, using the BPM Workspace. The message will be captured in a business object and passed to a file service, which, in turn will write the message to a disk file. Later, you expand upon this to add more complexity to the process.

You create process elements throughout this section of the tutorial.

Procedure In this topic you will learn to: Explore BPM Studio



Step Action

1. Start JDeveloper from the Windows Task Bar: Start > All Programs > Oracle Fusion Middleware 11.1.1.5.0 > JDeveloper Studio 11.1.1.5.0 When prompted to select a role, accept the Default Role and click OK. Click the JDeveloper Studio 11.1.1.5.0 menu.

Step Action 2. Click the OK button.



Step Action 3. Close the Tip of the Day window

Click the Close button.



Step Action 4. Create a new application. Click the New Application bar in the left panel or use

the File>New Menu option Click the File menu.

Step Action 5. Click the New...Ctrl+N menu.



Step Action 6. The BPM Application wizard opens. Name the application "ClassBPMIDE" and

accept the default directory for storing application files (E:\JDeveloper\mywork). Select BPM Application in the Application Template panel. Click the Applications tree item.



Step Action 7. Click the BPM Application cell.




Step Action

9. Enter the desired information into the Application Name: field. Enter "ClassBPMIDE".

Step Action 10. Click the Next button.



Step Action 11. In Step 2 of the Create BPM Application wizard, you create a project for the

ClassBPMIDE application. Enter ClassBPMIDemo as the Project Name. Notice that BPM and SOA are selected as project technologies by default. Click Finish. Enter the desired information into the Project Name: field. Enter "ClassBPMDemo".




Step Action 13. Click the Finish button.



Step Action 14. In the next screen, name the process "ClassWelcome".

Enter the desired information into the Name field. Enter "ClassWelcome".



Step Action 15. In the BPM Process wizard, select the Manual Process pattern. Click Next.

Click the Manual Process cell.




Step Action 17. The process model appears in the design editor panel in the middle of the

JDeveloper window. The tab name will be same as the name of your new process. Click the Finish button.



Step Action 18. Change the name of the user task in the design model. Notice that the model

begins and ends with two circular icons. The circle on the left is a Start activity and the circle on the right is an End activity. Connecting the two circles is a line that represents the flow of activities through the process. This is called the sequence flow and sometimes is referred to as the "transition line". Between the Start and End activities is a User Task type activity. Right click on this and select Properties. Click the User Task Type.

Step Action 19. Right-click the User Task Type.



Step Action 20. When the Properties dialog box appears, on the Basic tab, change the name of the

activity to "Request Welcome". Click OK. Click the Properties menu.



Step Action 21. Enter the desired information into the Name: field. Enter "Request Welcome".

Step Action 22. Don't worry about the warning message indicating that no implementation has

been defined. You will do this later Click the OK button.



Step Action 23. If not already visible, Add the Component Palette to the JDeveloper window by

selecting View > Component Palette from the menu. The palette will appear in the right pane of the window. Select BPM from the drop-down list at the top of the Component Palette, then expand the Activities accordion panel as shown. Click the Activities.



Step Action 24. Add a service activity to the process. You'll need to first make room for another

activity on the sequence flow. Click on the End activity and drag it to the right, dropping it on the right side of the design panel, allowing enough room for another activity icon to fit between the Request Hello activity and the End activity. Click the End Activity



Step Action 25. Press the left mouse button and drag the mouse to the desired location.

Step Action 26. Release the mouse button.



Step Action 27. Now click the Service activity icon in the Component Palette and drag it to the

Sequence flow between Request Welcome and End. Drop it there. Notice that the transition line turns blue when the drop target area approaches the line. Important: The transition line must be blue when you drop the object in order for the transition line to be connected to the activity. Click the Service.



Step Action 28. Press the left mouse button and drag the mouse to the desired location.

Step Action 29. When you drop it, the Properties dialog box for the activity opens. On the Basic

tab, change the activity name to "Write Message". Release the mouse button.



Step Action 30. Enter the desired information into the Name: field. Enter "Write Message".




Step Action 32. Click the View menu.



Step Action 33. The Oracle BPM Project Navigator displays a hierarchical view of the

components of an Oracle BPM project. The components displayed in the navigator are related to the modeling and implementation of business processes. Click the BPM Project Navigator menu.



Step Action 34. The Log Window displays messages, errors, and warnings to the BPM project as

well as compilation and deployment of SOA composite applications. Click the Messages - Log.

Step Action 35. The Simulation View allows you to run and see the result of project simulation

models. Click the Simulations.



Step Action 36. The Documentation Window allows you to create end-user and use case

documentation for your processes. You add documentation for the entire process or for each flow object within your process. Click the Documentation.



Step Action 37. The BPM Component Palette contains a list of the BPMN flow objects supported

by Oracle BPM. You can model business processes by dragging and dropping these flow objects from the BPM Component Palette to the Process Editor. Click the Activities.

Step Action 38. Click the Events.



Step Action 39. Click the Events.



Step Action 40. Click the Gateways.

Step Action 41. Click the Gateways.



Step Action 42. Click the Artifacts.



Step Action 43. Click the Artifacts.

Step Action 44. Like the Project Navigator, the Application Navigator displays a hierarchical

view of the components of a project. However, these are lower-level components that include the underlying configuration files, XML files, java classes, and other resources used by a SOA composite application. Click the BPM Application Navigator.



Step Action 45. Click the ClassWelcome tree item.



Step Action 46. The Structure window offers a structural view of the data in the component

currently selected in the active window of those windows that participate in providing structure: the diagrams, the navigators, the editors and viewers, and the Property Inspector. The components displayed in the Structure window are usually components in the Project or Application Navigators. Click the + button before the Activities tree item.

Step Action 47. Click the Activities.




In this topic you learned how to: Explore BPM Studio End of Procedure.

Exploring BPM Composer In this topic, you explore the BPM Composer interface.

Procedure In this topic you will learn to: Explore BPM Composer



Step Action 1. Enter the desired information into the field. Enter "bpm/composer".

Step Action 2. Click the Go to "http://localhost:7001/bpm/composer" (Alt+Enter to open in

a new tab) button.



Step Action 3. Enter the desired information into the * Username: field. Enter "weblogic".



Step Action 4. Click in the * Password: field.

Step Action 5. Enter the desired information into the * Password: field. Enter "welcome1".



Step Action

6. Click the Login button.

Step Action 7. Click the Administration link.



Step Action 8. Click the Project Management button.

Step Action 9. Click the Template Management link.



Step Action 10. Click the Role Mapping link.

Step Action 11. Click the Home link.



Step Action 12. Click the Create New Project button.



Step Action 13. Click the Open a Project button.

Step Action 14. Click the Project button.



Step Action 15. Click the Project button.

Step Action 16. Click the Preferences link.



Step Action 17. Click the Cancel button.



Step Action 18. Click the Help button.

Step Action 19. Click in the Quick Search field.



Step Action 20. Enter the desired information into the Quick Search field. Enter "studio".

Step Action 21. Click the Search link.



Step Action 22. Click the Collapse Pane button.

Step Action 23. Click the Restore Pane button.




In this topic you learned how to: Explore BPM Composer End of Procedure.

Exploring BAM Active Studio Procedure In this topic you will learn to: Explore BAM Active Studio



Step Action 1. Click the Active Studio button.

Step Action 2. Click the Collapse Task Area button.



Step Action 3. Click the Expand Task Area button.



Step Action 4. Click the My Reports object.

Step Action 5. Click the Shared Reports object.



Step Action 6. Click the Alerts object.

Step Action 7. Click the Home object.



Step Action 8. Click the Personalize object.



Step Action 9. Click the Home Page object.

Step Action 10. Click the Cancel object.




In this topic you learned how to: Explore BAM Active Studio End of Procedure.

Understanding WebLogic Clusters Overview A WebLogic Server cluster consists of multiple WebLogic Server instances, running simultaneously and working together to provide increased scalability and reliability. A domain includes one or more WebLogic Server instances, which can be clustered, nonclustered, or a combination of clustered and nonclustered instances. A domain can include multiple clusters. A cluster appears to clients as one WebLogic Server instance. The server instances that constitute a cluster can run on one machine or on different machines. You can increase a cluster’s capacity by adding server instances to the cluster on an existing machine, or by adding machines to the cluster to host the incremental server instances.



All server instances in a cluster use multicast or unicast to broadcast regular server heartbeat messages to other members of the cluster. Each heartbeat message contains data that uniquely identifies the server that sends the message. Servers broadcast their heartbeat messages at regular intervals. In turn, each server in a cluster monitors the multicast or unicast address to ensure that all peer servers’ heartbeat messages are being sent. This section covers the following topics: Creating a Cluster of Existing Servers Starting the Clustered Servers Monitoring the Cluster

Creating a Cluster of Existing Servers Procedure In this lesson, you learn how to: Create a Cluster of Existing Servers



Step Action 1. If any of your managed servers are running, shut them down. For example, using

the administration console, select Environment > Servers from the Domain Structure panel. Then click the Control tab. Click the Environment Expand Node graphic.




Step Action 3. Click the Control link.



Step Action 4. Lets Scroll down to complete the task

Step Action 5. Select the check box for each managed server. Click the Shutdown button and

select Force Shutdown Now. Release the mouse button.



Step Action 6. Click the Select weblearning1 option.



Step Action 7. Click the Shutdown button.

Step Action 8. Click the Force Shutdown Now link.



Step Action 9. Click the Yes button.



Step Action 10. Select Environment > Clusters from the Domain Structure panel. Click the New

button. Click the Lock & Edit button.





Step Action 13. Click the New button

Release the mouse button.



Step Action 14. Click the New button.

Step Action 15. Click in the *Name: field.



Step Action 16. Enter the desired information into the *Name: field. Enter "Class2009Cluster".




Step Action 18. Note:

For multicast communication to function properly, your machine's network interface must be active. Release the mouse button.



Step Action 19. Click the Messaging Mode: list.

Step Action 20. Click the Multicast option



Step Action 23. Select the new cluster. Click the Configuration > Servers tab.


Step Action 24. Click the Class2009Cluster link.




Step Action 27. Next, Click the Add button




Step Action 28. Click the Add button.

Step Action 29. Select one of your managed servers and click Finish.

Click the Select a server: list.



Step Action 30. Click the weblearning1 option




Step Action 32. Repeat the previous steps to add the remaining two managed servers to the

cluster. In the Change Center panel, click Activate Changes. Lets Scroll down to complete the task



Step Action 37. Click the Select a server: list.

Step Action 38. Click the weblearning2 option



Step Action 40. Lets Scroll down the page




Step Action 44. Lets Scroll down to view the completed task

Step Action 45. Next, In the Change Center panel, click Activate Changes.





In this lesson, you learned how to: Create a Cluster of Existing Servers End of Procedure.

Starting the Clustered Servers Procedure In this lesson, you learn how to: Start the Clustered Servers



Step Action 1. Perform the following steps:

Start one of your managed servers. From a shell, change directories to <domain>\bin and use the startManagedServer script. For example: startManagedWebLogic.cmd weblearning1 localhost:7001 Supply your administrative credentials, if prompted.



Step Action 2. Watch the server start up using the shell's standard output stream. At some point,

you should see it begin listening for cluster communication and begin waiting to synchronize with other servers in the cluster. Because the other servers have not started, there is nothing for it to synchronize with yet:



Step Action 3. Supply your administrative credentials

Step Action 4. Note: If your managed server's Standard Out Severity Level is not set to Notice

or lower, these log messages will not be shown in the shell. Alternatively, use the console to view the contents of the server's log file.



Step Action 5. Watch the server start up using the shell's standard output stream.



Step Action 6. Repeat the previous steps to start the other two managed servers. Once again, use

the shell's standard output stream or the server log to confirm that the servers joined the cluster successfully


In this lesson, you learned how to: Start the Clustered Servers End of Procedure.

Monitoring the Cluster Procedure In this lesson, you learn how to: Monitor the Cluster



Step Action 1. Return to the administration console. Select Environment > Clusters from the

Domain Structure panel. Then select your cluster. Click the Environment Expand Node graphic.



Step Action

4. Release the mouse button.

Step Action 5. Click the Class2009Cluster link.



Step Action 6. Click the Monitoring link.




Step Action 8. The resulting table should indicate that all the three managed servers are

currently participating in the cluster. Various communication statistics are also available. Release the mouse button.



Step Action 9. Lets Scroll up the page





In this lesson, you learned how to: Monitor the Cluster End of Procedure.

Oracle SQL - Working with UNION A union is two SELECT statements that you combine in the same query. Unions enable you to have two tables in the same query without having joining criteria and without creating a Cartesian product. Upon completion of this lesson, you will be able to:

• Describe unions. • Create unions in queries. • Use joins in unions.

Understanding UNIONS You use unions to combine records that have no fields in common and to retrieve similar data from unrelated records in one query, as shown in this example:

In this topic, you will review unions in queries.

Procedure



Step Action 1. In this example, the Training department requires a query that lists all training

locations and all vendors from which it buys products. To obtain a consolidated listing of all locations and vendors, you need to combine the names of the training locations from the PSU Training Locations table (PSU_TRNLOC_TBL) with the names of the vendors from the Vendor table (PSU_VENDOR_TBL).



Step Action

2. To retrieve the correct query output, you would write two separate statements and create a union to combine them in one query, as shown in this example.

Step Action 3. You must follow three rules with unions:

• Each statement must consist of the same number of fields. • Each statement must consist of the same data types. • The field data types in each statement should correspond (be in the same order).



Step Action 4. This diagram lists and explains the features of union.



Step Action 5. Literals are placeholders or pieces of text. Literals are useful when you create

complex unions. When you create a union, both queries must have the same number of fields, but the fields do not have to be identical. Therefore, applying literals as placeholder fields is useful.

Step Action 6. Unions require that you use the same numbers of fields in each SELECT

statement. Because the fields do not have to be the same, you can create a literal expression and use that expression as a field. This example shows five fields, the fifth field ('TrnLoc') is a literal field.



Step Action 7. This diagram shows the steps used to include literals as placeholder fields.

Step Action 8. This diagram shows the steps used to create a union.



Step Action 9. You have successfully reviewed the Understanding Unions topic.

End of Procedure.

weblearning developer demo courses train - ibm training · disclose these training materials are...

Documents