Monday 10 March 2014

oracle.fabric.common.FabricException

oracle.fabric.common.FabricException: oracle.fabric.common.FabricInvocationException: Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.6.0) (Build 111018)): oracle.toplink.exceptions.DatabaseException
Internal Exception: weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool SOALocalTxDataSource is Suspended, cannot allocate resources to applications..
Error Code: 0: Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.6.0) (Build 111018)): oracle.toplink.exceptions.DatabaseException
Internal Exception: weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool SOALocalTxDataSource is Suspended, cannot allocate resources to applications..
Error Code: 0


Whenever you receive oracle.fabric.common.FabricException in SOA check that your database is running or that tablespace is good.

Because SOA BPEL is stateful in won't work without database.


Monday 10 February 2014

How to add sequence numbers in XSLT for EBS AP_Invoice_Interface and AP_Invoice_Lines

Create a valid data-source connection to your database. I have used the EBS Application Adapter to create the sequence number for my InvoiceId.

        <top:invoiceId>
          <xsl:value-of select='oraext:sequence-next-val("AP_INVOICES_INTERFACE_S","jdbc/soa/ebsdev")'/>
        </top:invoiceId>

              <top:invoiceLineId>
                <xsl:value-of select='oraext:sequence-next-val("AP_INVOICE_LINES_INTERFACE_S","jdbc/soa/ebsdev")'/>
              </top:invoiceLineId>

As seen above, you can create the sequence number within xslt pointing it to the data-source configured on your weblogic