Friday May 11, 2012

Sample Script for Extending an Existing Oracle Service Bus (OSB) Cluster by Adding Additional Managed Servers

Extending an existing Oracle Service Bus (OSB) cluster (scaling up or scaling out) is currently a manual task as described in our product documentation:


If some of the steps or tasks involved in adding the server are not completed successfully or omitted, the new managed servers will fail or have issues. In order to help with this task, we have created a very basic sample scipt that should help to successfully create the additional managed servers. The script is available as a SAMPLE CODE document provided by Oracle Customer Support:


To run the script, download the attachments of the note above and store them in a directory of your choice:


Open the extend.properties file in a text editor and adapt it to your environment:



The admin server of the domain should be up and running before adding additional managed servers. To run the script, start a command prompt window and set the domain environment for your existing domain:



Change to the directory containing the downloaded script and property file. To run the script, you can use the wlst.cmd|sh script which is provided with the WebLogic Server installation. The wlst.cmd|sh script is available in %MW_HOME%\wlserver_10.3\common\bin on Windows and $MW_HOME/wlserver_10.3/common/bin on Linux/Unix. Run the script:

  • wlst.cmd|sh extendOSBDomain.py



The script will analyze the cluster as defined in the extend.properties file and check which managed servers are already available. The prerequisite for this sample script is, that all managed server names have the same prefix like osb_server and that they are numbered sequentially, in my example osb_server1 to osb_server4. The script will create a new managed server osb_server5:



The script will also create the related JMS objects for the new managed server:


Wednesday Apr 25, 2012

Extending a SOA Domain to Include BAM

This post includes instructions and screen shots on how to extend a SOA domain to include BAM. We follow the SOA 11g EDG guide:

     Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite 11g Release 1 (11.1.1)
     Section 7.3 Extending the Domain to Include BAM
     http://docs.oracle.com/cd/E21764_01/core.1111/e12036/extend_bam.htm#CCHJFACD

