Monitoring at service bus

Hello,
I need to monitor the performance of bpel processes and I am using service bus. I want to know if it's possible to monitor for example the response time for one instance (not avg, max, etc..)? And if a violation occurs to able to see it exactly the time it occurs? I want to know if I can define such an alert because with the SLA alerts it is not possible to define it.

>
I want to know if it's possible to monitor for example the response time for one instance (not avg, max, etc..)?
>
I guess that by "one instance" you probably mean "one request". As far as I know there is no such feature in OSB. However, there is access.log in WebLogic which could be probably used to track individual requests.
>
And if a violation occurs to able to see it exactly the time it occurs? I want to know if I can define such an alert because with the SLA alerts it is not possible to define it.
>
You will only see the time when your SLA rule was evaluated. That's how it goes with OSB and its Aggregator.

Similar Messages

  • Oracle Service Bus: Monitoring/Tracking Consumer Services?

    Hi,
    since we have a Oracle Service Bus and a Oracle Service Registry, is there any standard solution for tracking which consumer services/applications are accessing which provider services? What we need is monitoring the applications (consumer) which are accessing an specific service (provider) registered in the OSB. Is it possible to have this information as monitoring/statistical data in the Oracle Service Bus console? if not, any suggestion to implement such behaviour ?
    Thank you in advance,
    Antonio.

    I would like to have (don't know where) a list with all my consumer services (outside OSB) and so map them with the accessed proxy services (providers on OSB). The aim for this functionality is being able to monitor which consumer services from outside the OSB (then I need a place where these services can be identified and listed) are accessing specific proxy services published as providers on the OSB. Is like "well, I have my proxies published on the OSB, but I need to know WHO (consumers outside the OSB) is accessing to them?". I don't know if such functionality is provided by the Oracle Service Registry or the Service Bus, or it's just a custom implementation without any Oracle product.
    Thank you for your help Manoj!
    Antonio.

  • Error using the test console of the Oracle Service Bus 11gR1

    Hi I am facing a an issue while using the test console of the Oracle Service Bus 11gR1 .
    Every time I try to execute a business service or a proxy service I end up getting the following message.
    Error Accessing Test Configuration
    *"Test Console" service is not running. Contact administrator to start this service.*
    In fact to add to my frustration I am unable to execute any of my proxy services from outside clients like SOAPUI as well.
    Is anyone else facing this too ??
    Also every time the server starts I can see some diagnostic error messages on my Eclipse console.
    *[ERROR] AdapterManager - ServletContainerAdapter manager not initialized correctly.*
    Attached the whole log at the end below.
    To provide an update on my trouble shooting
    1. ) I tried to give the IntegrationAdmin and IntegrationDeployer roles to my admin user. in fact i also tried to give it all the possible privileges.
    Result: Still the same error message.
    Error Accessing Test Configuration
    "Test Console" service is not running. Contact administrator to start this service.
    2.) I have already tried to change the following entry <java:alsb-test-console-debug>true</java:alsb-test-console-debug> in my C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\alsbdebug.xml
    I am also attaching the file contents here
    <java:sb-debug-logger xmlns:java="java:com.bea.wli.debug">
    <java:alsb-stages-transform-runtime-debug>false</java:alsb-stages-transform-runtime-debug>
    <java:alsb-alert-manager-debug>false</java:alsb-alert-manager-debug>
    <java:alsb-credential-debug>false</java:alsb-credential-debug>
    <java:alsb-jms-reporting-provider-debug>false</java:alsb-jms-reporting-provider-debug>
    <java:alsb-management-credential-debug>false</java:alsb-management-credential-debug>
    <java:alsb-management-dashboard-debug>false</java:alsb-management-dashboard-debug>
    <java:alsb-management-debug>false</java:alsb-management-debug>
    <java:alsb-management-user-mgt-debug>false</java:alsb-management-user-mgt-debug>
    <java:alsb-module-debug>false</java:alsb-module-debug>
    <java:alsb-monitoring-aggregator-debug>false</java:alsb-monitoring-aggregator-debug>
    <java:alsb-monitoring-debug>false</java:alsb-monitoring-debug>
    <java:alsb-pipeline-debug>false</java:alsb-pipeline-debug>
    <java:alsb-security-wss-debug>false</java:alsb-security-wss-debug>
    <java:alsb-service-account-manager-debug>false</java:alsb-service-account-manager-debug>
    <java:alsb-service-provider-manager-debug>false</java:alsb-service-provider-manager-debug>
    <java:alsb-service-repository-debug>false</java:alsb-service-repository-debug>
    <java:alsb-service-security-manager-debug>false</java:alsb-service-security-manager-debug>
    <java:alsb-service-validation-debug>false</java:alsb-service-validation-debug>
    <java:alsb-test-console-debug>true</java:alsb-test-console-debug>
    <java:alsb-transports-debug>false</java:alsb-transports-debug>
    <java:alsb-uddi-debug>false</java:alsb-uddi-debug>
    <java:alsb-wsdl-repository-debug>false</java:alsb-wsdl-repository-debug>
    <java:alsb-wspolicy-repository-debug>false</java:alsb-wspolicy-repository-debug>
    <java:alsb-security-encryption-debug>false</java:alsb-security-encryption-debug>
    <java:alsb-security-module-debug>false</java:alsb-security-module-debug>
    <java:alsb-sources-debug>false</java:alsb-sources-debug>
    <java:alsb-custom-resource-debug>false</java:alsb-custom-resource-debug>
    <java:alsb-mqconnection-debug>false</java:alsb-mqconnection-debug>
    <java:alsb-throttling-debug>false</java:alsb-throttling-debug>
    <java:alsb-flow-resource-debug>false</java:alsb-flow-resource-debug>
    <java:alsb-flow-transport-debug>false</java:alsb-flow-transport-debug>
    <java:alsb-flow-deployment-debug>false</java:alsb-flow-deployment-debug>
    <java:alsb-debugger-debug>false</java:alsb-debugger-debug>
    <java:alsb-console-debug>false</java:alsb-console-debug>
    <java:alsb-result-caching-debug>false</java:alsb-result-caching-debug>
    <java:alsb-bpel-debug>false</java:alsb-bpel-debug>
    <java:alsb-jca-framework-adapter-debug>false</java:alsb-jca-framework-adapter-debug>
    </java:sb-debug-logger>
    starting weblogic with Java version:
    java version "1.6.0_18"
    Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
    Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
    Starting WLS with line:
    C:\Oracle\MIDDLE~1\home11g\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3\server -Ddomain.home=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1 -Dcommon.components.home=C:\Oracle\MIDDLE~1\home11g\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Oracle\MIDDLE~1\home11g\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\AdminServer -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\home11g\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\home11g\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\home11g\patch_wls1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\home11g\patch_oepe1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\home11g\patch_ocp353\profiles\default\sysext_manifest_classpath weblogic.Server
    <30-Jun-2010 16:22:43 o'clock BST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 16.0-b13 from Sun Microsystems Inc.>
    <30-Jun-2010 16:22:47 o'clock BST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
    <30-Jun-2010 16:22:48 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <30-Jun-2010 16:22:48 o'clock BST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <30-Jun-2010 16:22:49 o'clock BST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <30-Jun-2010 16:22:49 o'clock BST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log00005. Log messages will continue to be logged in C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log.>
    <30-Jun-2010 16:22:49 o'clock BST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
    <30-Jun-2010 16:22:56 o'clock BST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <30-Jun-2010 16:22:58 o'clock BST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <30-Jun-2010 16:22:58 o'clock BST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\access.log00005. Log messages will continue to be logged in C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\access.log.>
    <30-Jun-2010 16:23:06 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <30-Jun-2010 16:23:06 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <30-Jun-2010 16:23:59 o'clock BST> <Warning> <JDBC> <BEA-001110> <No test table set up for pool "wlsbjmsrpDataSource". Connections will not be tested.>
    <30-Jun-2010 16:23:59 o'clock BST> <Warning> <JDBC> <BEA-001552> <The Logging Last Resource (LLR) data source wlsbjmsrpDataSource will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.>
    <30-Jun-2010 16:25:35 o'clock BST> <Alert> <OSB Security> <BEA-387068> <There is no PKI credential mapper provider configured in your security realm. Service key provider management will be disabled. Configure a PKI credential mapper provider if you need service provider support. This is typically the case if you have Oracle Service Bus proxy services with web service security enabled or outbound 2-way SSL connections.>
    <30-Jun-2010 16:25:40 o'clock BST> <Warning> <WliSbTransports> <BEA-381917> <MQ Transport could not be registered due to : Missing MQ Library>
    [ERROR] AdapterManager - ServletContainerAdapter manager not initialized correctly.
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\OSB_domain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\OSB_domain.log00005. Log messages will continue to be logged in C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\OSB_domain.log.>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.128.2.170:7001 for protocols iiop, t3, ldap, snmp, http.>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "OSB_domain" running in Development Mode>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    This is really putting me off and its really disappointing to see all these issues in this new release.
    How can oracle let a release slip in with such a Major Issue.
    Please can any one help or provide a work around atleast.
    Regards
    Nitin

    I guess till version 10gr3.1 you only needed to start one server and it allowed to access both admin and service bus console.Yes, in 11g as well you may access the admin and OSB console by just starting the admin server but in 11g OSB configuration gets deployed on OSB server (managed server) and test service also runs over this server.
    Are you saying there is some other server I need to start just for running the test console ????Yes. Managed server osb_server1 needs to be started for deploying, testing and accessing OSB resources.
    As If the OSB server was not running how can I check my published services, modify them and do all the bits and pieces after opening the open the service bus console but not just test them???You can modify and save your configuration without staring OSB server but if you will check in change centre then all the changes being done without starting OSB server will remain in partially activated state.
    I have been using the service bus for 3 years and I have never faced any such issue.With each new release you may get new features and with a major release like 11g, architecture and functionality may change.
    If it all there is some other server I need to start then whats the process to do so ??Open command prompt. Navigate to $Domain_Home/bin and run command
    startManagedWeblogic.cmd <nameOfManagedServer>
    for eg. -
    D:\OFMW11g\mw\user_projects\domains\ofmw_domain\bin>startManagedWebLogic.cmd osb_server1
    Once this server is up and running, try using test console.
    Regards,
    Anuj

  • Enterprise Business Services and Oracle Service Bus

    Hi,
    We are using AIA and we have developed a number of EBS’. These are composite applications containing a mediator and are deployed to the SOA Server.
    Am I right in saying that another option is to use the Oracle Service Bus and replace the composite application ESB’s with ESB’s in the Oracle Service Bus?
    Robert

    Gerhard,
    I was thinking the benefits would be:
    -     End point Virtualisation – Single end point for services we can configure.
    -     Move the job of wiring the integrations from Development to Admin
    -     Single point of monitoring for SLA’s and QOS
    -     Improve visibility of ESB’s by providing a single list. (At the moment they are amongst many services in enterprise manager.)
    At the moment we have 3 SOA servers connected to 6 systems. (Dev, Test and Prod) I was imagining it might be possible to have a single OSB with Service routing controlled by policies. This way we would not need three OSB setup’s.
    I am also charged with planning for the development of further services and we already have a long list of composites in enterprise manager. I am imagining that this will quickly become unmanageable. With OSB we could hide the downstream services and only show the EBS’.
    I also imagined that when we introduced a 11.1.1.6 SOA server we could simply adjust the routing rules at the OSB to set up a dev environment. Test out the new services work, then make similar adjustments on a per EBS basis until we have migrated completely to 11.1.1.6.
    I agree that there are a lot of trade off’s and I do not really have the experience to weigh up the balance between the two. Yesterday I was asked to come up with methods of monitoring performance of the current integration as well as future integrations and the OSB data sheet talks a little bit about this which is why I am thinking more about it; Although have only got as far as looking at the OSB data sheet and some manuals.
    I guess another option would be to go with some EBS’s as mediators and others on OSB but I think using a consistent method for EBS’s would be preferable.
    Also there is the question do we have one OSB for all systems or separate OSB’s for Dev, Test and Prod.
    Robert

  • Service Bus(OSB) not harvesting Endpoint to Enterprise Repository(OER)

    Hi,
    I am harvesting a WSDL-based HTTP Proxy Service from Oracle Service Bus (OSB) to Oracle Enterprise Repository (OER) but the Endpoint is not harvested. The other artifacts are harvested successfully.
    Can someone please help
    Thanks,
    Umar

    Hi Anuj,
    Here is the info you requested:
    *1. Exactly which version of OSB and OER are you using?*
    OSB version: Oracle Service Bus 11.1 Sun Dec 18 03:49:34 PST 2011 1447174
    OER version: Oracle® Enterprise Repository 11.1.1.6.0 (v11.1.1.6.0-111103_0001-1437995)
    *2. What type of proxy services are you publishing?*
    Proxy Type: Web Service - SOAP 1.1 (WSDL:OSB_PR_POC/OpenAccount, port="OpenAccountServicePort")
    My proxy service routes to business service.
    *3. If it is a WSDL based proxy then are you able to see enpoint URL in exported WSDL from proxy?*
    OSB shows the Endpoint information(Endpoint URI      /OSB_PR_POC/PS_OpenAccount)
    I don't exactly understand what you mean by 'exported WSDL'
    *4. Did you harvested the configuration from OSB machine itself?*
    The OSB and OER are on the same machine. Used the OSB command line harvester to harvest the project. So, Yes, harvested the configuration from OSB machine.
    *5. Can you provide the harvesting log?*
    Please find below the logs:
    E:\Oracle\Middleware\Oracle_OSB1\harvester>"C:\PROGRA~1\Java\JDK17~1.0_0\bin\java"     -Dweblogic.home="E:\Oracle\MIDDLE~1\WLSERV~1.3" -Dosb.home="E:\
    Oracle\MIDDLE~1\ORACLE~2" com.oracle.oer.sync.framework.Introspector -harvester_home "E:\Oracle\MIDDLE~1\ORACLE~2\harvester"
    log4j:WARN No appenders could be found for logger (org.apache.axis.i18n.ProjectResourceBundle).
    log4j:WARN Please initialize the log4j system properly.
    +0 [main] INFO com.oracle.oer.sync.framework.MetadataManager - Oracle Enterprise_Repository_Harvester version: v11.1.1.6.0-111020_0001-1434818+
    +250 [main] INFO com.bea.alsb.harvester.container.OSBInstance - OSB Harvester created a temporary directory (C:\Users\c74945\AppData\Local\Temp\3\OS+
    B11gConfig) for the configuration framework data. This directory will not be automatically deleted.
    +<Aug 29, 2012 12:03:21 PM AST> <Info> <OSB Offline> <BEA-000000> <Initialing ALSB in offline mode. Install dir: E:\Oracle\MIDDLE~1\ORACLE~2 config dir+
    +: C:\Users\c74945\AppData\Local\Temp\3\OSB11gConfig>+
    +<Aug 29, 2012 12:03:23 PM AST> <Alert> <OSB Security> <BEA-387042> <There is no user password credential mapper provider configured in your security r+
    ealm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service acc
    ount support.>
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "Resource SDK".>+
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "Resource SDK" initialized.>+
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "Custom Resource SDK".>+
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "Custom Resource SDK" initialized.>+
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "XSLT Resource".>+
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "XSLT Resource" initialized.>+
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "XML Schema Resource".>+
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "XML Schema Resource" initialized.>+
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "MFL Resource".>+
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "MFL Resource" initialized.>+
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "WS-Policy Resource".>+
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "WS-Policy Resource" initialized.>+
    +<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "WSDL Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "WSDL Resource" initialized.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "XQuery Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "XQuery Resource" initialized.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "JCA Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "JCA Resource" initialized.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "XML Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "XML Resource" initialized.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "Archive Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "Archive Resource" initialized.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "JNDI Provider Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "JNDI Provider Resource" initialized.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "SMTP Server Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "SMTP Server Resource" initialized.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "Proxy Server Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "Proxy Server Resource" initialized.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "Global Settings Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "Global Settings Resource" initialized.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "UDDI Registry Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "UDDI Registry Resource" initialized.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397037> <Initializing Proxy Service Repository>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397038> <Proxy Service Repository Intialized>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397039> <Initializing Business Service Repository>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397040> <Business Service Repository Intialized>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "FLOW Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "FLOW Resource" initialized.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "Resource SDK".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "Resource SDK" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "Custom Resource SDK".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "Custom Resource SDK" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "XSLT Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "XSLT Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "XML Schema Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "XML Schema Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "MFL Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "MFL Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "WS-Policy Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "WS-Policy Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "WSDL Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "WSDL Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "XQuery Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "XQuery Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "JCA Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "JCA Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "XML Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "XML Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "Archive Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "Archive Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "JNDI Provider Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "JNDI Provider Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "SMTP Server Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "SMTP Server Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "Proxy Server Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "Proxy Server Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "Global Settings Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "Global Settings Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "UDDI Registry Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "UDDI Registry Resource" started.>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <Monitoring> <BEA-000000> <New Metadata version is 0>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "FLOW Resource".>+
    +<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "FLOW Resource" started.>+
    +<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390020> <Config Service is initializing for the first time>+
    +<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Project System>+
    +<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Project _static>+
    +<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Project default>+
    +<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Folder System/JNDI Providers>+
    +<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Folder System/Operator Settings>+
    +<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Folder System/Proxy Servers>+
    +<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Folder System/SMTP Servers>+
    +<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Folder System/UDDI>+
    +<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390022> <Creating out-of-the-box resource: Operations System/Operator Settings/GlobalOperationa+
    lSettings>
    +8393 [main] INFO com.bea.alsb.harvester.plugin.reader.OSBReader - OSB Config Jar Import / Validation starting.+
    +10452 [main] INFO com.bea.alsb.harvester.plugin.reader.OSBReader - OSB Config Jar Import / Validation complete.+
    +61402 [main] INFO com.oracle.oer.sync.framework.MetadataManager - Successfully completed the harvest+
    Starting OERWriter Shutdown and Clean up...
    Let me know if you need anymore info.
    Thanks.

  • Oracle Service Bus (OSB), Eclipse --- and statement of direction

    Can somebody please explain what this means in: http://www.oracle.com/technology/products/integration/service-bus/docs/Oracle-Service-Bus-SOD.pdf
    +...The web-based console was complemented in the 3.0 release with full IDE support in Eclipse. The Eclipse capabilities will be ported to Oracle JDeveloper to provide a one-stop IDE for all SOA design needs. Until that port is complete, customers will still be able to use the Eclipse environment as IDE (in addition to the web-based console)...+
    More specifically: what will happen to the Eclipse OSB plugin/workshop once the JDeveloper port is complete?
    A) will it cease to exist and/or be terminated?
    B) will it remain as is, without keeping the functionality in synch with new stuff in JDev?
    C) will it continue to evolve side-by-side with JDev?
    Thx,
    -J.

    I think it is clear that Oracle will remain commited to Eclipse in terms of deploying java applications to WebLogic, they will provide some plugins for some time to come. You will however see oracle specific products, such as OSB, Portal, etc removed from Eclipse and ported to JDev. The reason for this is that Oracle can release new releases within their timeframe. If Oracle rely on Eclipse to deliver some functionality before they can release new products then they will be doing their customers a disservice.
    This statement in the SOD clearly states that JDev is the strategic platform and the Eclipse IP will be ported to JDev in the future:
    Design-Time Environment
    JDeveloper is the IDE of choice for SOA development at Oracle. AquaLogic Service Bus users have traditionally been using the web-based console to design, manage and monitor ESB flows. The web console is a key differentiator for ALSB (now Oracle Service Bus) and will therefore remain a primary design
    environment moving forward.
    The web-based console was complemented in the 3.0 release with full IDE support in Eclipse. The Eclipse capabilities will be ported to Oracle JDeveloper to provide a
    one-stop IDE for all SOA design needs. Until that port is complete, customers will still be able to use the Eclipse environment as IDE (in addition to the web-based
    console).
    cheers
    James

  • Oracle Service Bus and Financila Message Designer

    Hi,
    I am new to OSB and FMD so want some good working examples/samples which can explain how to call the FMD cartridge from OSB.

    Oracle Service Bus 10gR3 contains the JCA framework which will eventually allow us to exploit the whole set of JCA adapters currently in use in BPEL Process Manager. Over the next few months several JCA adapters will be certified to be used with Oracle Service Bus - the Database adapter is one of the first of these.
    As for SOA Suite and WebLogic bundling, let me explain. SOA Suite contains the following products:
    BPEL Process Manager
    Business Activity Monitoring
    Business Rules
    Web Services Manager
    Complex Event Processing
    B2B
    ESB (the old Oracle ESB product)
    Service Bus (formerly AquaLogic Service Bus from BEA)
    This does not come with an application server as the suite is hot-pluggable (i.e. can be used with a number of application servers). However, the preferred (and cheaper) approach is to purchase SOA Suite and WebLogic Suite (which contains iAS, WebLogic Enterprise Edition, Coherence, JRockit with 100ms deterministic garbage collection and WebLogic Operations Control). This is because some of the elements of the SOA Suite only currently run on iAS (B2B) and some only run on WebLogic Server (Oracle Service Bus) although in the future these will also become hot pluggable.
    To find out more, check out the SOA Suite and WebLogic Suite pages below:
    [SOA Suite|http://www.oracle.com/technologies/soa/soa-suite.html]
    [WebLogic Suite|http://www.oracle.com/appserver/weblogic/weblogic-suite.html]
    You will find the DataSheets are particularly useful for giving you an overview of the suite.
    Hope that helps.
    Chris

  • Oracle service bus and database connectivity

    Since currently OSB does not support Adapter Framework, what are currently options for using DB Adapter type functionality in Oracle Service Bus (ALSB).
    It seems JMS and other transports are very well supported, but how do we use DB Services?
    Please if someone can provide some insight into this.
    thanks

    Oracle Service Bus 10gR3 contains the JCA framework which will eventually allow us to exploit the whole set of JCA adapters currently in use in BPEL Process Manager. Over the next few months several JCA adapters will be certified to be used with Oracle Service Bus - the Database adapter is one of the first of these.
    As for SOA Suite and WebLogic bundling, let me explain. SOA Suite contains the following products:
    BPEL Process Manager
    Business Activity Monitoring
    Business Rules
    Web Services Manager
    Complex Event Processing
    B2B
    ESB (the old Oracle ESB product)
    Service Bus (formerly AquaLogic Service Bus from BEA)
    This does not come with an application server as the suite is hot-pluggable (i.e. can be used with a number of application servers). However, the preferred (and cheaper) approach is to purchase SOA Suite and WebLogic Suite (which contains iAS, WebLogic Enterprise Edition, Coherence, JRockit with 100ms deterministic garbage collection and WebLogic Operations Control). This is because some of the elements of the SOA Suite only currently run on iAS (B2B) and some only run on WebLogic Server (Oracle Service Bus) although in the future these will also become hot pluggable.
    To find out more, check out the SOA Suite and WebLogic Suite pages below:
    [SOA Suite|http://www.oracle.com/technologies/soa/soa-suite.html]
    [WebLogic Suite|http://www.oracle.com/appserver/weblogic/weblogic-suite.html]
    You will find the DataSheets are particularly useful for giving you an overview of the suite.
    Hope that helps.
    Chris

  • [OSB] Oracle Service Bus: select database DBadapter runtime

    Suppose you have 2 databases DB1 and DB2 and both have the SCOTT scheme with the EMP table. The default way to gain access to the databases in the Oracle Service Bus (OSB) is by defining 2 database adapters and defining a business service on each adapter:
    - BS1 DBadapter1 DB1.SCOTT.EMP
    - BS2 DBadapter2 DB2.SCOTT.EMP
    With this setup you can define a proxy service and let the message flow decide which adapter to call.
    Now change this configuration a little and suppose you have 25 databases, you can define 25 database adapters and 25 business services, but that involves a lot of repeating work of defining adapters and business services. A more elegant configuration is one business service with one database adapter, and the database connection is set runtime in stead of design time.
    PS BS DBadapter DB1.SCOTT.EMP ... DB25.SCOTT.EMP
    The challenge is: how do you configure the database adapter runtime (called by an OSB business service).
    With kind regards,
    Jornica

    Oracle Service Bus 10gR3 contains the JCA framework which will eventually allow us to exploit the whole set of JCA adapters currently in use in BPEL Process Manager. Over the next few months several JCA adapters will be certified to be used with Oracle Service Bus - the Database adapter is one of the first of these.
    As for SOA Suite and WebLogic bundling, let me explain. SOA Suite contains the following products:
    BPEL Process Manager
    Business Activity Monitoring
    Business Rules
    Web Services Manager
    Complex Event Processing
    B2B
    ESB (the old Oracle ESB product)
    Service Bus (formerly AquaLogic Service Bus from BEA)
    This does not come with an application server as the suite is hot-pluggable (i.e. can be used with a number of application servers). However, the preferred (and cheaper) approach is to purchase SOA Suite and WebLogic Suite (which contains iAS, WebLogic Enterprise Edition, Coherence, JRockit with 100ms deterministic garbage collection and WebLogic Operations Control). This is because some of the elements of the SOA Suite only currently run on iAS (B2B) and some only run on WebLogic Server (Oracle Service Bus) although in the future these will also become hot pluggable.
    To find out more, check out the SOA Suite and WebLogic Suite pages below:
    [SOA Suite|http://www.oracle.com/technologies/soa/soa-suite.html]
    [WebLogic Suite|http://www.oracle.com/appserver/weblogic/weblogic-suite.html]
    You will find the DataSheets are particularly useful for giving you an overview of the suite.
    Hope that helps.
    Chris

  • What is SAP ESB (Enterprise Service Bus)?

    Hi fellow sdners gurus…  I have been reading threads about SAP SOA and ESB. 
    I do not want to start a debate on wether XI is an ESB, but more of a statement to what is SAP ESB (if XI it is, then be it).
    1) What is SAP ESB (Enterprise Service Bus) today (I could not find a clear answer to is)? 
    2) Who uses this SAP ESB in production currently and what kind of environment (i.e. strictly SAP backend systems, or combination of various vendors’ backend systems)?
    Can someone share some light on this topic?
    As a reminder, an ESB is expected to exhibit the following characteristics (source Wikipedia):
    •     It is usually operating-system and programming-language agnostic; for example, it should enable interoperability between Java and .NET applications.
    •     It uses XML (eXtensible Markup Language) as the standard communication language.
    •     It supports web-services standards.
    •     It supports various MEPs (Message Exchange Patterns) (e.g., synchronous request/response, asynchronous request/response, send-and-forget, publish/subscribe).
    •     It includes adapters for supporting integration with legacy systems, possibly based on standards such as JCA
    •     It includes a standardized security model to authorize, authenticate and audit use of the ESB.
    •     To facilitate the transformation of data formats and values, it includes transformation services (often via XSLT or XQuery) between the format of the sending application and the receiving application.
    •     It includes validation against schemas for sending and receiving messages.
    •     It can uniformly apply business rules, enriching messages from other sources, the splitting and combining of multiple messages and the handling of exceptions.
    •     It can provide a unified abstraction across multiple layers
    •     It can route or transform messages conditionally, based on a non-centralized policy (i.e. no central rules-engine needs to be present).
    •     It is monitored for various SLA (Service Level Agreement) threshold message latencies and other SLA characteristics.
    •     It (often) facilitates "service classes," responding appropriately to higher and lower priority users.
    •     It supports queuing, holding messages if applications are temporarily unavailable.
    Your help is greatly appreciated.
    Kind Regards,
    Jean-Michel

    PI or XI is the ESB from SAP side. PI is not a full pledged ESB on a reference model of ESB idea but it is the the framework SAP provide as a ESB product.
    A Standard Based ESB Reference Model should fullfil the following features in a framework.
    ESB Features    Service Enablement Phase (1, 2, 3)
    1)     Message brokering between heterogeneous environments                     
    2)     Supports asynchronous, synchronous, publish and subscribe messaging                    
    3)     Supports synchronous and asynchronous bridging                    
    4)     Supports message formats of SOAP                    
    5)     Support for message format of SOAP with attachments                    
    6)     Support for xml message                     
    7)     Support for structured non-XML data                    
    8)     Support for raw data message                    
    9)     Support for text data message                    
    10)     Sport for e-mail with attachment message                    
    11)     Heterogeneous transports between service end points                    
    12)     Supports for FILE protocols                    
    13)     Supports for FTP protocols                     
    14)     Supports for HTTP protocols                    
    15)     Supports for HTTPS protocols                    
    16)     Supports for Multiple JMS providers                    
    17)     Supports for RMI protocols                    
    18)     Supports for web service protocols                    
    19)     Supports for CORBA protocols                    
    20)     Supports for DCOM protocols                    
    21)     Supports for E-mail (POP, SMTP, IMAP) protocols                    
    22)     Support for advanced transformation engine                    
    23)     Support for configuration-driven routing                    
    24)     Message routing based policies                    
    25)     Support for call-outs to external services to support complex routing                    
    26)     Support for point-to-point routing                    
    27)     Support for one-to-many routing scenarios                     
    28)     Support for request response model                    
    29)     Support for publish-subscribe models                    
    30)     Service monitoring                    
    31)     Service logging                    
    32)     Service auditing with search capabilities.                    
    33)     Support for capture of key statistics for message and transport attributes including message invocations, errors, and performance, volume, and SLA violations.                     
    34)     Supports clusters and gathers statistics across the cluster to review SLA violations                    
    35)     Support for service provisioning                     
    36)     Support deployment of new versions of services dynamically through configuration                    
    37)     Migrates configured services and resources between design, staging and production                    
    38)     Supports multiple versions of message resources that are incrementally deployed with selective service access through flexible routing                    
    39)     Configurable policy-driven security                    
    40)     Supports the latest security standards for authentication, encryption-decryption, and digital signatures                    
    41)     Supports SSL for HTTP and JMS transports                    
    42)     Supports multiple authentication models                    
    43)     Policy-driven SLA enforcement                    
    44)     Establishes SLAs on a variety of attributes including                     
    a.     Throughput times                    
    b.     Processing volumes                    
    c.     Success/failure ratios of message processes                    
    d.     Number of errors                    
    e.     Security violations                    
    f.     Schema validation issues                     
    45)     Initiates automated alerts or enables operator-initiated responses to rule violations using flexible mechanisms including                     
    a.     E-mail notifications                    
    b.     Triggered JMS messages                    
    c.     Triggered integration processes with a JMS message                    
    d.     Web services invocations with a JMS message                    
    e.     Administration console alerts.                     
    46)     Support for having multiple LOBs manage their own service bus based on their policies, and a service bus at an enterprise level that could act as a broker for sharing services across the various business units.                    
    47)     Support for agent plug-in to support following features                    
    48)     External provider’s service access for security                    
    49)     External provider’s service management                     
    50)     External provider’s transaction container                    
    a.     External provider’s business orchestration (BPEL Engine) and business work flow service container                    
    51)     Transaction support on message level                    
    52)     IDE Integration                    
    53)     Open standards

  • Where download Oracle Service Bus 10gR3?

    could someone tell me please where I can download Oracle Service Bus 10gR3? the file name should be osb103_wls103_win32.exe
    I just installed:
    SOA Suite 10.1.3.1
    SOA Suite Patch to take SOA Suite to 10.1.3.5 revision level
    Business Activity Monitoring 10.1.3.3
    SOA Suite Patch to take BAM to 10.1.3.5 revision level
    Oracle JDeveloper 10.1.3.4
    missing only Oracle Service Bus 10gR3 for complete my environment
    Thanks

    the file name should be osb103_wls103_win32.exeWhy do you want to use older version of OSB in 10g series (latest version in 10g series is 10.3.1)? Any special requirement?
    You may get the installer of older versions from oracle support (http://metalink.oracle.com/) or from http://edelivery.oracle.com/
    Regards,
    Anuj

  • Capturing service bus traffic with fiddler

    Hi,
    I'm using Node js to connect to Service Bus Topics and I'm having problems to get the Topic information programmatically. I'm trying to use fiddler to debug the problem. In order to see the node js traffic I'm setting the proxies in the command line shell
    to : https_proxy=http://127.0.0.1:8888
    http_proxy=http://127.0.0.1:8888
    NODE_TLS_REJECT_UNAUTHORIZED=0
    but in fiddler I can only see the tunneling to https.
    My question is how do I change the traffic to the Service Bus to HTTP so I can monitor it with fiddler.
    Also, if you think about other ways i can debug calls to Service Bus it will be helpful.
    Thanks.

    Hi,
    Thank you for reaching out to us. I am currently researching to gather more information with regards to your request. I shall revert back to you with an update at the earliest. Sincerely appreciate
    your patience.
    Regards,
    Azam khan

  • Issue in deploying Service Bus projects using maven

    Hi,
    I am following the following documentation for deploying service bus projects to my OSB server.
    http://docs.oracle.com/middleware/1213/core/MAVEN/osb_maven_project.htm#MAVEN8973
    I was able to issue mvn package as described in documentation and also able to see sbar files in .data/Maven directory of each project.
    But i am seeing following error when i issue mvn pre-integration-test. Am i missing any steps.
    [INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (default-deploy) @ System ---
    [INFO] Service Bus Archive deployed using session Service_Bus_Maven-System-1424718369010.
    java.io.IOException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'w
    eblogic.management.mbeanservers'
            at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.ja
    va:237)
            at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.j
    ava:120)
            at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:369)
            at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
            at oracle.sb.maven.plugin.deploy.MBeanHelper$MBeanInvocationHandler.getJMXConnector(MBeanHel
    per.java:228)
            at oracle.sb.maven.plugin.deploy.MBeanHelper$MBeanInvocationHandler.invoke(MBeanHelper.java:
    131)
            at com.sun.proxy.$Proxy16.createSession(Unknown Source)
            at oracle.sb.maven.plugin.DeployMojo.createSession(DeployMojo.java:141)
            at oracle.sb.maven.plugin.DeployMojo.execute(DeployMojo.java:89)
            at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.j
    ava:101)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
    ilder.java:84)
            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
    ilder.java:59)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter
    .java:183)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
            at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
            at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
            at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:606)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
            at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.d
    omainruntime'. Resolved 'weblogic.management.mbeanservers' [Root exception is javax.naming.NameNotFo
    undException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic
    .management.mbeanservers']; remaining name 'domainruntime'
            at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1180
            at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:270)
            at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:187)
            at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:210)
            at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
            at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
            at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
            at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:701)
            at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:231)
            at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:527)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:523)

    Hi Siva,
    I am facing same issue I am bale to create package but while deployment goal I am facing problem.I am following same document as you do.
    I can see my mvn-pre-integration ..show me sucees in result
    [DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:3.0.3
    [DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:package from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracl
    -servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
    [DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:package' with basic configurator -->
    [DEBUG]   (f) oracleHome = C:\Oracle\Middleware\Oracle_Home
    [DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
    [DEBUG]   (f) system = false
    [DEBUG] -- end configuration --
    [INFO]
    [INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (default-deploy) @ TestOSBLinux ---
    [DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracle
    servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
    [DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy' with basic configurator -->
    [DEBUG]   (f) oraclePassword = Oracle123
    [DEBUG]   (f) oracleServerUrl = http://192.168.137.150:7001
    [DEBUG]   (f) oracleUsername = weblogic
    [DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
    [DEBUG] -- end configuration --
    [INFO] Service Bus Archive deployed using session Service_Bus_Maven-TestOSBLinux-1429888616161.
    [INFO]
    [INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (deploy) @ TestOSBLinux ---
    [DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracle
    servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
    [DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy' with basic configurator -->
    [DEBUG]   (f) oraclePassword = Oracle123
    [DEBUG]   (f) oracleServerUrl = http://192.168.137.150:7001
    [DEBUG]   (f) oracleUsername = weblogic
    [DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
    [DEBUG] -- end configuration --
    [INFO] Service Bus Archive deployed using session Service_Bus_Maven-TestOSBLinux-1429888623126.
    [INFO]
    [INFO] ------------------------------------------------------------------------
    [INFO] Building LinuxMachine 1.0-SNAPSHOT
    [INFO] ------------------------------------------------------------------------
    [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-so
    rces, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, i
    tegration-test, post-integration-test, verify, install, deploy]
    [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
    [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
    [DEBUG] === PROJECT BUILD PLAN ================================================
    [DEBUG] Project:       LinuxMachine:LinuxMachine:1.0-SNAPSHOT
    [DEBUG] Dependencies (collect): []
    [DEBUG] Dependencies (resolve): []
    [DEBUG] Repositories (dependencies): [central (https://repo.maven.apache.org/maven2, default, releases)]
    [DEBUG] Repositories (plugins)     : [central (https://repo.maven.apache.org/maven2, default, releases)]
    [DEBUG] =======================================================================
    [INFO] ------------------------------------------------------------------------
    [INFO] Reactor Summary:
    [INFO]
    [INFO] TestOSBLinux ....................................... SUCCESS [ 20.752 s]
    [INFO] LinuxMachine ....................................... SUCCESS [  0.009 s]
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESS
    [INFO] ------------------------------------------------------------------------
    But not get deployed .....
    When i  run mvn com.oracle.servicebus.plugin:oracle-servicebus-plugin:deploy**  to invoke deployment goal it fails which below logs
    org.apache.maven.plugin.MojoNotFoundException: Could not find goal 'deploy*.*' in plugin com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0 amon
    goals deploy, package
            at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:275)
            at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:239)
            at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:233)
            at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:103)
            at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:83)
            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:85)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
            at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
            at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
            at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:606)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
            at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
            at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
    [ERROR]
    [ERROR]
    Thanks&Regards
    Prabhat

  • How to log the exception using Log action in Oracle Service Bus

    Hi,
    Whenever an exception is raised how to log the exception using Log action in oracle service bus.After logging where I have to find the logged message.

    It would be in the log file for the managed server which ran the request. If you are logging the message at a lower level than your app server, however, you won't see it. You should be logging the exception at Error level.

  • Oracle OSB 11G. Unable to find Oracle Service Bus Configuration Page.

    Hi All,
    Sorry for the apparent silly question but I am studying and learning the product.
    I have the OSB 11G installed and running with a proxy service working and routing requests. The Oracle ESB documentation http://download.oracle.com/docs/cd/E21764_01/doc.1111/e15866/ui_ref.htm#i1327746 at chapter 4.4.2 New Oracle Service Bus Configuration Project Wizard
    Use this wizard to create an Oracle Service Bus configuration project. For configuration options, see Section 4.4.3, "Oracle Service Bus Configuration Page."
    4.4.3 Oracle Service Bus Configuration Page.
    I don't see the configuration page in anywhere in the left pane of the console. Am I missing something? The project creation works fine but I just don't see the configuration Wizard.
    Thanks.
    Regards
    Salvatore Ilardo

    The link which you are referring is for user interface objects in the Oracle Service Bus plug-ins and OSB plug-ins are used with OEPE (Oracle Enterprise Pack for Ecplise) for OSB development. OEPE is the only supported IDE for OSB development as of now.
    Remember, at a time, one and only one Oracle Service Bus Configuration project can be deployed in a OSB domain which may contain desired number of Oracle Service Bus Projects and that's why there is no provision of creating Oracle Service Bus Configuration Project in sbconsole GUI. In IDE, you may create many Oracle Service Bus Configuration Project and that's why it has a Oracle Service Bus Configuration Project Wizard.
    Regards,
    Anuj

Maybe you are looking for