Error Codes customisation in OSB

Hi,
I am using OSB 10gR3. My scenario is as follows:
WSDL Proxy Service1 --> JMS Business Service1 --> RequestQueue --> processing --> ResponseQueue --> JMS Business Service1 --> WSDL Proxy Service1
It is a synchronous call.
If the RequestQueue is down OR there is a Timeout, I want to send a customised error message back to the caller (not the one which OSB sends) in the following format:
<error>
<errorCode>12345</errorCode>
<errorDescription>Connection Failed</errorDescription>
</error>
Is this possible?
Please help!!
Thanks in advance!!
Regards,
Karthik

Creating Custom Error Codes in OSB
Send custom error xml in response in osb
OSB 10gR3: Custom Error Handler (and Raise Error Action)
Regards,
Anuj

Similar Messages

Retry on certain HTTP error code ( OSB 10g)

Hi All,
I want to retry on service call out when i get Http error code 401 for OSB 10g. But don't want to retry on other type of application error or soap fault. What is the best way to implement this? Is there any out of box option to set?
Regards

This is not supported as a out of box option but you can easily set this up in OSB. This is what I did in a similar situation.
PS1( with service callout, in the service callout check for the custom response which is received from PS2, if the custom response has an error code , it means you received an error from service provider else success )----> BS1(intermediate Business service with retry settings )----> PS2(Proxy service which checks the error code from BS2 in the error handler, if the error is 401 then do a raise error or reply with error else do a reply with success. When we do a reply with error in case of 401 error code the BS1 will retry this operation. In case of reply with success send the error code wrapped in a custom response back to PS1 else send back the response from BS2 ,This PS1 cannot be a local proxy service. )----> BS2--> call the service provider.

OSB Error codes

What OSB error codes,I have to handle in the error handler stage when a route node finds that the given end point is not available and also when the end system is timing out.
Is it BEA-38000?
Thanks.

You should test various scenarios in your setup and check which errors you get in different scenarios. There can be many and the error codes will depend on type of transport as well (HTTP, FTP, FIle etc)
In case of Server found but service not available, you should get BEA-380000 error code with Not Found in description:
<con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-380000</con:errorCode>
     <con:reason>Not Found</con:reason>
     <con:location>
     <con:node>RouteNode1</con:node>
     <con:path>response-pipeline</con:path>
     </con:location>
     </con:fault>In case server not running on same port:
<con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-380000</con:errorCode>
     <con:reason>General runtime error: Socket Closed</con:reason>
     <con:location>
     <con:node>RouteNode1</con:node>
     <con:path>request-pipeline</con:path>
     </con:location>
     </con:fault>In case of Timeout set on Business Service triggering (Target service still processing and Socket gets closed because of preconfigured timeout value on BS), you should get BEA-380000 error code with SocketTimeOut exception stacktrace in Description.
<con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-380000</con:errorCode>
     <con:reason>
     [WliSbTransports:381304]Exception in HttpOutboundMessageContext.RetrieveHttpResponseWork.run: java.net.SocketTimeoutException
java.net.SocketTimeoutException
at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse$SocketTimeoutNotification.<clinit>(AsyncResponseHandler.java:551)
at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse.handleTimeout(AsyncResponseHandler.java:396)
at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse.timeout(AsyncResponseHandler.java:502)
at weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:1052)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
     </con:reason>
     <con:location>
     <con:node>RouteNode1</con:node>
     <con:path>response-pipeline</con:path>
     </con:location>
     </con:fault>In case of Timeout while obtaining connection to remote server:
          <con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-380000</con:errorCode>
     <con:reason>General runtime error: connect timed out</con:reason>
     <con:location>
     <con:node>RouteNode1</con:node>
     <con:path>request-pipeline</con:path>
     </con:location>
     </con:fault>

Error while calling secured OSB proxy from BPEL