The environment used had 2 physical hosts: BAMHOST1 and BAMHOST2. The steps were performed on BAMHOST1. Please refer to the following section in the EDG for instructions on how to propagate the domain to the other BAM server.

     Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite 11g Release 1 (11.1.1)
     Section 7.7 Propagating the Domain Configuration to BAMHOST1 and BAMHOST2 Using the
     pack/unpack Utility
     http://docs.oracle.com/cd/E21764_01/core.1111/e12036/extend_bam.htm#CFHBJGJJ


    1. Change directory to the location of the Configuration Wizard. It should be under the $ORACLE_COMMON_HOME/common/bin directory:

          Example: cd /u01/app/oracle/product/soa/common/bin
    	

    2. Start the Configuration Wizard:

           ./config.sh
    	

    3. In the Welcome screen, select Extend an existing WebLogic domain, and click Next.

    4. In the WebLogic Domain Directory screen, select the following WebLogic domain directory, $ORACLE_BASE/admin/domain_name/aserver/domain_name Example: /u01/app/oracle/product/admin/aserver/edg_domain.

    Click Next.


    (click image for full view)

    5. In the Select Extension Source screen, do the following:

      5.1 Select Extend my domain automatically to support the following added products
      • Oracle Business Activity Monitoring 11.1.1.0 [soa]

      Click Next.


      (click image for full view)

    6. The warning message CFGFWMK-64061 may appear. Select Replace existing component and click OK


    (click image for full view)

    7. In the Configure JDBC Component Schema screen do the following:

      7.1. Select BAM Schema.

      7.2. Select Configure selected component schemas as RAC multi data source schemas in the next panel.

      Enter values for the following fields:

      • Driver: Oracle driver (Thin) for RAC Service-Instance connections, Versions:10, 11.
      • Service Name: Enter the service name of the database; for example, ORCL
      • User Name: Enter the BAM complete user name for the schema; example DEV_ORABAM
      • Password: Enter the password to use to access the schema

      7.3. Click Add and enter the details for the first and second RAC instance. For example:

      • HostName: 10.0.10.89 (used SCAN address)
      • Instance Name: ORCL1
      • HostName: 10.0.10.89 (used SCAN address)
      • Instance Name: ORCL2

    Click Next.


    (click image for full view)

    8. In the Test JDBC Data Sources screen, the connections should be tested automatically. The Status column displays the results. Ensure that all connections were successful. Click Next.


    (click image for full view)

    9. In the Select Optional Configuration screen, select the following:

    • Managed Servers, Clusters, and Machines
    • Deployments and Services
    • JMS File Store

    Click Next.


    (click image for full view)

    10. In the Select JMS Distributed Destination Type screen, select UDD from the drop-down list for all Fusion Middleware Components' JMS Modules.

    11. In the Configure Managed Servers screen, rename the bam_server1 server to WLS_BAM1.


    (click image for full view)

    12. Click on Add and add a new server called WLS_BAM2. Give these servers the attributes shown in the picture.


    (click image for full view)

    13. In the Configure Clusters screen, add the following cluster:

    • Name: BAM_Cluster
    • Cluster Address: leave it empty


    (click image for full view)

    14. In the Assign Servers to Clusters screen, add WLS_BAM1 and WLS_BAM2 to the BAM_Cluster. Do not modify the other assignments that display in this screen; leave them as they are.


    (click image for full view)

    15. In the Configure Machines screen, do the following:

      15.1 Delete the LocalMachine that appears by default.

      15.2 Click the Unix Machine tab. You should add the BAMHOST1 and BAMHOST2 machines and have the following entries:


    (click image for full view)

    16. In the Assign Servers to Machines screen, do the following:

    • Assign WLS_BAM1 to BAMHOST1
    • Assign WLS_BAM2 to BAMHOST2

    Click Next.

    17. In the Target Deployments to Clusters or Servers screen, ensure the following targets:

    • usermessagingserver and usermessagingdriver-email should be targeted only to SOA_Cluster and BAM_Cluster. (The usermessaging-xmpp, usermessaging-smpp, and usermessaging-voicexml applications are optional.)
    • WSM-PM should be targeted only to WSM-PM_Cluster.
    • The DMS Application should be targeted to BAM_Cluster, SOA_Cluster, WSM-PM_Cluster and Admin Server.
    • Target the oracle.sdp.* library only to SOA_Cluster and BAM_Cluster. Target the oracle.soa.* library only to SOA_Cluster.
    • Target the oracle.rules.* library to SOA_Cluster, BAM_Cluster and Admin Server.
    • The oracle.wsm.seedpolicies library should be targeted only to the WSM-PM_Cluster.
    • oracle.bam* is targeted only to BAM_Cluster.

    Click Next.


    (click image for full view)

    18. In the Target Services to Clusters or Servers screen, ensure the following targets:

    • mds-owsm, mds-owsm-rac0, and mds-owsm-rac1 should be targeted to both WSM-PM_Cluster and AdminServer.
    • mds-soa, mds-soa-rac0, and mds-soa-rac1 should be targeted to both SOA_Cluster and AdminServer.
    • OraSDPMDatasource, OraSDPMDatasource-rac0, and OraSDPMDatasource-rac1 should be targeted to both SOA_Cluster and BAM_Cluster.

    Click Next.


    (click image for full view)

    19. In the Configuration Summary screen, click Extend.


    (click image for full view)

    20. In the Configure JMS File Stores screen, enter the shared directory location example: u01/app/oracle/admin/shared /jms

    21. In the Creating Domain screen, click Done.


    (click image for full view)

Wednesday Apr 18, 2012

Follow Up to SOA 11g Database Guide Webcast

On April 11th I presented a webcast talking about the SOA Suite 11g database guide. This post is a follow up to answer the questions asked and also provide the link for the presentation recording.

The presentation recording can by found here
(https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=ANNOUNCEMENT&id=740964.1)

The schedule for future webcasts can be found here
(https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=ANNOUNCEMENT&id=740966.1)

Questions


Q. I've just finished setting up partitioning for our SOA installation. My question is if we drop a partition for BRDECISIONINSTANCE table for example, how do we avoid violating constraints and FKs?

A. This is answered in the following documentation:

