Bam server and metadata Language

Hi,
I installed Livecycle 8.2 with Bam server.
I configure process management with Bam.
When I log on dashboard or workbench, the language is in French, what I want.
But for example the events in workbench or dimensions in dashboard are display in English.
How can I have all the display in French ?
I suppose it depends on the database.
Thanks

Hi "Help Please" (funny name),
I think you relate to the Oracle ESB (in 11g mediator)? In that case the metadata server relates to the repository definitions and the Run-time server does what its name suggests. In a single node setup these can run in the same container. But in a HighAvailability setup there can only run one Metadataserver in a cluster at the same time. The Runtime server can have multiple instances. So these can run in a active-active configuration. The metadata server then should be in a seperate container that is configured active-passive. So that if the active one goes down opmn can bringup the passive one.
Regards,
Martien

Similar Messages

  • BAM HA and Data Consistency

    Hi,
    I need to preserve consistency of data in BAM, meaning BAM itself does not require HA, but I need to guaranty there is no loss of data (even if BAM server is down). I have a single BAM server and a cluster of WLS where the JMS queues/topics are located (data is read from JMS queues/topics using EMS).
    Using any kind of topic means loss of data once BAM server is down.
    BAM does not reconnect after migration so using a queue on a migrate-able JMS server also does not seem to work.
    Using a distributed queue requires a queue for each EMS instead of using a single queue with Message Selector. And anyways there is no reconnection in this case as well.
    What would be the preferred approach than?
    Any suggestions are highly appreciated.
    Regards.

    Hi
    There are a couple of performance related measures that you can take :
    - Creating aggregates on 3-4 objects which are very popular in terms of reporting. Make sure that you don' t go overboard with this as maintaining  too many aggregates could create a memory issue.
    - If you are using BI 7.0 , then go for 'Repartitioning'.  Would help you in loading data as well as during reporting.
    - Compressing / Indexing are always available and good options.
    - I don't compressing could create an issue even if your Info cube gets populated thru multiple data sources.
    Cheers
    Umesh

  • BAM Server Connection FAILED

    I'm working with BAM 10.1.2 and BPEL 10.1.2.0.2. Well, I'm trying connect to the BAM server and I can't do it!!!
    Maybe I need something..... but i dont know what?
    I red that is posible fix this issue installing the BPEL PM 10.1.3 but I dont to find that download!
    help me!

    Hello - typo from my previous response - pl read last word as "access". Contact Oracle rep for quick BAM 10.1.3 access. (if this is possible for you).
    http://www.oracle.com/technology/tech/java/oc4j/10131/index.html
    http://www.oracle.com/technology/software/products/ias/soapreview.html
    BPEL 10.1.2 has BAM -sensor- connection as [preview] mode.
    Alternates - in BPEL_BAM server dialog box
    (a) donot use localhost, (b) provide domain name in CAPS (donot leave empty). (c) Provide server name in CAPS.

  • Disconnect WSUS server and Process of Approving Updates via Metadata.

    Hi Folks:
    I have recently setup 2 WSUS servers.   The first one has connectivity to the Internet and of course has access to Microsoft updates.   The second WSUS server is part of a disconnected network.   Both WSUS servers are supporting client workstations
    of various operating system versions.   The connected WSUS server is fairly easy, from a management viewpoint.   I simply check to see what updates are "Needed" and I approve them for download.   However, the disconnected WSUS server
    is the one that I need some advice on.   I want to have a fairly simply procedure for the disconnected WSUS server, but here is the procedure that I think would work:
    Transfer metadata and updates via disc from the connected WSUS server to the disconnected WSUS server (using documented export/import procedure).
    Check to see what is "Needed" updates on the disconnected WSUS server, once the WSUS server has had a chance to absorb all the imported metadata and updates.   This means that the disconnected WSUS server has determined from it's supported
    client workstations, what updates are required.
    Generate a list of those "Needed" updates in some form, so that I can now approve those updates on the CONNECTED WSUS server for download.  
    Once those updates have been downloaded to the connected WSUS server, transfer the updates and metadata again to the disconnected WSUS server.   Approve those updates, so that they can now be sent out to the client workstations on the disconnected
    network.
    If that is my procedure (can someone like Lawrence Garvin), please let me know, if that sounds correct.   I'm concerned about the double export/import of the metadata and updates.
    Also, I'm wondering if it would be better to have separate connected WSUS server for supporting the disconnected WSUS to keep things straight.
    For example:
    One connected WSUS servers supporting the set of client workstations, that are on the connect WSUS server's network.
    One disconnected WSUS server supporting the set of client workstations that are on the disconnected WSUS server's network.
    One more connected WSUS server, that would be used to download and transfer metadata and updates to the disconnect WSUS server.   The advantage in keeping this separate, is that you would never confuse approved updates between the connected network
    client workstations and the disconnected network client workstations.  Especially, if they have different versions of software, that require updating.  
    Any input would be appreciated.

    You will likely also want to configure your WSUS server to "Download express installation files." under the "Update Files and Languages," setting on your options.
    I will unequivocally disagree with this statement, for several reasons:
    First, there's nothing that needs to be deployed that would use Express Installation Files anyway. Express Installation Files were designed to facilitate the deployment of Very Large Updates (read: SERVICE PACKS) across slow-speed links by significantly
    reducing the size of the binary that must be downloaded by the CLIENT. There are NO service packs in the catalog that won't already be installed on any client system.
    Second, in exchange for that ability of clients to download less, it significantly increased the size of the binary that must be downloaded by the SERVER from Microsoft. Express Installation Files will cause hundreds of gigabytes of extra binaries to be
    downloaded, which will need to be transferred to the disconnected server. None of which will actually ever be used.
    Third, most disconnected networks do not include WAN links, so the primary purpose of Express Installation File is contra-indicated by the very scenario being discussed.
    Otherwise by default you might get just an installer downloaded onto the WSUS server and clients might still need internet access to download the actual package contents.
    It would seem that you do not correctly understand Express Installation Files.
    There is an in-depth explanation of Express Installation Files in the WSUS Deployment Guide. For additional information see
    https://technet.microsoft.com/en-us/library/dd939908(v=ws.10).aspx#express
    I also would not recommend a internet facing WSUS server just to provide updates to the disconnected WSUS server as that will also need to download a full copy of the content to that server when it is likely already downloaded onto your internet
    / production WSUS server anyway.
    Seemingly you are also not actually familiar with the documented guidance for how to manage disconnected networks. An Internet-facing (connected) WSUS server is *exactly* how this is done.
    You may also find this part of the Deployment Guide to be useful reading:
    Configure a Disconnected Network to Receive Updates
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Opening BAM Server Port and Integrating BPEL Server over Internet

    Hi Friends,
    I have a BPEL Process which has Sensor Actions to insert data to a BAM Data Object. BPEL & BAM Servers are on different boxes and have to be accessed over the internet. I want to know whether anyone can give me any pointers to manually open BAM Server's Port from a Windows XP machine to be accessed by a BPEL Server Process over Internet. Pl. provide detailed steps in case possible.
    Appreciate your help in advance.
    Thanks
    Ram

    When you create the BPEL process (or after you deploy it) you can modify the bam server settings. In your case, I think all you need to do is supply the correct port -- 445 instead of 80
    If you are doing this post-deployment you can go to the BPEL console, select the BPEL service and modify the connection settings by modifying the process' descriptor. You should modify the bamserver.port property. If you are not using 10.1.3.3, then there is a bug with the descriptor page that requires that you make sure you re-type in the bamserver.password field PRIOR to clicking update desciptor.
    If you are doing it pre-deployment, you can modify the bpel.xml file in JDeveloper of your BPEL process. You will see the bamserver.port property defined in that file.

  • BAM Connection in 12C -  Failed to establish a connection to localhost at port 7004.Please verify the Bam server host and JNDI port.

    Hi,
    BAM server is running on 7004 in our local system.
    We need o connect to BAM server from OSB service.
    We tried to use the BAM adapter in the pipeline in 12c, We received Failed to establish a connection to localhost at port 7004.Please verify the Bam server host and JNDI port.
    Please let us know the resolution to this issue.
    Also please provide some links/steps to connect from OSB service to BAM server in 12c.
    Thanks,

    In BAM 12c, you can send data via JMS by configuring an EMS in BAM using the "self-described" payload. Make sure the date formats match correctly. You can configure an error queue which will show you any data parsing problems.
    For example,
    <msgRoot dataObjectName="Student" operationType="insert" keys="RequestId">
       <RequestId>R1000</RequestId>
       <StudentId>S12345</StudentId>
       <RequestType>Admission</RequestType>
       <RequestStatus>Open</RequestStatus>
       <RequestMessage>Please Admin</RequestMessage>
       <RequestCode>3</RequestCode>
       <SubmitTime>2015-03-17 18:23:07</SubmitTime>
       <ApprovalTime>2015-02-18 18:23:07</ApprovalTime>
    </msgRoot>

  • Oracle BPEL Process Manager 10.1.3.x sensors and Oracle BAM Server 11g TP4

    In Oracle Fusion Middleware Developers Guide for Oracle SOA Suite in section 42.5 there is the next:
    "You can also use Oracle BPEL Process Manager 10.1.3.1 sensor actions to publish sensor data as data objects on Oracle BAM Server 11g"
    Is it really possible?

    Hi, Please post this in BPEL forum, not here.
    Regards,
    Priyanka GES

  • Hardcoded BAM server parameters when using BAM sensors

    The problem we're having is that when a BPEL process has BAM sensors, the BAM server configuration parameters are hardcoded in bpel.xml and sensorAction.xml.
    This causes problems when the process is being deployed to a different instance than the development instance.
    I solved the problem for the bpel.xml file with the <customize> ant task, but haven't found a solution yet for sensorAction.xml.
    Any suggestions?
    Thanks,
    Arnold van Koppen

    See..when the BAM Server is down the corresponding data objects wont be available to you..During the design time wat u do is create a variable which contains the elements dat u wanna monitor in the BAM...IN BAM u create data objects ..then u map the schema from the BPEL to the BAM Data Objects ...U need a BAM Server connection which pulls up the metadata from the server ..If the BAM Server is down u wont get the BAM DOs...to keep a back up u can use DB as the sensor action so that the data from the sensor action is written to the DB..Using a DB Adapter i think the data from the Reports schema can be written to the OracleBAM schema ...so that even if the BAM Server is down the data is written to the OracleBAM schema

  • Sharepoint 2013: Problem / Error when creating Variation Hierarchy for French and German Languages from Variation root EN

    Hi,
    I have a website with English and Arabic Language Packs installed. I have the corresponding Variation heirachies created and the whole site collection is published.
    Recently the client asked for french and german languages to be accomodated as well. So I followed the same approach I did for English and arabic (installed the language packs) for foundation, ran ocnfiguration wizard, installed server language pack &
    ran configuration wizard.
    But after creating the variation label, when i try to create the variation heirarchy, I am getting the following error.
    "Unknown failure when creating a variation of page http://server:port/en/pages/default.aspx in label /fr/Pages/default.aspx.
    The Variations Create Hierarchies job failed with the following error message&  Unknown failure when creating a variation of site
    http://server:port/en in label fr."
    Am not sure what is going wrong. Appreciate a feedback.
    Thanks,
    SSP
    SSP

    Hi,
    According to your description, my understanding is that the error occurred when you created the Variation Hierarchy for French and German Languages from Variation root EN.
    I recommend to check the Resources folder located at C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15 to see if the file core.fr-FR.resx exists in the folder.
    Here is a similar thread for you to take a look:
    http://social.msdn.microsoft.com/Forums/sharepoint/en-US/611575b2-d129-44c6-814b-2e5782178850/unknow-failure-when-creating-variations-in-sharepoint-2013-is-this-a-bug-in-sharepoint-2013-rtm?forum=sharepointadmin
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • ORACLE SERVER AND UNIX TP MONITOR-1

    제품 : ORACLE SERVER
    작성날짜 : 2002-05-17
    ====================================================================
    Subject: Oracle Server and UNIX Transaction Processing Monitors - 1
    =====================================================================
    PURPOSE
    This file contains commonly asked questions about Oracle Server and UNIX
    Transaction Processing Monitors (TPMs). The topics covered in this article are
         o What is a Transaction Processing Monitor (TPM)?
         o What is the X/Open Distributed Transaction Processing Model?
         o How does the Oracle Server works with TPMs?
         o How should I position TPMs with my customer?
         o What Oracle products must a customer purchase?
         o Where can my customer purchase a TPM?
         o Availability and packaging
    Explanation & Example
    What is a Transaction Processing Monitor?
    =========================================
    Under UNIX, a Transaction Processing Monitor (TPM) is a tool that coordinates
    the flow of transaction requests between front-end client processes that issue
    requests and back-end servers that process them. A TPM is used as
    the "glue" to coordinate transactions that require the services of several
    different types of back-end processes, such as application servers and
    resource managers, possibly distributed over a network.
    In a typical TPM environment, front-end client processes perform screen
    handling and ask for services from back-end server processes via calls to the
    TPM. The TPM then routes the requests to the appropriate back-end server
    process or server processes, wherever they are located on the network. Through
    configuration information, the TPM knows what services are available and where
    they are located. Generally, the back-end server processes are specialized so
    that each one handles one type of requested service. The TPM provides
    location transparency as well and can send messages through the network
    utilizing lower-level transport services such as TCP/IP or OSF DCE.
    The back-end servers process the requests as necessary and
    return the results back to the TP monitor. The TP monitor then routes
    these results back to the original front-end client process.
    A TPM is instrumental in the implementation of truly distributed processing.
    Front-end clients and back-end processes have no knowledge of each
    other. They operate as separate entities, and it is this concept that provides
    flexibility in application development. Front-end and back-end processes are
    developed in the UNIX client-server style, with each side optimized for its
    particular task. Server functionality can be deployed in stages, which makes
    it easy to add functionality as needed later in the product cycle. It also
    makes it easy to distribute both the front-end and back-end processes
    throughout the network on the most appropriate hardware for the job. In
    addition, multiple back-end server processes of the same type might be
    activated to handle increasing numbers of users.
    What is the X/Open Distributed Transaction Processing Model?
    ============================================================
    The X/Open Transaction Processing working group has been working
    for several years to establish a standard architecture to implement
    distributed transaction processing on open systems. In late 1991,
    X/Open published the initial Distributed Transaction Processing (DTP)
    model specification and defined the first of several interfaces that
    exist between the components of the model. Subsequently, other publications
    and a revised model specification have been published.
    An important function of the TPM in the X/Open DTP model is the
    synchronization of any commits and rollbacks that are required to complete
    a distributed transaction request. The Transaction Manager (TM) portion
    of the TPM is the entity responsible for ordering when distributed commits
    and rollbacks will take place. Thus, if a distributed application program
    is written to take advantage of the TM portion of the TPM, then it,
    and not the DBMS, becomes responsible for enabling the two-phase commit
    process. Article 2 has more detail on this model.
    How does the Oracle Server work with TPMs?
    ==========================================
    When a TPM is used without invoking an X/Open TM component to manage the
    transactions, Oracle Server needs no special functionality. The transaction
    will be managed by Oracle itself. However, when the TPM X/Open TM component
    is used to manage the transaction, the Oracle Server, that is the Oracle DBMS,
    acts as a Resource Manager--a type of back-end process. In the case of
    TPM-managed transactions, the TM needs a way to tell the RMs about the stages
    of the transaction. This is done by a standard, X/Open defined interface
    called XA. Article 2 of of this document gives more information about both
    the X/Open model and Oracle7's use of XA.
    Because the XA interface provides a standard interface between the TM and the
    resource manager, it follows that the TM can communicate with any XA-compliant
    resource manager (e.g., RDBMS), and, conversely, that a resource manager can
    communicate with any XA-compliant TM. Thus, the Oracle Server, beginning with
    Oracle7, works with any XA-compliant TM.
    How should I position TPMs with my customer?
    ============================================
    There's been a great deal of confusion about the need for TPM technology. Some
    software suppliers, most notably IBM, will assert that a TPM like CICS is a
    necessary requirement for high volume OLTP. Other vendors will assert that
    there is seldom a need for such technology. And yet others promote TPMs as
    providers of higher transaction throughput.
    From Oracle's standpoint, customers might choose TPM technology under any of
    the following conditions:
    1. For heterogeneous database access, especially for 2PC capability
         This means that a TPM can be used to coordinate 2PC between Oracle
         DBMS and any other XA-compliant database, such as Informix. This
         does NOT provide SQL heterogeneity - SQL calls to Oracle DBMS may be
         different than SQL calls to Informix. The TPM handles the routing,
         communication, and two-phase commit portion of the transaction, but
         does not translate one type of SQL call into another.
    2. For transaction monitoring and workload control
         The leading TPMs supply tools to actively manage the flow of
         transactions between clients and servers and to load balance the work
         load across all available processors on a network, not just on a
         single multi-processor system. Some TPMs also have the ability to
         dynamically bring up additional back-end services during peak work
         hours.
    3. For more flexible application development and installation
         One of the key features of the DTP model is application modularity.
         Modularity, that is, the decomposition of a large program into small,
         easily defined, coded and maintained "mini-programs" makes it easy to
         add new functionality as needed. Modularity also makes it much easier
         to distribute the front-end and back-end processes and the resource
         managers across hardware throughout a network.
    4. For isolating the client from details of the data model
    By using the service oriented programming model, the client program
         is unaware of the data model. The service can be recoded to use a
         different one with no change to the client. To get this advantage,
         the application developer must explicitly code the server and client
         to fit the service model.
    5. For connection of thousands of users
         TP Monitors, because of their three-tier architecture, can be used
         to connect users to an intermediate machine or machines, removing
         the overhead of handling terminal connections from the machine
         actually running the database. See Article 4 for more information.
    There are also several cases where TPM technology is not the right answer.
    These include:
    1. If the customer is simply looking for a performance improvement
         The customer may have heard a theory that "higher performance
         is possible for large scale applications only if they use a
         TP monitor". First, no performance gain can be achieved for
         existing applications; in fact, they won't even run under a TP
         Monitor without recoding. Second, performance improvements have
         only been documented for large numbers of users, and "large"
         means many hundreds or thousands. Without a TP Monitor,
         Oracle Server can handle several hundred users with its normal
         two-task architecture and several times that using the Multi
         Threaded Server. For more on performance, see Article 4.
    2. If the customer has made large investment in his existing Oracle
    applications
         TP monitor applications must be designed from the ground up to take
         advantage of TP monitor technology. Current Oracle customers will find
         it difficult to "retrofit" a TP monitor to their existing applications.
         The Multi Threaded Server, on the other hand, allows the use of
         existing Oracle applications without change.
    3. If the customer is committed to the Oracle tool set
         Currently, none of Oracle's front-end tools (Oracle Forms, etc.) is
         designed to work with TP monitors. It is possible to invoke a
         TP Monitor by using user exits. However, the fact that the TP
         Monitor model hides the data model from the client means that only
         the screen display parts of Forms can be used, not the automatic
         mapping from screen blocks to tables.
    4. If the customer does not have a staff of experienced software engineers
         This is still very young technology for UNIX. There is not a lot of
    knowledge in the industry on how to build TP monitor applications or
    what techniques are most useful and which are not. Furthermore,
         integrating products from different vendors, even with the support
         of standard interfaces, is more complex than deploying an integrated
         all-Oracle solution. Because TP monitor technology is fairly
         complex, we recommend that you let the TP monitor supplier promote
         the virtues of their technology and differentiate themselves from
         their competitors.
    What Oracle products must a customer purchase?
    ==============================================
    If your customer is only interested in building Oracle-managed TP Monitor
    transactions, the only Oracle products required are the Oracle Server
    and the appropriate Oracle precompiler for whatever language the
    application is being written in--most likely C or Cobol. If TPM-managed
    transactions are required, the Oracle7 Server with the distributed option
    is also required. SQL*Net is optional because the TPM takes care of the
    network services. Article 2 describes when you would choose to have the TP
    Monitor manage the transactions.
    Where can my customer purchase a TPM?
    =====================================
    There are many vendors offering the UNIX TPM products. (Oracle does not
    relicense TPMs.) Information on the most well known products is provided
    below:
    The following support XA:
    Product & Vendor     FCS          Known OS/Platform Ports
    "TUXEDO System/T"     1986          UNIX SVR4 & SVR3: Amdahl, AT&T,
    UNIX System Laboratories          Bull, Compaq, Dell, Fujitsu, ICL,
    190 River Road                    Motorola, Olivetti, Pyramid,Sequent,
    Summit, NJ 07901               Sun, Toshiba, Unisys, NCR, Stratus
                             Other: IBM AIX, HP/UX, DEC Ultrix
    "TOP END"      1992          UNIX SVR4: NCR
    NCR Corporation
    1334 S. Patterson Blvd.
    Dayton, OH 45479
    "ENCINA"          1992          IBM AIX, HP, Sun (SunOS and Solaris)
    Transarc Corporation               Other: OS/2, DOS, HP-UX, STRATUS
    707 Grant Street (Depends on DCE)
    Pittsburgh, PA 15219
    "CICS/6000" 1993          AIX: IBM
    IBM Corporation                    (Depends on DCE)
    "CICS 9000" 1994          HP-UX
    HP
    The following do not currently support XA:
    Product & Vendor     FCS          Known OS/Platform Ports
    "VIS/TP"          unknown          unknown
    VISystems, Inc.
    11910 Greenville Avenue
    Dallas, TX 75243
    "UniKix"          1990          UNIX: ARIX, AT&T, NCR, Pyramid,
    UniKix                     Sequent, Sun, Unisys      
    "MicroFocus           1993          SCO Unix, AIX
    Transaction System"
    Micro Focus
    26 West Street
    Newbury RG13 1JT
    UK
    There are also several third parties who are reselling the products listed
    above.
    In addition, Groupe Bull, Digital, Siemens-Nixdorf, and several other hardware
    vendors are planning to redesign their proprietary TPMs to be XA-compliant and
    suitable for use on UNIX systems.
    Availability and Packaging
    ==========================
    On what platforms is the XA Library available?
    Oracle provides the XA interface with Oracle7 Server on all platforms that
    support an XA-compliant TPM. Support for XA is included as part of the
    Oracle7 Server distributed option and has no extra charge in and of itself.
    Which version of XA does Oracle Server support?
    Oracle7 Server supports the Common Application Environment (CAE) version of
    XA, based on the specification published by X/Open in late 1991. It will
    require that the TM also be at that level. This means Tuxedo /T version 4.2,
    for example.
    Oracle Server supports all required XA functions. There are some optional
    features Oracle Server does not support, such as asynchronous operation.
    None of those options affect application programming.
    Page (2/4)
    This file contains commonly asked questions about Oracle Server and UNIX
    Transaction Processing Monitors (TPMs). The topics covered in this article are
         o Oracle Server Working with UNIX TPMs
         o TPM Application Architecture
    The questions answered in part 2 provide additional detail to the information
    provided in part 1.
    Oracle Server Working with UNIX TP Monitors
    ===========================================
    Do I need XA to use Oracle Server with TPMs? If I don't use it, what are
    the consequences?
    There are a number of real applications running today with Oracle Server and
    TPMs but not using XA. To use a TPM with Oracle without using XA, the user
    would write an "application server" program which could handle one or more
    "services". For example, a server program might handle a service called
    "debit_credit". The key requirement is that the entire transaction,
    including the "commit work", must be executed within a single service. This
    is the restriction which XA will remove, as we'll see later. Each
    server process can serially handle requests on behalf of different clients.
    Because a server process can handle many client processes, this can
    reduce the total number of active processes on the server system,
    thereby reducing resource requirements and possibly increasing overall
    throughput.
    When Oracle is used with a TPM in this mode, we call it an Oracle-managed
    transaction since the transaction commit or rollback is done with a SQL
    statement.
    What is XA? How does XA help Oracle7 work with UNIX TPMs?
    XA is an industry standard interface between a Transaction Manager and a
    Resource Manager. A Resource Manager (RM) is an agent which
    controls a shared, recoverable resource; such a resource can be
    returned to a consistent state after a failure. For example, Oracle7 Server
    is an RM and uses its redo log and undo segments to be able to do this.
    A Transaction Manager (TM) manages a transaction including the
    commitment protocol and, when necessary, the recovery after a failure.
    Normally, Oracle Server acts as its own TM and manages its own commitment
    and recovery. However, using a standards-based TM allows Oracle7 to
    cooperate with other heterogeneous RMs in a single transaction.
    The commonly used TPMs include a TM component for this purpose. In order to
    use the TM capability of the TPM rather than Oracle7's own transaction
    management, the application uses a transaction demarcation API (called TX)
    provided by the TPM rather than the SQL transaction control statements (e.g.
    "commit work"). For each TX call, the TM then instructs all RMs, by the
    appropriate XA commands, to follow the two-phase commit protocol. We
    call this a TPM-managed transaction.
    The following picture shows these interfaces within a monolithic application
    program model. This is the model most commonly described in the
    DTP literature. We'll see later what the picture looks like when we add
    Oracle7 and when we switch to a modularized client-server application
    program model.
              | |
              | |
              | Application Program (AP) |
              | |
              | |
                   | | |                    |
    Resource Manager API | | | |
    (e.g. SQL) -----|--|------------- | TX API
              | | v |          |
              --------|-------------     |          |
              | v | | v
         ---------------------- | | --------------------
         | | | | | |
         | Resource | | |<----->| Transaction |
         | Managers | |--- | Manager |
         | (RMs) | |<-------->| (TM) |
         | |--- | |
         | |<----------->| |
         ---------------------- XA --------------------
                        Interface
    The XA interface is an interface between two system components, not
    an application program interface; the application program does
    not write XA calls nor need to know the details of this interface.
    The TM cannot do transaction coordination without the assistance of
    the RM; the XA interface is used to get that assistance.
    How does the DTP Model support client-server?
    The above picture was actually simplified to make it easier to explain
    the role of XA. In a true distributed transaction architecture, there
    are multiple applications, each with an Application Program, a Resource
    Manager, and a Transaction Manager. The applications communicate by
    using a Communication Resource Manager. The CRM is generally provided
    as a component of the TPM. It includes the transaction information when
    it sends messages between applications, so that both applications can
    act of behalf of the same transaction. The following picture
    illustrates this:
    Client Application
    | AP |
    ||| | |
    SQL ||| | TX | CRM
    ||V V | API
    -||-- ----- |
    | |V | | | V
    --|-- |<---| | -----
    | V || | | | |
    ----- |<----| TM |<-->| CRM |
    | || | |XA+ | |
    | RMs |<-----| | -----
    | | XA | | A
    ----- ----- | Server Application
    | -----------------------------
    | | AP |
    | -----------------------------
    | ||| | |
    | SQL ||| | TX | CRM
    | ||V V | API
    | -||-- ----- |
    | | |V | | | V
    | --|-- |<---| | -----
    | | V || | | | |
    | ----- |<----| TM |<-->| CRM |
    | | || | |XA+ | |
    | | RMs |<-----| | -----
    | | | XA | | A
    | ----- ----- |
    | |
    | |
    -------- |
    / |
    / |
    / |
    Most TP Monitor products include both a TM and a CRM, and also provide
    additional functions such as task scheduling and workload monitoring.
    What is XA+? What does Oracle need to do to comply with it?
    XA+ is an interface that lets the X/Open model actually be distributed
    because it allows a communication resource manager to tell a TM on the
    server that a message from a client just came in for a particular
    transaction. Oracle is not currently planning to provide an X/Open
    communication resource manager, so we don't have any plans right now
    to do XA+. Version 2 of the DTP model paper from X/Open describes it.
    The status of the current XA+ specification is "snapshot".
    When would I choose an Oracle-managed transaction vs a TPM-managed
    transaction?
    Oracle Server is very efficient at managing its own transactions. If
    the TPM manages the transaction, in general some additional overhead
    will be incurred.
    The two main reasons a customer might prefer to use a TPM-managed
    transaction are as follows:
    (1) He may need to update RMs from different vendors. Experience so far
    has been that the most common case is wanting to update both Oracle and
    a TP Monitor managed resource such as a transactional queuing service
    in the same transaction (see Article 3).
    (2) He may want to use the model of having several different services in
    a transaction, even to the same database. For example, the
    "debit_credit" service could be split into a "debit" service and a
    "credit" service. This is a very attractive model, but this type of
    modularity does exact a performance penalty (see Article 4).
    Can I get a version of XA to run on Oracle Server version 6?
    No, the XA functionality uses two underlying mechanisms in the Oracle
    Server which are not available in version 6: two-phase commit and
    session switching. The upi calls for these functions do not not exist
    in version 6.
    When would I use XA vs Oracle7 to coordinate all-Oracle distributed
    transactions?
    Generally speaking, Oracle Server should be used to coordinate all-Oracle
    distributed transactions. The main reason for using XA to coordinate
    transactions would be that you want to use the TP Monitor service-oriented
    architecture. That is, you would like to construct an application built of
    services and service requests in order to benefit from the modularity and
    workload control such an environment provides.
    TP Monitor Application Architecture
    ===================================
    What might a TP Monitor application look like?
    Most TPM applications will consist of two more more programs, where
    there are front-end client programs which request services and back-end
    server programs which provide services. In this case, the TPM supplies an
    additional capability which is transactional communication. The client
    describes the boundaries of the transaction, through the use of the TX API,
    and the TPM relays that transaction information to each requested service.
    The overall application structure generally looks like the following in the
    client-server model. The "TP Monitor Services" box is not necessarily a
    process. It could be one or more processes, or just libraries coordinating
    through shared memory. Each client process and server process could be on
    a different machine. Normally, the application server processes would be
    connected to their Oracle Server processes using the IPC driver; the TPM
    would be used to deliver messages between application client processes on
    one machine and application server processes on another. However, the
    application server processes could also be connected with the standard
    Oracle SQL*Net to shadow processes on different machines. This might be
    useful if one of the databases was on a machine which did not support TPMs.
    |Application| |Application| |Application|
    | Client 1 | | Client 2 | | Client 3 |
    | | | | | |
    \ TPM API | TPM API / TPM API
    | |
    | TP Monitor Services |
    | |
         | --------------------- |
    | | Transaction Manager | |
    ---------------|---------------|---------------------
    TPM API | | XA | XA | TPM API
    | | inter- | inter- |
              | | face | face |
              | | | |
    ----------- | | -----------
    |Application| | | |Application|
    | Server 1 |--- ---| Server 2 |
    | (Pro*C) | | | | (Pro*C) |
    | SQL | SQL
    | | | |
    | Resource ----------- ----------- |
    | Manager | | | | |
    | | Oracle7 | | Oracle7 | |
    | | Server | | Server | |
    | | Process | | Process | |
    | | | | | |
    | ----------- ----------- |
    | | | |
    | ----------------------------------------------------- |
    | | | |
    | | SGA | |
    | | | |
    | ----------------------------------------------------- |
    | |
    Application client programs might be written in C and be linked with
    TPM libraries. Alternatively, they could use a screen painter product.
    Application server programs would be written in Pro*C or Pro*COBOL and
    be linked with TPM libraries, the normal Oracle7 user-side libraries
    and libxa.a. The Oracle7 Server process is the regular Oracle7 executable.
    More complicated application architectures can also be constructed. Most of
    the TPMs allow a server to become a client of another service, so you can
    involve additional servers.
    Could I use Oracle7's Multi Threaded Server as the SQL*Net connection in the
    previous picture?
    Yes, but that will not be needed in many cases. For example, both
    application server processes in the previous picture could talk to a
    single Oracle7 Server process through the Multi Threaded Server in the
    previous picture. However, since the TPM architecture typically reduces
    the number of server processes, the reduction in processes using Multi
    Threaded Server may be less significant than in an architecture without
    TPMs. If the application will use database links, however, then MTS will
    be required.
    How do I write an Oracle TP Monitor application?
    The actual API used to talk to the TPM varies between vendors, so you need
    to get the documentation from the vendor. However, all have a way to
    indicate where a transaction begins and ends and a way to send a request
    and receive a response from a client to a server. Some use an RPC model,
    some use a pseudo-RPC model, and some use a send/receive model. The TX API
    described earlier is a subset of the TPM API as defined by each of
    the TPM providers.
    The client program and server program might look something like the
    following examples. We h (such as Tuxedo's
    "tpacall
    Reference Ducumment
    ---------------------

    hello,
    the role is the same on all plattforms. the reports server takes requests for running reports, spawns an engine that executes the request. in addition to that, the server also provides scheduling services and security features for the reports environment.
    regards,
    the oracle reports team

  • While starting the Bam Server getting the error(JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)).

    Hi All,
    i am trying to start the BAM server  in Windows7 local Machine,in AdminConsole , after starting the NodeMAnager in CMD.
    -->i got the server status as failed , i ahve ched the logs in E:\Oracle\Middleware\user_projects\domains\Soa_domain\servers\bam_Server1\logs\bam_server1.out 
    i could see the following error.
    starting weblogic with Java version:
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    Starting WLS with line:
    C:\PROGRA~1\Java\JDK16~1.0_4\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE  -Xms768m -Xmx1536m -XX:PermSize=256m -XX:MaxPermSize=768m -Dweblogic.Name=bam_server1 -Djava.security.policy=E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=E:\Oracle\Middleware\user_projects\domains\Soa_domain\servers\bam_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans...   -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=E:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=E:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=E:\Oracle\MIDDLE~1\WLSERV~1.3\server  -Dcommon.components.home=E:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=E:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\bam_server1 -Doracle.domain.config.dir=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1  -Digf.arisidbeans.carmlloc=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml  -Digf.arisidstack.home=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\bam_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=E:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,E:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1,E:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol  -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false  -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=E:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=E:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=E:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=E:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=E:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://[2001:0:5ef5:79fb:4b5:2a1f:3f57:fdf8]:7001  -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=E:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;E:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath  weblogic.Server
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    <Jul 8, 2013 10:25:15 AM> <FINEST> <NodeManager> <Waiting for the process to die: 6800>
    <Jul 8, 2013 10:25:15 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Jul 8, 2013 10:25:16 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    after that i changed the Listen port number of bam_server1 to from 9001 to 9003 and NodeManager from 5556 to 5557 , after that i restarted the NodeManager Still getting same error.
    NodeManager after restart running on old Listen port,it is not running on 5557
    NodeManagerHome=E:\Oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1
    ListenAddress=
    ListenPort=5556
    ListenBacklog=50
    SecureListener=true
    AuthenticationEnabled=true
    NativeVersionEnabled=true
    CrashRecoveryEnabled=false
    JavaHome=C:\PROGRA~1\Java\JDK16~1.0_4\jre
    StartScriptEnabled=true
    StopScriptEnabled=false
    StartScriptName=startWebLogic.cmd
    StopScriptName=
    LogFile=E:\Oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1\nodemanager.log
    LogLevel=INFO
    LogLimit=0
    LogCount=1
    LogAppend=true
    LogToStderr=true
    LogFormatter=weblogic.nodemanager.server.LogFormatter
    DomainsFile=E:\Oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1\nodemanager.domains
    DomainsFileEnabled=true
    StateCheckInterval=500
    UseMACBroadcast=false
    DomainRegistrationEnabled=false
    DomainsDirRemoteSharingEnabled=false

    Hi All,
    i am trying to start the BAM server  in Windows7 local Machine,in AdminConsole , after starting the NodeMAnager in CMD.
    -->i got the server status as failed , i ahve ched the logs in E:\Oracle\Middleware\user_projects\domains\Soa_domain\servers\bam_Server1\logs\bam_server1.out 
    i could see the following error.
    starting weblogic with Java version:
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    Starting WLS with line:
    C:\PROGRA~1\Java\JDK16~1.0_4\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE  -Xms768m -Xmx1536m -XX:PermSize=256m -XX:MaxPermSize=768m -Dweblogic.Name=bam_server1 -Djava.security.policy=E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=E:\Oracle\Middleware\user_projects\domains\Soa_domain\servers\bam_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans...   -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=E:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=E:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=E:\Oracle\MIDDLE~1\WLSERV~1.3\server  -Dcommon.components.home=E:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=E:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\bam_server1 -Doracle.domain.config.dir=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1  -Digf.arisidbeans.carmlloc=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml  -Digf.arisidstack.home=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\bam_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=E:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,E:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1,E:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol  -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false  -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=E:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=E:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=E:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=E:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=E:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=E:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://[2001:0:5ef5:79fb:4b5:2a1f:3f57:fdf8]:7001  -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=E:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;E:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath  weblogic.Server
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    <Jul 8, 2013 10:25:15 AM> <FINEST> <NodeManager> <Waiting for the process to die: 6800>
    <Jul 8, 2013 10:25:15 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Jul 8, 2013 10:25:16 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    after that i changed the Listen port number of bam_server1 to from 9001 to 9003 and NodeManager from 5556 to 5557 , after that i restarted the NodeManager Still getting same error.
    NodeManager after restart running on old Listen port,it is not running on 5557
    NodeManagerHome=E:\Oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1
    ListenAddress=
    ListenPort=5556
    ListenBacklog=50
    SecureListener=true
    AuthenticationEnabled=true
    NativeVersionEnabled=true
    CrashRecoveryEnabled=false
    JavaHome=C:\PROGRA~1\Java\JDK16~1.0_4\jre
    StartScriptEnabled=true
    StopScriptEnabled=false
    StartScriptName=startWebLogic.cmd
    StopScriptName=
    LogFile=E:\Oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1\nodemanager.log
    LogLevel=INFO
    LogLimit=0
    LogCount=1
    LogAppend=true
    LogToStderr=true
    LogFormatter=weblogic.nodemanager.server.LogFormatter
    DomainsFile=E:\Oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1\nodemanager.domains
    DomainsFileEnabled=true
    StateCheckInterval=500
    UseMACBroadcast=false
    DomainRegistrationEnabled=false
    DomainsDirRemoteSharingEnabled=false

  • How to Create an Oracle BAM Server Connection?

    I m following the steps at the end of this post to create the connection but at the end I m getting this message from JDev:
    {Unable to write to
    /C:/JDeveloper/mywork/Application1/.adf/META-INF/connections.xml
    because it is a read-only. Either make it writable or allow it to be made writable through source control.}
    it creates the directory C:/JDeveloper/mywork/Application1/.adf/META-INF/ with only a adf-config.xml file but NOT the connections.xml any one knows what is wrong?
    Bellow is the stpes I m following. Its exactly what is written at the Oracle Fusion Middleware Developer´s guide for Oracle SOA Suite 11g Release 1(11.1.1) E10224-01
    To create an Oracle BAM connection:
    1. Select New from the File main menu in Oracle JDeveloper.
    The New Gallery dialog opens.
    2. Choose Connections from the General category.
    3. Select BAM Connection in the Items list, and click OK.
    The BAM Connection wizard opens.
    4. Provide a name for the connection. Leave the Create Connection In selection as
    Application Resources.
    5. Click Next.
    6. Enter the following connection information about the Oracle BAM instance.
    7. Click Next.
    8. Test the connection by clicking Test Connection. If the connection was successful,
    the following message appears:
    Passed.
    9. Click Finish.
    Note: You can create connections to Oracle BAM in the Oracle
    JDeveloper Resource Palette as well as the Application Resources
    panel of a specific application. It is recommended that you create these
    connections in the Application Resources pane rather than the
    Resource Palette.
    Field Description
    BAM Web Host Enter the name of the host on which the BAM report server and
    Web server are installed. In most cases, the BAM Web host and
    Oracle BAM Server host are the same.
    BAM Server Host Enter the name of the host on which the Oracle BAM Server is
    installed.
    User Name Enter the Oracle BAM Server user name (typically bamadmin).
    Password Enter the password of the user name.
    HTTP Port Enter the port number or accept the default value of 8888. This is
    the HTTP port for the BAM Web host.
    RMI Port Enter the port number or accept the default value of 9085. The
    RMI port is for the BAM report cache, which is part of the Oracle
    BAM Server.
    Use HTTPS Select this check box if you want to use secure HTTP (HTTPS) to
    connect to the Oracle BAM Server during design time.
    Otherwise, HTTP is used.
    Message was edited by:
    Mario.Mesquita

    Ok that will be nice, but is not the case I dont want to read the tutorial, the problem is I already start to read and execute the tutorial you told me the problem is this tutorial it doesnt show how to do everything from scratch because you already have inside the zip file everything like xmls etc etc, and I want to get my DO and create the process myself, I dont want to get something that it is already done, this tutorial does not show for example how to create this composite.xml, this file it is already inside the zip file, so this way I just follow half of the process and dont learn how to make the whole process.
    tks

  • SOA managed server and SOA infra not starting

    Hi
    I have my database and listener up and running. I can also successfully start SOA Administration server.
    But I am unable to start SOA managed server. I can see SOA managed server getting started with WARNING and SOA infra always fails to start.
    I tried using both from command line as well as from NodeManager but without any luck. As a result I am unable to proceed with Deployment as soa_server1 does not appear in Step 4 in Jdeveloper deployment GUI dialog. I would also like to ask from the Gurus:
    How can I start soa-infra alone as I cannot see any command from the command line to individually start soa-infra ?
    Here is my part of output from soa_server1. The exception errors keep logging in loop and the file is growing. I had to terminate the process:
    <Jun 3, 2010 10:40:03 PM> <INFO> <NodeManager> <Server output log file is '/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.out'>
    ** Setting up SOA specific environment...
    EXTRA_JAVA_PROPERTIES= -da:org.apache.xmlbeans...
    LD_LIBRARY_PATH=/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/native:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/lib/i386/jrockit:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/lib/i386:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/../lib/i386:/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/native:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/thirdparty/edifecs/XEngine/bin
    USER_MEM_ARGS=-Xms512m -Xmx512m
    ** End SOA specific environment setup
    ** SOA specific environment is already set, skipping...
    JAVA Memory arguments: -Xms512m -Xmx512m
    WLS Start Mode=Development
    CLASSPATH=/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/user-patch.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/soa-startup.jar::/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/lib/tools.jar:/home/oracle1/Oracle/Middleware/utils/config/10.3/config-launch.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle1/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.2.0.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle1/Oracle/Middleware/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/home/oracle1/Oracle/Middleware/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.common.adapters_11.1.1/oracle.soa.common.adapters.jar:/home/oracle1/Oracle/Middleware/oracle_common/soa/modules/commons-cli-1.1.jar:/home/oracle1/Oracle/Middleware/oracle_common/soa/modules/oracle.soa.mgmt_11.1.1/soa-infra-mgmt.jar:/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.xdk_11.1.0/xsu12.jar:/home/oracle1/Oracle/Middleware/modules/features/weblogic.server.modules.xquery_10.3.1.0.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/db2jcc4.jar:/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/soa-infra:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/fabric-url-handler_11.1.1.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/quartz-all-1.6.5.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar:/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar:/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/xqrl.jar:/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/lib/tools.jar:/home/oracle1/Oracle/Middleware/utils/config/10.3/config-launch.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle1/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.2.0.jar:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle1/Oracle/Middleware/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/home/oracle1/Oracle/Middleware/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/home/oracle1/Oracle/Middleware
    PATH=/home/oracle1/Oracle/Middleware/wlserver_10.3/server/bin:/home/oracle1/Oracle/Middleware/modules/org.apache.ant_1.7.0/bin:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/bin:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin:/home/oracle1/Oracle/Middleware/wlserver_10.3/server/bin:/home/oracle1/Oracle/Middleware/modules/org.apache.ant_1.7.0/bin:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/jre/bin:/home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin:/u02/app/oracle/product/11.1.0/db_1/bin:/usr/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.6.0_14"
    Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
    BEA JRockit(R) (build R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32, compiled mode)
    Starting WLS with line:
    /home/oracle1/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin/java -jrockit -Xms512m -Xmx512m -Dweblogic.Name=soa_server1 -Djava.security.policy=/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.system.BootIdentityFile=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da -Dplatform.home=/home/oracle1/Oracle/Middleware/wlserver_10.3 -Dwls.home=/home/oracle1/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/home/oracle1/Oracle/Middleware/wlserver_10.3/server -Ddomain.home=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1 -Dcommon.components.home=/home/oracle1/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig -Doracle.server.config.dir=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig/servers/soa_server1 -Doracle.security.jps.config=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig/carml -Digf.arisidstack.home=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/home/oracle1/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dsoa.archives.dir=/home/oracle1/Oracle/Middleware/Oracle_SOA1/soa -Dsoa.oracle.home=/home/oracle1/Oracle/Middleware/Oracle_SOA1 -Dsoa.instance.home=/home/oracle1/Oracle/Middleware/user_projects/domains/domain1 -Dtangosol.coherence.clusteraddress=227.7.7.8 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dcom.sun.management.jmxremote -Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=/home/oracle1/Oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks -Dem.oracle.home=/home/oracle1/Oracle/Middleware/oracle_common -Djava.awt.headless=true -Dbam.oracle.home=/home/oracle1/Oracle/Middleware/Oracle_SOA1 -Dums.oracle.home=/home/oracle1/Oracle/Middleware/Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.2.103:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/oracle1/Oracle/Middleware/patch_wls1032/profiles/default/sysext_manifest_classpath weblogic.Server
    [JRockit] Local management server started.
    <Jun 3, 2010 10:40:15 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>
    <Jun 3, 2010 10:40:21 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
    <Jun 3, 2010 10:40:35 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jun 3, 2010 10:40:35 PM EST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Jun 3, 2010 10:40:36 PM EST> <Notice> <LoggingService> <BEA-320400> <The log file /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Jun 3, 2010 10:40:36 PM EST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.log00281. Log messages will continue to be logged in /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.log.>
    <Jun 3, 2010 10:40:36 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/logs/soa_server1.log is opened. All server side log events will be written to this file.>
    <Jun 3, 2010 10:41:10 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jun 3, 2010 10:41:51 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Jun 3, 2010 10:41:51 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jun 3, 2010 10:43:51 PM EST> <Warning> <Connector> <BEA-190110> <Resource Adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance/operation of WebLogic Server.>
    <Jun 3, 2010 10:43:53 PM EST> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.soa.fabric, Specification-Version: 11.1.1, Implementation-Version: 11.1.1, referenced from: /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/tmp/_WL_user/worklistapp/r8n7fr]. Make sure the referenced optional package has been deployed as a library.>
    <Jun 3, 2010 10:44:07 PM EST> <Warning> <oracle.sdp.messaging.driver.base> <SDP-26024> <Registration of driver Email-Driver did not complete; will retry periodically until messaging server responds.>
    <Jun 3, 2010 10:44:35 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "jsp" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
    <Jun 3, 2010 10:44:46 PM EST> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.soa.fabric, Specification-Version: 11.1.1, Implementation-Version: 11.1.1, referenced from: /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/tmp/_WL_user/soa-infra/ztorh], [Extension-Name: oracle.soa.adapter, Specification-Version: 11.1.1, Implementation-Version: 11.1.1, referenced from: /home/oracle1/Oracle/Middleware/user_projects/domains/domain1/servers/soa_server1/tmp/_WL_user/soa-infra/ztorh]. Make sure the referenced optional package has been deployed as a library.>
    <Jun 3, 2010 10:45:00 PM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "mds-soa": Socket read timed out>
    <Jun 3, 2010 10:45:02 PM EST> <Error> <oracle.mds> <BEA-000000> <
    oracle.mds.lcm.exception.MDSLCMException: MDS-00922: The ConnectionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl" cannot be instantiated.
    weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Socket read timed out
         at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:170)
         at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:188)
         at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
         at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
         at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: oracle.mds.exception.MDSException: MDS-00922: The ConnectionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl" cannot be instantiated.
    weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Socket read timed out
         at oracle.mds.internal.persistence.db.ConnectionManagerFactory.createConnectionManager(ConnectionManagerFactory.java:80)
         at oracle.mds.internal.persistence.db.DBStoreUtils.getConnectionManager(DBStoreUtils.java:389)
         at oracle.mds.persistence.stores.db.DBMetadataStore.checkRepositoryCompatibility(DBMetadataStore.java:815)
         at oracle.mds.persistence.stores.db.DBMetadataStore.checkCompatibility(DBMetadataStore.java:1092)
         at oracle.mds.persistence.stores.db.DBMetadataStore.<init>(DBMetadataStore.java:276)
         at oracle.mds.internal.lcm.MDSLCMManager.createMetadataStore(MDSLCMManager.java:2064)
         at oracle.mds.internal.lcm.deploy.DeployManager.createMetadataStore(DeployManager.java:660)
         at oracle.mds.internal.lcm.deploy.DeployManager.deployToDBRepository(DeployManager.java:974)
         at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:445)
         at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:168)
         at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:160)
         at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:188)
         at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
         at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
         at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    Hi
    Thanks for your reply
    Here is my installation details on Linux 32 bit OS:
    Weblogic server- wls1032_linux32.bin
    Repository Creation Utility- ofm_rcu_linux_11.1.1.2.1_disk1_1of1.zip
    SOA Suite- ofm_soa_generic_11.1.1.2.0_disk1_1of1.zip
    JDeveloper Studio, base install- jdevstudio11112install.jar
    SOA Extension for JDeveloper- ofm_osb_generic_11.1.1.3.0_disk1_1of1.zip
    The installation went very smooth and there was no errors in the same.
    I can successfully start the Weblogic Administration server from the command line but unable to start successfully SOA Managed (soa_server1), Infra and BAM server (bam_server1). I tried starting SOA Managed (soa_server1) from command line as well as from Weblogic console EM (after starting Node Manager) but always receiving the errors I uploaded in my post earlier. As a result I am unable to deploy any composite application
    Please advice
    Thanks
    Rohit

  • Model and MetaData configarations  in JCO Connection

    Hi all,
               while creating new model i used Load Balance option instead of Single Server.So while creating JCO connection what should be selected for ApplicationData and MetaData radio buttons.The error which i am got aftet deploying and running is
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
    Is this error is because of LoadBalance configarartion while creating JCO for Destinations or at the client num which we gave at the starting step of creating JCO
    Regards
    Padma N

    i got similar problem and this is how i resolved
    this is because jco connections are Using SSO and the user who is accessing that webdynpro application is not present in the backend system.
    please make sure user is there in the backend system from which you are getting data
    xxxxxxxxxxxxxxxxxxxxxxx
    Edited by: Armin Reichert on Feb 18, 2008 7:26 PM

  • Oracle BAM server doesn't start up

    Hi, I have a BAM server in a cluster and start up sometimes and not others.
    When started shuts down unexpectedly.
    Logs files doesn't show errors.
    =============================================================================================
    startWebLogic.cmd console show a "million" times, stop when shutdown server
    "(Warning) (oracle.mds) (BEA-000000) (A call to flushChanges on the current MDSSession does not specify the correct transaction key)"
    ==============================================================================================
    startManagedWebLogic.cmd console show this:
    There are 1 nested errors:
    weblogic.management.ManagementException: [Management:141247]The configuration di
    rectory C:\Oracle\Middleware\wlserver_10.3\common\bin\config does not exist and
    the admin server is not available.
            at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyle
    Config(RuntimeAccessImpl.java:200)
            at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(Runtim
    eAccessImpl.java:115)
            at weblogic.management.provider.internal.RuntimeAccessService.start(Runt
    imeAccessService.java:41)
            at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesMan
    ager.java:461)
            at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServ
    icesManager.java:166)
            at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
            at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
            at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
            at weblogic.Server.main(Server.java:71)
    >
    <16/04/2014 11h'07 ART> <Notice> <WebLogicServer> <BEA-000365> <Server state cha
    nged to FAILED>
    <16/04/2014 11h'07 ART> <Error> <WebLogicServer> <BEA-000383> <A critical servic
    e failed. The server will shut itself down>
    <16/04/2014 11h'07 ART> <Notice> <WebLogicServer> <BEA-000365> <Server state cha
    nged to FORCE_SHUTTING_DOWN>
    Thanks!

    See the below error :
    The configuration directory C:\Oracle\Middleware\wlserver_10.3\common\bin\config does not exist and  the admin server is not available.
    It clearly mentions that config.xml file was not found - which is needed for the Admin Server to start. Check in the above location if one exists or not.

Maybe you are looking for

  • Things to know before building a Mega 651 (and other things you should know afte

    Okay, following hot on the heels of the "things to know" series on Mega 180 and 865, I thought I'd just chip in with this short post on what you should know before splashing out on a nice budget Mega 651 PROCESSOR SUPPORT: The official list of suppor

  • ABAP Dump when calling Function Module Starting New Task

    Hi all. I have a tricky situation now, I am doing a POC on parallel processing. I am getting an ABAP dump on the following Call Function line which is in class lcl_steer_114numc (See below for full program): METHOD start.     CALL FUNCTION 'Z_ZZCLS_S

  • Cannot Access Array Issue

    I cant seem to get the array to be read from outside of the public MyBuffer part of the class. I need to be able to access theArray from the rest of the class. Does anyone know what I did wrong here? Thanks! public class MyBuffer<T> extends Object im

  • Can't Edit

    When i go into iTunes and click on a song and say "Get Info" everything is greyed out. How can i change that? PS it is even on songs i imported myself

  • MacBook Pro crash report - endless loop

    Hi, several weeks ago i found my Macbook getting slower and slower. Surfing is a mess with some tabs open and i only can dream about to work multitasking-like. Sometimes i have to wait around 30secs after just one click, for example, changing the tab