Hi,
I have a OSB Proxy service to which I have applied OWSM Policy:
oracle/wss_username_token_service_policy
In the Setting:
Process WS-Security Header is set to Yes
While calling this Proxy from BPEL I tried to append binding properties, I tried the following options:
option1:
wsseHeaders=credentials
wssePassword=welcome1
wsseUsername=weblogic
option2:
oracle.webservices.auth.password=welcome1
oracle.webservices.auth.username=weblogic
But neither of them work and I get the following error:
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-386200</con:errorCode>
<con:reason>General web service security error</con:reason>
<con:location>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
<Sep 21, 2010 9:49:30 AM PDT> <Error> <OSB Security> <BEA-387022> <An error ocur
red during web service security inbound request processing [error-code: Security
HeaderUnmarshallingError, message-id: 3659922647318344420--645cdd1d.12b2fe0c158.
-7e45, proxy: OSBTest/Proxy Services/PrivatePersonnelDB_PS, operation: null]
--- Error message:
oracle.wsm.security.SecurityException: WSM-00069 : The security header is missin
g.
at oracle.wsm.security.policy.scenario.processor.UsernameTokenProcessor.
verify(UsernameTokenProcessor.java:218)
at oracle.wsm.security.policy.scenario.executor.WssUsernameTokenScenario
Executor.receiveRequest(WssUsernameTokenScenarioExecutor.java:123)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor
.execute(SecurityScenarioExecutor.java:530)
at oracle.wsm.policyengine.impl.runtime.AssertionExecutor.execute(Assert
ionExecutor.java:41)
at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.executeS
impleAssertion(WSPolicyRuntimeExecutor.java:608)
Truncated. see log file for complete stacktrace
I have even tried to enable HTTP basic Authentication for the service, but did not work.
Any help is highly appreciated.
Thanks.

Hi,
I have applied oracle/wss_username_token_service_policy for my proxy service and trying to test that from OSB Test Console. I am getting below error,
"[OSB Security - OWSM:387253]Failed to initialize Owsm Credential Manager. Please validate the Keystore Configuration"
When i have launched Test Console for this proxy, i have observed in Security part, oracle/wss_username_token_client_policy is appearing. I am not sure why oracle/wss_username_token_client_policy is appearing there when i applied oracle/wss_username_token_service_policy to my proxy service.
Also do i have to need to configure any Keystore for oracle/wss_username_token_service_policy, If so please tell me the process.
If no key store is required where will the credentials be stored.
Thanks
Rajesh

Why do I get -18001 Errors using Customised TestStand User Interface

Hi all
I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
If anyone
has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
Thanks
Dave

David,
I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
LabVIEW : VI is not executable.
An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
2) The same error will occur when
a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
Building The Operator Interface
The following are steps if you are using a LabVIEW operator interface.
1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
Creating a LabVIEW Run-time Server
If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
Assembling the Test VIs for Run-Time Distribution
This distribution process uses one of the shipping TS examples that calls LV VIs.
1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
3) Confirm that the sequence runs without problem.
4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
6) Set the target directory to be something distinct like C:\temp\AssblVIs.
7) If you are using TestStand 2.0 skip adding Dynamic VIs
8) Save with or without diagrams. Its your choice.
Change Search Directories
Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
1) In the sequence editor select Configure>>Search Directories.
2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
3) Close the Edit Search Directories dialog box.
4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
1) In the sequence editor select Configure>>Adpaters.
2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
Distributing Components
-To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
-To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
-You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
Hope this helps.
Regards,
Kitt
=========================================
Title:
Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
Components that need to be distributed:
TS engine
Operator interface
LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
LabVIEW run-time engine
LabVIEW test VIs
Test sequence files
Actions before distributing:
It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
Assemble the test VIs for distribution.
Update the TestStand search directories so that the sequences reference the assembled VIs.
Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
Test the distribution components on the development machine.
Enter section headings, separating each section with a line break:
TS Engine Component
Operator Interface Component
LabVIEW ActiveX Server
Configuring the LabVIEW Standard Prototype Adapter
LabVIEW Run-time Engine Component
Assembling your Test VIs for Distribution
Note
TS Engine Component
With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
Operator Interface Component
You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
LabVIEW ActiveX Server
You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
Configuring the LabVIEW Standard Prototype Adapter
When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
LabVIEW Run-time Engine Component
If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
Assembling your Test VIs for Distribution
After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
Links: See Distributing LabVIEW Test VIs below
Note
Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
==============================================

Error in transformation in OSB