- Referential Integrity and Equipartioning (version 11.1.1.6)
(http://docs.oracle.com/cd/E23943_01/admin.1111/e10226/soaadmin_partition.htm#autoId3)


Q. I am working on an 11g upgrade (11.1.1.3.0 -> 11.1.1.5.0), and reviewing the 11.1.1.5.0 documentation, I do not explicitly see information on running the RCU for the BAM schema, so does this mean that there is no requirement to upgrade BAM in this version?

A. With RCU you would create new and empty schemas. As you want to upgrade your schemas from 11.1.1.3 to 11.1.1.5, the tool to do this is called Patch Set Assistant (PSA). After upgrading your software installation to 11.1.1.5, you would then use PSA to upgrade the schemas. I would recommend to check the related section in the guide 1384379.1:

Upgrade --> Updating SOA Schemas from 11g to a Later Patch Set
Check this section to understand the update process.
Then check the km document linked from there - Note 1325406.1 - Updating Repository Schemas for Oracle Fusion Middleware 11g with Patch Set Assistant (PSA) [Video]
This document has a video that explains step by step how to run PSA and what to do to update the schemas.

Finally, before actually running PSA, check section Which Schemas and Objects Need to be Upgraded? in the guide 1384379.1 to understand which schemas need to be updated if updating from 11.1.1.3 to 11.1.1.5. This information is available in the documentation linked from the guide.


Q. Is there also a way to programatically terminate long running composites? We have to many to manually terminate them?

A. These instances need to be terminated either manually in EM or via the API. Information is available in KM note 1400612.1 - How to Purge Active Instances ("Running" / "Recovery Needed" State) in the SOA Application.


Q. Q: I want to know basic to SOA. Can you send some links or doc id for basics of SOA?

A. This link to the Oracle SOA Suite, Business Process Management Suite, and Web Services Documentation Library is a good starting point:

http://docs.oracle.com/cd/E23943_01/soa.htm.


Q. How can we delete long running instances that will never complete?

A. These instances need to be terminated either manually in EM or via the API. Information is available in KM note 1400612.1 - How to Purge Active Instances ("Running" / "Recovery Needed" State) in the SOA Application


Thank you to everyone who attended and to anyone who views the recording. If there are further questions or discrepancies please add a comment to this post for update.

Thursday Apr 05, 2012

Upcoming Customer WebCast: SOA 11g Database: Guide for Administrators

The SOA infrastructure database is used by SOA Suite products like BPEL PM, BAM, BPM, Human Worklow, B2B and Mediator. A SOA administrator is involved in many different tasks like installation, upgrade, performance tuning and other administrative topics. Another important one is purging - see the posting for this: SOA Suite 11g Purging Guide.

We have implemented a guide to help with thess tasks: SOA 11g Infrastructure Database: Installation, Maintenance and Administration Guide.

An upcoming advisor webcast planned for Wednesday, April 11 2012 at 15:00 UK / 16:00 CET / 07:00 am Pacific / 8:00 am Mountain / 10:00 am Eastern will walk you through the guide and show some of the highligts. Registration for this webcast is available in SOA 11g Database: Guide for Administrators [ID 1422913.1].

The presentation recording can by found here after the webcast.
(https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=ANNOUNCEMENT&id=740964.1)

The schedule for future webcasts can be found here
(https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=ANNOUNCEMENT&id=740966.1)

Friday Mar 30, 2012

SOA Suite 11g Purging Guide

We now have a single source of truth concerning Purging in My Oracle Support. The material is contained within the SOA 11g Infrastructure Database: Installation, Maintenance and Administration Guide under the 'Purging' tab.

All of the previous purge related content for 11g is now deprecated and many of the documents will redirect to this Guide while others simply contain a disclaimer.

What does the Guide contain?

  • Summary Overview of Purging. What it does and why it's important
  • Specific information on each release of 11g
  • Available patches for each release of 11g and recommendations
  • How to run the different purge scripts
  • Tips on improving performance
  • How to begin troubleshooting problems with the process
  • How to identify orphaned records
  • Useful reference information


Here are a couple of screen shots to help with navigation:

Guide Landing Page:


(click image for full view)


Select the 'Purging' tab:


(click image for full view)


The left menu contains the following options:
  • Alternative: Database Partitioning
  • What to do on 11gR1 GA (11.1.1.1)
  • What to do on PS1 (11.1.1.2)
  • What to do on PS2 (11.1.1.3)
  • What to do on PS3 (11.1.1.4)
  • What to do on PS4 (11.1.1.5)
  • Overview of PS5 (11.1.1.6)
  • Purging Step by Step
  • Performance Tips
  • Troubleshooting Purge
  • Orphaned Records
  • Reference

This resource goes hand in hand with the excellent documents SOA 11g Database Growth Management Strategy and Start Small, Grow Fast available on OTN.

The latest product documentation can be found here.

Friday Mar 09, 2012

Follow Up to SOA Selective Tracing Webcast

On March 7th I presented a webcast on how to use Selective Tracing with SOA Suite 11g. This post is a follow up to answer the questions asked and also provide the link for the presentation recording.

The presentation recording can by found here
(https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=ANNOUNCEMENT&id=740964.1)

The schedule for future webcasts can be found here
(https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=ANNOUNCEMENT&id=740966.1)

There is a mistake in the slides on where to start WLST from. It should be started from 'oracle_common/common/bin', NOT wlserver_10.3/common/bin.

Questions


Q. Can the loggers for selective tracing participation be chosen through the WLST interface?

A. Yes. The loggers can be enabled or disabled using the WLST 'configureTracingLoggers' command. Full documentation on the WLST interface for Selective Tracing can be found here
(http://www.art2dec.com/documentation/docs/fmw11g1115documentation/web.1111/e13813/custom_logging.htm#CEGIJECA)


Q. What is the best way to trace a login process?

A. Selective Tracing is only effective for ODL (Oracle Diagnostic Logging) loggers. Give that the actual login process is mostly handled by WebLogic Server, Selective Tracing will not capture this information because WLS does not implement ODL. To capture data about a login it is recommended to enable the WLS Authentication and Authorization debug loggers through the WLS console.


Q. Can tracing be enabled for WebLogic Server 10.3.5 for a particular managed server?

A. From Enterprise Manager Selective Tracing is a set at the domain level, however, the WLST interface offers an option on many of the commands called 'target'. Here you may specify a particular managed server for the tracing session. More information can be found in the product documentation referenced above. Note that a WLS only installation will not have the 'oracle_common' folder and without this Selective Tracing is unavailable.


Thank you to everyone who attended and to anyone who views the recording. If there are further questions or discrepancies please add a comment to this post for update.

Friday Mar 02, 2012

How to Reset a SOA 11g DMS Metric

What is DMS?

DMS stands for 'Dynamic Monitoring Service' and is a facility through which WebLogic Server and many of our deployed applications expose runtime information. At the top level there is a list of 'Nouns' and these Nouns have attributes where the specific values are populated.

To view the runtime DMS you can access the following URL on any running WebLogic instance:

http://<host>:<port>/dms/Spy

Login using the administrative credentials and you will see the following screen.


(click image to enlarge)


If SOA is deployed and running on the instance you will see a list of SOA related Nouns like the following:


(click image to enlarge)


Some of these simply state what is deployed such as the composite names, components, etc. Others provide runtime metrics for the SOA components such as the number of requests processed, the average time of those requests, etc. Most of these metrics are aggregated across composites and components.


Why Reset a Metric?


There could be several reasons for resetting a particular metric at runtime but the use case of concern here is when you have configured a WLDF Watch to monitor for some state. Here we are monitoring the average processing time of a BPEL Process in the 'soainfra_component' Noun. When the average time exceeds 5 seconds we want to trigger a Diagnostic Framework Incident and then we want to reset the Noun so we can continue monitoring it without triggering the Watch over and over and don't have to restart the server.

Here is what the metric looks like in Spy:


(click image to enlarge)


Our avg time is 1545 milliseconds. We run some load and push the avg processing time over our threshold of 5 seconds.


(click image to enlarge)


We'll assume that the Incident is generated and now we want to reset this particular metric. To do this we pass in some arguments to the Spy servlet through the URL.

Arguments:
  • operation: What operation do we want to perform?
  • format: What format is the data in
  • cache: What action to take on the cached data
  • name: The name of the object we want to reset
  • recurse: Do we want the reset to be recursive

Here are our values:
  • operation = reset
  • format = raw
  • cache = refreshall
  • name = <discussed below>
  • recurce = all

The 'name' is quite long and one way to get it is directly from the WLDF Watch configuration. Here is the expression that was used to create the Watch taken from the WLS console:


(click image to enlarge)


We're going to copy the 'name' from here and paste it into our reset URL. Here is the complete URL:

http://<HOST>:<PORT>/dms/Spy?operation=reset&format=raw&cache=refreshall&name=/soa_cluster_prod_jrockit_7001/soa_server1/soainfra/default/TestProject2/1.0/soa_a684ec4b-6c01-4901-979b-7c6b44bdee07/bpel/BPELProcess2&recurse=all

Every environment will be different and the name will change upon redeployment of the project.

An alternative approach is to build the 'name' value manually. It takes the form:

/<DOMAIN NAME>/<SERVER NAME>/<PROJECT DEPLOYMENT PATH>/<COMPOSITE NAME>/<COMPOSITE REVISION>/<COMPOSITE LABEL>/<COMPONENT TYPE>/<COMPONENT NAME>

The following fields can be pulled directly from the soainfra_component table in DMS Spy:
  • COMPOSITE NAME is the 'soainfra_composite' column
  • COMPOSITE REVISION is the 'soainfra_composite_revision' column
  • COMPOSITE LABEL is the 'soainfra_composite_label' column
  • COMPONENT TYPE is the 'soainfra_component_type' column
  • COMPONENT NAME is the 'Name' column


These fields can change depending in the DMS metric used so WLDF can help for establishing the template to be used going forward.

We paste the URL into our browser and make the request. Refreshing the metric in Spy we see that it has been reset:


(click image to enlarge)


We'll take a quick look at the 'soainfra_Binding' metric to confirm that only soainfra_component was reset:


(click image to enlarge)


You can reset all metrics with the following URL:

http://<HOST>:<PORT>/dms/Spy?operation=reset&format=raw&cache=refreshall&name=/&recurse=all


I hope this post is helpful to anyone interested in working with the DMS metrics and sheds some light on how they work.

Monday Feb 27, 2012

Policy Authorization Example in SOA Suite 11g

Use Case:

We have a composite that we want to limit access to.  We will use HTTP basic authentication and an authorization policy to ensure that access is only granted to users who are members of a particular group.

We will use the WebLogic Server Console to create our users and group.  Authentication and Authorization for the composite will be entirely configured in Enterprise Manager with notes on how some steps can also be done in JDeveloper. Note that all screenshots were taken using 11.1.1.6 (PS5).


Configure the Users and Group

(No screenshots for this section but they will be used extensively in the following sections)
  1. Login to the WLS console ('http://<host>:<port>/console')
  2. In the left menu select 'Security Realms'
  3. Select the realm where you want to create the users and groups.  The default is 'myrealm'
  4. At the top select the 'Users and Groups' tab
  5. You'll start with 'Users' so click 'New' and enter your user name and pwd.  Create as many users as you want.but here we are using 'Bob1', 'Bill1' and 'jane'
  6. Go to the 'Groups' tab and create a new group.  Here we're using 'Group1'
  7. Go back to the users and select 'Bob1'
  8. Select the 'Groups' tab and add 'Group1'.  Do the same for Bill1. We're gong to intentionally leave 'jane' out of the group.

You've got your users and groups configured

If you haven't already done so, deploy your composite now.



Configuration in Enterprise Manager (EM)

The EM configuration is comprised of the following steps:
  1. Add a Domain Credential
  2. Add an Application Role
  3. Add an Application Policy that assigns the Application Role a specific permission
  4. Add 3 WS Policies to the project

Let's first add a domain Credential.  From the left menu expand the domains and right click on the domain name

1.  Add Domain Credential


1.1) Login to EM

1.2) Select 'Security' -> 'Credentials'



(click image for full view)



1.3) Select 'Create Map'




(click image for full view)



1.4) Enter the map name as 'oracle.wsm.security'




(click image for full view)



1.5) Click 'OK'

1.6) Highlight the new Map and select 'Create Key'




(click image for full view)



1.7) Enter the key name as 'basic.credentials'

1.8) Enter the user name and pwd, we're using the admin user 'weblogic' here




(click image for full view)



1.9) Click OK and your Credentials should now look like this:




(click image for full view)



(back to top)

The next steps in our configuration are to configure the Application Role and Application Policy.  These will be used by the Authorization policy.

2.  Create the Application Role


2.1) In the left menu right click the domain name

2.2) Select 'Security' -> 'Application Roles'




(click image for full view)



2.3) Select 'soa-infra' in the 'Application Stripe' drop down

2.4) Select 'Create' as we are going to create a new Application Role




(click image for full view)



We're going to name our new role 'GroupOneRole'

2.5) Under Members click 'Add'




(click image for full view)



The Type should be 'Group'

2.6) Search and select Group1 which we created earlier

2.7) Click 'OK'




(click image for full view)



You should now have Group1 in your Members list.


(click image for full view)



(back to top)

3.  Create the Application Policy


3.1) Right click on the domain name again

3.2) Select 'Security' -> 'Application Policies'