Hi all,
I am getting following error in transformation in OSB console:
<con:reason>
    OSB Assign action failed updating variable "PaymentRequestsPCMToEBS": com.bea.wli.common.xquery.XQueryException: Error parsing XML: {err}XP0006: "element {http://schemas.xmlsoap.org/soap/envelope/}Body { {http://www.w3.org/2004/07/xpath-datatypes}untypedAny }": bad value for type element {http://xmlns.oracle.com/pcbpel/adapter/db/top/PollPaymentStatusDB}StgPcmInPaymentReqCollection { {http://www.w3.org/2001/XMLSchema}anyType }
    </con:reason>
If I test the same in OEPE then there are no errors.
Here is the payload:
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<pay:InputParameters xmlns:pay="http://xmlns.oracle.com/pcbpel/adapter/db/sp/PaymentStatus">
    
    <pay:P_INT_NAME>string</pay:P_INT_NAME>
    
    <pay:P_SOURCE_MESSAGE_REF>string</pay:P_SOURCE_MESSAGE_REF>
    
    <pay:P_SOURCE_ENTITY_REF>string</pay:P_SOURCE_ENTITY_REF>
    
    <pay:P_HEADER_REC>
        
        <pay:INTERFACE_SOURCE_CODE>string</pay:INTERFACE_SOURCE_CODE>
        
        <pay:BATCH_ID>string</pay:BATCH_ID>
        
        <pay:GROUP_CODE>string</pay:GROUP_CODE>
        
        <pay:HEADER_DESCRIPTION>string</pay:HEADER_DESCRIPTION>
        
        <pay:PR_NUMBER>string</pay:PR_NUMBER>
        
        <pay:HEADER_ATTRIBUTE3>string</pay:HEADER_ATTRIBUTE3>
        
        <pay:HEADER_ATTRIBUTE4>string</pay:HEADER_ATTRIBUTE4>
        
        <pay:NOTE_TO_BUYER>string</pay:NOTE_TO_BUYER>
        
        <pay:DELIVER_TO_REQUESTOR_NAME>string</pay:DELIVER_TO_REQUESTOR_NAME>
        
        <pay:CURRENCY_CODE>string</pay:CURRENCY_CODE>
        
        <pay:EXPENDITURE_ORGANIZATION_CODE>string</pay:EXPENDITURE_ORGANIZATION_CODE>
        
        <pay:ORGANIZATION_CODE>string</pay:ORGANIZATION_CODE>
        
        <pay:SUGGESTED_VENDOR_NAME>string</pay:SUGGESTED_VENDOR_NAME>
        
        <pay:SUGGESTED_VENDOR_ID>1000.00</pay:SUGGESTED_VENDOR_ID>
        
        <pay:SUGGESTED_VENDOR_SITE>string</pay:SUGGESTED_VENDOR_SITE>
        
        <pay:SUGGESTED_VENDOR_SITE_ID>1000.00</pay:SUGGESTED_VENDOR_SITE_ID>
        
        <pay:SUGGESTED_VENDOR_CONTACT>string</pay:SUGGESTED_VENDOR_CONTACT>
        
        <pay:SUGGESTED_VENDOR_CONTACT_ID>1000.00</pay:SUGGESTED_VENDOR_CONTACT_ID>
        
        <pay:SUGGESTED_VENDOR_PHONE>string</pay:SUGGESTED_VENDOR_PHONE>
        
        <pay:ACCRUAL_ACCOUNT_ID>1000.00</pay:ACCRUAL_ACCOUNT_ID>
        
        <pay:VARIANCE_ACCOUNT_ID>1000.00</pay:VARIANCE_ACCOUNT_ID>
        
        <pay:BUDGET_ACCOUNT_ID>1000.00</pay:BUDGET_ACCOUNT_ID>
        
        <pay:AMOUNT>1000.00</pay:AMOUNT>
        
        <pay:CERTIFIED_DATE>2008-09-29T02:49:45</pay:CERTIFIED_DATE>
    </pay:P_HEADER_REC>
    
    <pay:P_LINES_TAB>
        
        <pay:P_LINES_TAB_ITEM>
            
            <pay:QUANTITY>1000.00</pay:QUANTITY>
            
            <pay:UNIT_OF_MEASURE>string</pay:UNIT_OF_MEASURE>
            
            <pay:UNIT_PRICE>1000.00</pay:UNIT_PRICE>
            
            <pay:ITEM_SEGMENT1>string</pay:ITEM_SEGMENT1>
            
            <pay:CHARGE_ACCOUNT_SEGMENT1>string</pay:CHARGE_ACCOUNT_SEGMENT1>
            
            <pay:CHARGE_ACCOUNT_SEGMENT2>string</pay:CHARGE_ACCOUNT_SEGMENT2>
            
            <pay:CHARGE_ACCOUNT_SEGMENT3>string</pay:CHARGE_ACCOUNT_SEGMENT3>
            
            <pay:CHARGE_ACCOUNT_SEGMENT4>string</pay:CHARGE_ACCOUNT_SEGMENT4>
            
            <pay:CHARGE_ACCOUNT_SEGMENT5>string</pay:CHARGE_ACCOUNT_SEGMENT5>
            
            <pay:CHARGE_ACCOUNT_SEGMENT6>string</pay:CHARGE_ACCOUNT_SEGMENT6>
            
            <pay:CHARGE_ACCOUNT_SEGMENT7>string</pay:CHARGE_ACCOUNT_SEGMENT7>
            
            <pay:PROJECT_NUM>string</pay:PROJECT_NUM>
            
            <pay:TASK_NUM>string</pay:TASK_NUM>
            
            <pay:EXPENDITURE_TYPE>string</pay:EXPENDITURE_TYPE>
            
            <pay:DESTINATION_ORGANIZATION_CODE>str</pay:DESTINATION_ORGANIZATION_CODE>
            
            <pay:LINE_ATTRIBUTE2>string</pay:LINE_ATTRIBUTE2>
            
            <pay:NEED_BY_DATE>2014-09-19T00:18:33</pay:NEED_BY_DATE>
            
            <pay:DISTRIBUTION_ATTRIBUTE5>string</pay:DISTRIBUTION_ATTRIBUTE5>
            
            <pay:CURRENCY_UNIT_PRICE>1000.00</pay:CURRENCY_UNIT_PRICE>
            
            <pay:CURRENCY_AMOUNT>1000.00</pay:CURRENCY_AMOUNT>
            
            <pay:ITEM_DESCRIPTION>string</pay:ITEM_DESCRIPTION>
            
            <pay:CATEGORY_SEGMENT1>string</pay:CATEGORY_SEGMENT1>
            
            <pay:TAX_CODE>string</pay:TAX_CODE>
            
            <pay:DISTRIBUTION_ATTRIBUTE9>string</pay:DISTRIBUTION_ATTRIBUTE9>
            
            <pay:REMARKS>string</pay:REMARKS>
            
            <pay:LIABLE_FOR_WHT>string</pay:LIABLE_FOR_WHT>
        </pay:P_LINES_TAB_ITEM>
    </pay:P_LINES_TAB>
</pay:InputParameters>
In transformation I am using following code for converting String to Decimal
                    for $vendorSiteId in $stgPcmInPaymentReqCollection1/ns1:StgPcmInPaymentReq[1]/ns1:vendorSiteId
                    return
                        <ns0:SUGGESTED_VENDOR_SITE_ID>{ xs:decimal(data($vendorSiteId)) }</ns0:SUGGESTED_VENDOR_SITE_ID>
Please let me know if I am missing anything.

your payload doesn't seem to be correct.
if you're trying to parse a soap envelop i would expect a soap:Body tag
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<soap:Body>
<pay:InputParameters xmlns:pay="http://xmlns.oracle.com/pcbpel/adapter/db/sp/PaymentStatus">
</soap:Body>

How to get End System error code?

I am trying to access IBM MQ queue from my proxy service which is invoking a business service using OSB Service Callout Action.
Suppose the queue that I am trying to access is not available, OSB is always returning "OSB Service Callout action received an error response" error.
But, I want the Error code and message which are returned by IBM MQ.
Pls. help me to get the IBM error code & message.
I am usiing IBM MQ v7 and OSB 11g
Thanks,
Hari

Can you check the Fault Detail and log the $fault and check.
Edited by: Prabu on Oct 15, 2012 2:46 PM

System error in routine FI_TAX_GET_TXJCD_LEVELS error code 2 function build

I am getting error "System error in routine FI_TAX_GET_TXJCD_LEVELS error code 2 function build" when I am doing release to accounting throught VF02 this error I am getting.Out client is USA client.TAX is picking up from the Veterx interface.Can anybody help regarding this.I checked the Tax prodeuure and also the tax classification everything is assigned properly.

Good Evening,
The reason why you are getting an error when passing the document to
accounting is because your ship-to partner does not have a jurisdiction
code. The error is correctly triggered since the jurisdiction code is
required when shipping to a jurisdictional country. You can't
post this transaction without a jurisdiction code.
If you maintain a tax jurisdiction code on the customer master,
cancel the invoice and rebill, the document should pass to accounting.
The tax jurisdiction code is maintained on the address data screen.
Please check if there is a jurisdiction code maintained in
the customer master data. If that is not the case, check, if the
tax pricing procedure for the country of the customer is set relevant
for jurisdiction code. If the country of the customer is relevant
(entry for pricing procedure) and the customer master has no jur. code
maintained, the error tells exactly that situation. Then, either the co
should be set to not relevant for TXJCD or the customer should get
that customising entry.
Please be aware that if shipping from the US to a non juristiction
country the system should take a dummy jurisdiction code from the OBCL
transaction.
If you have access to OSS notes then please see:
400766 Changes in accounting interface for Rel
112609 How are tax codes transferred to condit
I hope this helps!
Kind Regards,
Martina McElwain
SD Forum Moderator

Mapping error code from Business service to Proxy

I am trying to get hands on with 11g and following the book Getting started with Oralce 11G soa suite. The example I have described is based on chapter 11 and chapter 14. I have a proxy service and business service. The business service calls a "ValidateCC" composite which validates the credit card information passed and is proxied by the proxy service. The validation of CC is done by a stored procedure, which returns an error ora-20001 if the credit card info is not found in the database.
Testing PROXY service from OSB console:
Here is the REQUEST message sent to proxy service:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<soapenv:Body>
<cca:creditcardStatusRequest xmlns:cca="http://www.globalcompany.com/ns/CCAuthorizationService">
<cca:CCNumber>2234-1234-1234-1234</cca:CCNumber>
</cca:creditcardStatusRequest>
</soapenv:Body>
</soapenv:Envelope>
Here is the response message received:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>BEA-380001: Internal Server Error</faultstring>
<detail>
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380001</con:errorCode>
<con:reason>Internal Server Error</con:reason>
<con:location>
<con:node>RouteTo_validationForCC</con:node>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Testing Business service from OSB console
Response received for the same message:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'validateCC' failed due to: Stored procedure invocation error.
Error while trying to prepare and execute the VALIDATECC API.
An error occurred while preparing and executing the VALIDATECC API. Cause: java.sql.SQLException: ORA-20001: UNKNOWN CREDIT CARD
ORA-06512: at "SOADEMO.VALIDATECC", line 12
ORA-06512: at line 1
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</faultstring>
<faultactor/>
<detail>
<exception>
ORA-20001: UNKNOWN CREDIT CARD
ORA-06512: at "SOADEMO.VALIDATECC", line 12
ORA-06512: at line 1
</exception>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
What i need:
I would like to have the exception 20001 populated in faultcode of the response from proxy message. A down stream BPEL process checks the faultcode and processes the message as needed.
My OSB message flow contains :
ValidateCredit +> envelope
PipelinePairNode1
Request Pipeline
Report and Validate
Response Pipeline
RouteTo_validationForCC
Service Error Handler
stage1 with Alert action.
My question is how to map the actual error occured in the cally be business service handler to the Service error handler in stead of throwing a generic BEA error. Please let me know

Thank You Swgt for your reply.
This is what I did:
When I'm in Edit mode, in the OSB Web Console, I go to my proxy service, click on the Edit Message Flow icon, in the Map of Message Flow window I left-click on my Route icon (which as you already mentioned routes to my Business Service), select Add Route Error Handler (this option only appears if you're in Edit Mode already), click on the Error Handler icon, Add Stage, click on the Stage icon, Edit Stage, click on Add an Action, Flow Control -> Reply. Here I select the Radio Button "With Failure" and then Save All and Activate the change for the session.
Is this correct?
I tried this. I no longer get the BEA-380001 error code. However, the fault returned is not a bindingFault as I would have expected, but rather a remoteFault. hence my fault policy never detects it, doesn't rethrow it, and my BPEL error handling never kicks in.
Is there a way to change this to work more or less in the sense of the tutorial?
Does using OSB to connect to the service automatically make it a remote fault, instead of a bindingFault?
Here's the SOAP message handled by my BPEL Component.
<messages>
<input>
<invokeCCStatusService_execute_InputVariable>
<part name="part1">
<creditcardStatusRequest>
<CCNumber>2234-1234-1234-1234</CCNumber>
</creditcardStatusRequest>
</part>
</invokeCCStatusService_execute_InputVariable>
</input>
<fault>
<bpelFault>
<faultType>0</faultType>
<remoteFault>
<part name="summary">
<summary>Beim Aufrufen des Bindings ist eine Exception aufgetreten.
Beim Aufrufen des JCA-Bindings ist eine Exception
aufgetreten: "JCA Binding execute of Reference operation
'validateCC' failed due to: Fehler beim Aufrufen von
gespeicherter Prozedur. Beim Versuch, die VALIDATECC-API
vorzubereiten und auszuführen, ist ein Fehler aufgetreten.
Beim Vorbereiten und Ausführen der VALIDATECC-API ist ein
Fehler aufgetreten. Ursache: java.sql.SQLException:
ORA-20001: UNKNOWN CREDIT CARD ORA-06512: in
"SOADEMO.VALIDATECC", Zeile 12 ORA-06512: in Zeile 1 Prüfen
Sie, ob die API in der Datenbank definiert ist und die
Parameter der API-Signatur entsprechen. Diese Exception wird
als nicht wiederholbar betrachtet. Sie ist wahrscheinlich auf
einen Modellierungsfehler zurückzuführen. Um den Fehler
stattdessen als wiederholbar zu klassifizieren, fügen Sie die
Eigenschaft nonRetriableErrorCodes mit dem Wert "-20001" zum
Deployment-Deskriptor hinzu (d.h. weblogic-ra.xml). Um einen
wiederholbaren Fault automatisch zu wiederholen, legen Sie
folgende Eigenschaften von composite.xml für diesen Aufruf
fest: jca.retry.interval, jca.retry.count und
jca.retry.backoff. Alle Eigenschaften sind Ganzzahlen. ". Der
aufgerufene JCA-Adapter hat eine Ressourcen-Exception
ausgelöst. Prüfen Sie die obige Fehlermeldung sorgfältig, um
eine Lösung zu finden.</summary>
</part>
<part name="detail">
<detail>
<exception>ORA-20001: UNKNOWN CREDIT CARD ORA-06512: in
"SOADEMO.VALIDATECC", Zeile 12 ORA-06512: in Zeile 1</exception>
</detail>
</part>
<part name="code">
<code>{http://schemas.xmlsoap.org/soap/envelope/}Server</code>
</part>
</remoteFault>
</bpelFault>
</fault>
<faultType>
<message>0</message>
</faultType>
</messages>

Cannot delete file from external hard drive (error code 36) in Finder, but Terminal is ok

I have a relatively new Macbook Pro Retina 15" and have a Western Digital 1 TB Passport. I've been using the passport for about a year now without any problems on older Macbooks in my house. I used to be able to read and write to this drive no problem. I am using the Paragon NTFS for Mac software in order to read and write to the NTFS drive. When I navigate through the drive in Finder, if I try to create a new folder, I do not have a problem. If I try to delete that folder I just created, I get this error:
The Finder can’t complete the operation because some data in “untitled folder” can’t be read or written.
(Error code -36)
The folder has nothing in it whatsoever. I just created it. But if I go to Terminal and I run
rm -rf "untitled folder"
This works fine. Why is Terminal acting different than Finder? This does not happen on my other Macbooks. Thanks in advance.

Thanx for such qucik reply!!! The pages were great, it had an answer for my problem, but unfortunately it also involved me dealing with it only on the MacIntosh HD itself, not on mounted external drive I suppose... So it didn't work they say that there is an icon in the left corner indicating locked folder - I don't see any icon on it. It says you can untick the box to unlock the folder - there is no tick to be unticked. Finally, they say that if I don't have permition or rights I cannot delete it. But how do i change permittion which already says that i can read and write in it? So everything appears to be normal only I cannot delete it. there is not even any warnig telling me I don't have enough rights, it just requires the password and after me typing it in it makes the sound of scraping paper but does nothing more. I aslo had some problems with emptying Trash after being seemingly succesful with one file and had got so far to have them appear in the Trash (no clue how this one actully got there though..) I followd the advice and emptied the Trash with Terminal. The Folder is still there but it shows 0 Kb... So far so good BUT: It is still on the external drive, so I obviously only managed to copy it into the Trash!!! Phew, innit a bit too tight to poor owners, this macbook?? I want my rights back!

Report generation failed----error code:-17205; Access Denied.

Hi, All
    i have a trouble about report generation.it seems the error happened at the "write UUT report"--this step is teststand report generation'DLL.
    detail:
    An error occurred calling 'Save' in 'Report' of 'NI TestStand 2010 SP1 API'
Access Denied.. Error writing to file 'D:\program\seq\xxx.xml'.
The file might be open in another application. If file access is intermittently denied, you should try disabling the Microsoft FindFast utility.
    error code:-17205; Access Denied.
    locationtep 'Write UUT Report' of sequence 'Single Pass' in 'SequentialModel.Seq'
    How to fix it?
    Thanks a lot.
BR

Hm, it looks like the file might be open in another application. If you see that file accesss is intermittently denied, you should try disabling the Microsoft FindFast utility.
CTA, CLA, MTFBWY

There was a recent upadate on my PC, however it does not work. A error code comes up which says, min version is not compatible with max version. And I caanot open my browser. Please help.

I do a system restore which allows me to open my browser. Without this I cannot open my browser - the error code comes up every time.

Do a clean (re)install
* Download a fresh Firefox copy from http://www.mozilla.com/firefox/all.html and save the file to the desktop.
* Uninstall your current Firefox version and remove the Firefox program folder before installing that copy of the Firefox installer.
* Don't remove personal data when uninstalling.
* It is important to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
From https://support.mozilla.com/en-US/questions/764376

My ipod touch is not list as a device on itunes. When I tried do update itunes, I get a ox8007054f error code and the update will not complete.

My ipod touch is not listed as a device when connected to my computer. As suggested I attempted to download the latest of itunes. I got an
ox8007054f error code and the down load will not complete. I have also tried to restore my computer to an earlier setting, but it will
not accept the change.

Have you looked at this completed previos discussion. It discusses 0x8007054F.
Re: Error message when trying to install iTunes

Capturing oracle error codes into a variable

Hi
Can someone show me how it is possible to save an Oracle defined error code into a variable? What I am trying to do is when a stored procedure fails an Oracle error is raised, such as ORA-xxxx, then pass this code into variable to be saved into a log.
How do I achieve this?

user633278 wrote:
How do I achieve this?Function SQLCODE in PL/SQL exception handler returns error code. SQLERRM returns message:
SQL> declare
2      x number;
3 begin
4      x := 1/0;
5    exception
6      when others
7        then
8          dbms_output.put_line('Error code: ' || SQLCODE);
9          dbms_output.put_line('Error message: ' || SQLERRM);
10 end;
11 /
Error code: -1476
Error message: ORA-01476: divisor is equal to zero
PL/SQL procedure successfully completed.
SQL> SY.

Error Code:942 While Scheduling a report in BI Publisher

Hi All,
I am trying to schedule one report in BI Publisher.
After Clicking Submit Button while scheduling report,i get following error:
Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.0.0) (Build 080319)): oracle.toplink.exceptions.DatabaseException Internal Exception: java.sql.SQLException: ORA-00942: table or view does not exist Error Code: 942 Call: UPDATE SEQUENCE SET SEQ_COUNT = SEQ_COUNT + 50 WHERE SEQ_NAME = 'JOB_ID_SEQ' Query: DataModifyQuery()
Kindly Help me in resolving this issue
Regards
Amrita Singh

i know the issue,i can give quick fix, but in-order to make sure you don't get another glitch like this.
I would recommend, you to install the scheduler in another schema or another db.
Re-installing the scheduler schema tables will fix this.

Error Codes customisation in OSB

Similar Messages

Maybe you are looking for