(click image for full view)



The 'Application Stripe' is 'soa-infra'
The 'Principal Type' is 'Application Role'

3.3) Search

3.4) Click 'Create'




(click image for full view)



3.5) Under 'Permissions' click 'Add'




(click image for full view)



3.6) Immediately click the 'Continue' button to get to the custom entry form

Intuitively it seems that the selections here are needed but they're actually not for what we want to do.


(click image for full view)



3.7) For 'Permission Class' enter 'oracle.wsm.security.WSFunctionPermission'

3.8) We're going to cheat a bit and enter '*' for both Resource Name and Permission Actions.  In an actual implementation you would probably specify the web service and relevant actions.




(click image for full view)



3.9) Click 'Select' and here's what we have for Permissions:




(click image for full view)



3,10) Under 'Grantee' click 'Add'




(click image for full view)



3.11) Search with the defaults and select 'GroupOneRole'

3.12) Click 'OK'




(click image for full view)



Your 'Create Application Grant' screen should now look like this:


(click image for full view)



3.13) Click 'OK' at the top right and confirm that the 'GroupOneRole' Principal appears in the list




(click image for full view)



(back to top)

We're now ready to add the policies to the project

4.  Add WS Policies to Project


4.1) Right click on the project name

4.2) Select 'Policies'




(click image for full view)



Here we see that the project has no policies associated with it.  We're going to add 3.

4.3) Select 'Attach To/Detach From'




(click image for full view)



Depending on the complexity of your project you will likely have more components than this.  Here we're going to select the web service that is the entry point for our composite, 'bpelprocess2_client_ep'.  The following window opens.


(click image for full view)



We're going to add 3 policies:

  • 'oracle/wss_http_token_service_policy' for authentication
  • 'oracle/log_policy' for logging the policy activities
  • 'oracle/binding_permission_authorization_policy' for authorization
All of these policies can be added to the web service in JDeveloper by right clicking on the service in the composite design view and selecting 'Configure WS Policies...'. The form is similar to what is shown here in EM.

4.4) Highlight the selections from the list and click 'Attach'.  When completed your 'Directly Attached Policies' should look like this:




(click image for full view)



4.5) Select 'Validate' and then 'OK'

Your policies list should now look like this:


(click image for full view)



The configuration is complete.

(back to top)

For testing we're using JMeter, submitting the request along with the HTTP authentication header.

I won't get into the JMeter configuration but will  provide the responses for two requests.  Let's first try our user 'Bob1'.

HTTP Authorization header value is 'Basic Qm9iMTp3ZWJsb2dpYzE='  (this is the Base64 encoding of 'Bob1:weblogic1')

Response from our server:




(click image for full view)



Now let's try user jane who exists in the domain but is not a member of Group1

HTTP Authorization header value is 'Basic amFuZTp3ZWJsb2dpYzE='  (Base64 encoding of 'jane:weblogic1')

Response from server:




(click image for full view)



Here we see the response code 403 which means the resource is forbidden to the authenticated requester.

In our server standard out we see the following error message:

<Error> <oracle.wsm.resources.security> <WSM-00045> <HTTP authentication/authorization failure.>



I hope this post is helpful for anyone trying to enable authorization for their SOA 11g  composite applications.  It's a very simply example but perhaps will serve as a good starting point.  In the future we may add the complexity in follow up posts.


(back to top)



Wednesday Feb 22, 2012

Introduction to SOA Information Centers

What is an Information Center (IC)?
Information Centers are meant to be your product landing page on My Oracle Support to see what's new, find useful links and hopefully avoid issues. They are specialized documents in our Knowledge Base that aggregate and organize the latest and most relevant information for a product or topic.  Each IC is made up of labeled subsections that display a list of content items.  Some of these subsections are dynamic, automatically picking up new content and dropping aged documents, while others are statically populated.  In either case we do our best to keep all of the content up to date.

Information Centers are product centric and grouped as such.  There will be an Overview IC for the product and a menu containing the associated IC's such as 'Troubleshoot' and 'Install and Configure'.  These documents are handled as a group and ultimately each product should have it's own group of IC's.


What are the Available SOA Information Centers?
The SOA Information Centers are organized in a hierarchical fashion starting with 'Service Oriented Architecture' at the top.  We currently have only a subset of the products covered but will be publishing additional IC's soon.  We've tried to make the navigation between IC's intuitive and simple.

These SOA IC's are currently available:


As we work to make our Information Centers more useful we would appreciate any feedback you have on what works and what doesn't.  At the end of the day they exist to meet your needs and we are here to see that they do.


Monday Feb 13, 2012

Diagnose SOA Suite 11g Issues Using RDA (Remote Diagnostic Agent)

  • RDA is a common tool to collect diagnostic data for Oracle products. Administrators of the Oracle Database will already know it.
  • RDA is easy to install and use
  • Recent versions of RDA (>= 4.26) provide a comprehensive set of analysis data for SOA Suite 11g to analyze different types of issues.
  • Diagnostic data can be viewed in a browser and is also available in a zip file to be uploaded to a Service Request.
  • Use RDA to minimize resolution time for SRs and avoid upload requests for basic diagnostic and product information by uploading a RDA collection while creating your SR!
ยท
  • RDA is a common tool to collect diagnostic data for Oracle products. Administrators of the Oracle Database will already know it.
  • RDA is easy to install and use
  • Recent versions of RDA (>= 4.26) provide a comprehensive set of analysis data for SOA Suite 11g to analyze different types of issues
  • Diagnostic data can be viewed in a browser and is also available in a zip file to be uploaded to a Service Request
  • Use RDA to minimize resolution time for SRs and avoid upload requests for basic diagnostic and product information by uploading a RDA collection while creating your SR!
  • [Read More]

    Thursday Feb 09, 2012

    Welcome to the SOA Proactive Support Blog

    Welcome to the SOA Proactive Support blog.  This is our first post and as such it is an opportunity to introduce ourselves and our mission.

    Who We Are
    We are a small team of support engineers based in both Europe and the United States.  Our expertise covers SOA products from OSB to BPEL to Human Workflow but we work for all products in the SOA stack. We've been in existence for about a year now but have been less visible than we would like to be.


    Our Mission

    • Improve the customer experience
    • Enable customers to avoid / prevent issues when working with our products
    • Enable faster resolution of problems when they occur


    Our Activities

    • Enhancement and maintenance of our knowledgebase
    • Improving product diagnostic capabilities
    • Improvements to the product documentation
    • Coordination with Product Management and Development
    • Outreach to improve awareness of new documents, tools, etc.
    • Maintain an open channel for feedback


    Our hope is that this blog will serve as a two-way communication channel. Although we obviously want new resources to be utilized we are also very interested in feedback on what we can improve. Many suggestions we can act on immediately while others may take more time but all of them will be acknowledged and followed up on.

    Although there are many specific activities that could be discussed here we will leave them for their own posts. Thank you for your time and we look forward to both informing and working with you.

    About

    This is the official blog of the SOA Proactive Support Team. Here we will provide information on our activities, publications, product related information and more. Additionally we look forward to your feedback to improve what we do.

    Search

    Categories
    Archives
    « April 2014
    SunMonTueWedThuFriSat
      
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
       
           
    Today