ICM Scripting Error Handling Best Practice

Can someone tell me what is the best way to handle errors in ICM scripting. For example false node on Send to VRU or Run Ext Script node, I normally handle this with calltypes for errors and then continue the callflow. But recently I noticed that some of my clients are using peripheral variable to store an error message instead of calltype. I am just wonderinmg which is the best option?

I don't think you need a call type, I usually set PV10 = "Error: XYZ". Creating a call type just seems a little redundant, however it would make it easier on the reporting side as you don't have to create any custom queries to search for a specific error type.
david

Similar Messages

Exception Handling best practices?

Hi, Where can I find the tutorial on exception handling best practices on oracle website?
I am looking for the sun standards for the exception handling.

By the way, the google keywords to find that tutorial are "java exception tutorial". In general to find a Java tutorial on topic X the google keywords are "java X tutorial". Prefer tutorials from Oracle when scanning the list of links you get back.

Script Error : Handler Not Definied

Hi Gurus,
I try to play a Lingo Script with Director MX 2004 but i got
this message: Script Error : Handler Not Definied
The Debug stops at this line in my code: dosRegister
"70BE7B1-13977F4"
Is anything missing from my Xtras folder?
I have DirectOS though.
Any idea ??
Thx

I suspect you have a cast member that uses one of the three
names in the
list and it is not a check box. It's probably before the
actual checkbox
member in the cast so it's finding it first.
Craig Wollman
Lingo Specialist
Word of Mouth Productions
212-928-9581
www.wordofmouthpros.com
"ajrobson" <[email protected]> wrote in
message
news:etn9j1$op2$[email protected]..
>I have a script that get a list of choosen check boxes,
it was working fine
>but
> now when i press the button that calls the script i get
a error saying
> "script
> error property not found" then it lists the line i have
put a * next to
> and
> says #hilite
>
> This is the top part of that script and to my knowlegde
i have not chnaged
> any
> of it and it worked before but now it does not, i also
use a script almost
> identical to this but use it for radiobuttons instead
and the line is the
> same
> in that and that script works, can anybody tell me what
as gone wrong?
>
>
>
> global err
>
> on CheckBoxState -- name of custom handler
> TickedBoxes = [] -- a empty list will be filled where
ever a checkbox is
> ticked
> CheckBoxNames = ["Dr no", "From russia with
love","Casino royale" ]
> repeat with i = 1 to 3 -- repeat for each checkbox
> CurrentCheckbox = CheckBoxNames
> ** if the hilite of member(CurrentCheckbox) then -- if
currentcheckbox
> hilite
> is true (checked)...
> append(TickedBoxes,CurrentCheckbox )
> end if
> end repeat
> return TickedBoxes
> end
>

ESB Exception Handling Best Practices

I've update the "ESB Transactions, Error Handling and Resubmit" Lesson PDF to include a best practices section. Go to http://otn.oracle.com/goto/esb and click on the link in the Learning more section. Feedback welcome.

Hi Dave,
I checked this document yesterday, it contained 18 pages.
Some great info in the additional 7 pages, just in time as well: at a customer site we are hitting bug 5547165, the rejected messages being empty. I checked the rejection handlers for BPEL and was investigating how these could be used in case of ESB. Seems you have provided the answer.
Any chance a fix for the bug mentioned here is in the 10.1.3.3 patch set?
One more thing: by default the rejected messages for ESB are written to file system, in a directory below the 'home' OC4J instance. Could this be turned into a configurable space in a next release?
Thanks and best regards, Sjoerd

Exception handling best practice

whats the best practice for exception handling on ?
- BC
-controller
-view layer (Managed beans)
do we have to handle commit operations on BC so we can rollback like this code
public void save()
// create/update/delete ROW
try
this.getTransaction().commit();
catch(JboException e ){this.getTransaction().rollBack();}
thanks
Edited by: user3674912 on 23/05/2011 05:18 ص

Hi,
IMO, best practices is to handle exceptions as close to their origin. If you can't handle it, you re-throw it as you would in Java so another handler gives it a try
Frank

Simple HTTP Post Handler - Best Practice?

I would like to create a fairly simple ASP.Net application that takes an XML record from an HTTP post request, submits it to a process that invokes a command line app that parses the XML file, takes the parsed XML file (as XML), and returns the result.
For now the process can be synchronous as the transform has to complete and there are no parallel activities that need to be performed.
I'm not sure that writing an HTTP Handler is the way to go, but maybe I'm mistaken. Plus there are no examples of doing that in Visual Studio 2013 using IIS 8.0 or 8.5 and I don't really understand the value of applying a file extension or processing
an HTTP post to initiate the request, perhaps using a dedicated port. I already have a class library for handling the process request.
I'm also a little confused about reading the post request - it seems I can just do it during the page load and that I should be able to extract the first request form field - that of course means using a webform to process the request which seems to be the
most straight-forward way to do this. So I'm looking for the best practice for fielding this kind of request. My target server is Windows 2012, but I'm developing with VS 2013 and C# on Windows 7 using IIS Express and configuring IIS is confusing.
Overall it is a fairly simple app, but there are so many rich new features in VS 2013 (most of my work has been in VS 2005). I also want to build a test app and am looking for the best way to do so, although I think I can build a simple client app
to do that. The business requirements will be to issue the post request from a MarkLogic xquery request which will take care of any JSON wrappers and balance between multiple Windows servers to handle the load.
Thanks for any help with this!
~Tim

Hi Tim,
Thank you for posting in the MSDN forum.
Actually this forum is to discuss the VS IDE, if this issue is related to web development, you could ask this question in the ASP.NET forum:
http://forums.asp.net. If then, you could get an answer more quickly and professional. Thanks for your cooperation.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

ESSCMD in Perl Script - Error handling

Does anyone use Perl scripts to run Esscmd commands? I'm trying to incorporate error handling and I can't seem to get Perl to recognize and error that happened when the Esscmd statement runs. A sample would be much appreciated. The fact that I'm not too familiar with Perl doesn't help! <BR>Thanks much.

Sorted.
Had to change
#!/usr/bin/perl
to
#!/usr/bin/perl --

What are default Zend Session handling best practices to prevent Cross Site Request Forgery?

I have enjoyed the David Powers book Adobe Dreamweaver CS5 with PHP: Training from the Source - and have put many of the examples into practice. I have a security related concern that may be tied to the Zend::Auth example in the book. While this is installed an working on my site:
<?php
$failed = FALSE;
if ($_POST) {
if (empty($_POST['username']) || empty($_POST['password'])) {
    $failed = TRUE;
} else {
    require_once('library.php');
    // check the user's credentials
    try {
      $auth = Zend_Auth::getInstance();
      $adapter = new Zend_Auth_Adapter_DbTable($dbRead, 'user', 'login', 'user_pass', 'sha1(?)');
      $adapter->setIdentity($_POST['username']);
      $adapter->setCredential($_POST['password']);
      $result = $auth->authenticate($adapter);
      if ($result->isValid()) {
        $storage = $auth->getStorage();
        $storage->write($adapter->getResultRowObject(array(
          'ID', 'login', 'user_first', 'user_last', 'user_role')));
        header('Location: /member/index.php');
        exit;
      } else {
        $failed = TRUE;
    } catch (Exception $e) {
      echo $e->getMessage();
if (isset($_GET['logout'])) {
require_once('library.php');
try {
    $auth = Zend_Auth::getInstance();
    $auth->clearIdentity();
} catch (Exception $e) {
    echo $e->getMessage();
Apparently, there is very limited protection against Cross Site Request Forgery, where the resulting SessionID could be easily hijacked? I am using the Zend Community edition (I have 1.11.11).     I have an observation from a client that this authentication is not up to snuff.
To boil it down:
1. Is there a Zend configuration file that might have some settings to upgrade the Session and or authentication security basics? I'm wondering specifically about the settings in /library/Zend/session.php? Ie secure the session against a changing user IP, and invoking some other session handling stuff (time-out etc).
2. If I understand it correctly, "salting" won't help with this, unless it's added/checked via a hidden POST at login time?
Ideally, the man himself, David Powers would jump in here - but I'll take any help I can get!
Thanks!

Might ask them over here.
http://forums.asp.net/1146.aspx/1?MVC
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Best practice for handling errors in EOIO processing on AEX?

Hi,
I'm looing for resources and information describing the best practice on how to handle processing errors of asynchronous integrations with Exactly-Once-In-Order QoS on an AEX (7.31) Java only installation. Most information I've found so far are describing a the monitoring and restart jobs on AS ABAP.
Situation to solve:
multiple different SOAP messages are integrated using one queue with an RFC receiver. On error the message status is set to Holding and all following messages are Waiting. Currently I need to manually watch over the processing, delete the message with status holding and restart the waiting ones.
Seems like I can setup component based message alerting to trigger an email or whatever alert. I still need to decide on how to handle the error and resolve it (ie. delete the errornous message, correct the data at sender and trigger another update). I still need to manually find the oldest entry with status waiting and restart it. I've found a restart job in Background jobs in configuration and monitoring home, but it can be only scheduled in intervals of 1 or more hours.
Is there something better?
Thank you.
Best regards,
Nikolaus

Hi Nikolaus -
AFAIK - For EOIO, you have to cancel the failed message and then process the next message in the sequence manually..
Restart job only works the messages which are in error state but not in holding state.. So you have to manually push the message... So there is no other alternative.
But it should not be that difficult to identify the messages in a sequence..
How to deal with stuck EOIO messages in the XI ... | SCN
Though it is for older version, it should be the same.. you should be able to select the additional columns such as sequence ID from the settings..

Error Handling in OS 10gR3: How To's, Approaches, best practices

I am trying to do error rhandling within OSB 10gR3 and looking for some guidance as to best practices and how to carry out the error handling based on my use-case as -
Consumers ---> GenericProxyExt(WSDL based) ---> GenericProxyInt(Any SOAP) ---> Proxy (Any XML) ---> Business Service --------------> Target Service
Since target web service will pass error in the SOAP:fault, where in the OSB should this error be handled? Also, how can I pass the custom error messages (instead of the one returned from the target service). Do I have to write error handlers in each of the proxy services?
Any insight, sample code, approaches will be helpful
Thanks,
-J

user2629959 wrote:
I am trying to do error rhandling within OSB 10gR3 and looking for some guidance as to best practices and how to carry out the error handling based on my use-case as - Some customer has documented related info www.insemble.com/CustomExceptionHandlingwithOracleServiceBus.pdf
>
Consumers ---> GenericProxyExt(WSDL based) ---> GenericProxyInt(Any SOAP) ---> Proxy (Any XML) ---> Business Service --------------> Target Service
Since target web service will pass error in the SOAP:fault, where in the OSB should this error be handled? Also, how can I pass the custom error messages (instead of the one returned from the target service). Do I have to write error handlers in each of the proxy services?Not sure if I understood your point of using that many proxies for invoking a Target Service.
Since BS throws soap fault, and the last Proxy is AnyXML. You need to do bit of manipulations. First of all for AnyXML services, you have to manually copy $fault into $body. Reason behind this step, is For Any XML there is no concept of $fault being returned and reply with failure. Subsequent proxies will receive the $fault as originated in Target Service. If we want to control the $fault received by the consumers, we have to use error handlers and populate $fault accordingly.
>
Any insight, sample code, approaches will be helpful
Thanks,
-J

Handling Error queue and Resolving issues - Best practices

This is related to Oracle 11g R2 streams replication.
I have a table A in Source and Table B in destination. During the replication by Oracle streams, if there is an error at apply process, the LCR record will go to error queue table.
Please share the best practices on the following:
1. Maintaining error table operation,
2. monitor the errors in such a way that other LCRs are not affected,
3. Reapply the resolved LCRs from error queue back to Table B, and
4. Retain the synchronization without degrading the performance of streams
Please share some real time insight into the error queue handling mechanism.
Appreciate your help in advance.

This is related to Oracle 11g R2 streams replication.
I have a table A in Source and Table B in destination. During the replication by Oracle streams, if there is an error at apply process, the LCR record will go to error queue table.
Please share the best practices on the following:
1. Maintaining error table operation,
2. monitor the errors in such a way that other LCRs are not affected,
3. Reapply the resolved LCRs from error queue back to Table B, and
4. Retain the synchronization without degrading the performance of streams
Please share some real time insight into the error queue handling mechanism.
Appreciate your help in advance.

What is Considered Best Practice for Error Handling in Components?

What would be the best approach to handling errors in custom (possibly composite) components?
I see three different possibilities:
Having the error handling funciton within the component. The problem is that this is not adaptable to the consumers error handling setup (i.e. logging to database, redirecting to a pretty error screen, etc.).
Passing in an error function as a parameter. The problem here is how to have the externally defined error function interact with external elements that are not defined within the component, i.e. passing the error or fault object to a logging class, or something similar, of which the component knows nothing about.
Referencing the external error handling methods directly from within the component. (Of course that's shabby programming, just listing as a technical option.)
How do you solve this?
My goal is to have a versatile custom component that can utilize any given consumer's error handler.
Thanks,
Mike

or define a customized event and dispatch it when error occur, then you can just listen to it outside

Best practice of OSB logging Report handling or java code using publish

Hi all,
I want to do common error handling of OSB I did two implementations as below just want to know which one is the best practice.
1. By using the custom report handler --> When ever we want to log we will use the report action of OSB which will call the Custom java class which
Will log the data in to DB.
2. By using plain java class --> creating a java class publish to the proxy which will call this java class and do the logging.
Which is the best practice and pros and cons.
Thanks
Phani

Hi Anuj,
Thanks for the links, they have been helpful.
I understand now that OSR is only meant to contain only Proxy services. The synch facility is between OSR and OSB so that in case when you are not using OER, you can publish Proxy services to OSR from OSB. What I didn't understand was why there was a option to publish a Proxy service back to OSB and why it ended up as a Business service. From the link you provided, it mentioned that this case is for multi-domain OSBs, where one OSB wants to use the other OSB's service. It is clear now.
Some more questions:
1) In the design-time, in OER no Endpoints are generated for Proxy services. Then how do we publish our design-time services to OSR for testing purposes? What is the correct way of doing this?
Thanks,
Umar

Best Practice for Implementing Exception Handling in BPEL

Hi All,
what is the best practice and the approach to follow Exception Handling in BPEL.
1) Do we need to implement Exception Handling in BPEL as we do in Java, means
     method 3 throws error to method 2 (if any) and
     method 2 throws error to method 1 (if any) and
     finally method 1 throws error to the main Class.
If we replicate the above scenario to BPEL
In BPEL main Scope have Custom Fault, Catch ALL
     Each Invoke is surrounded by a Scope Activity with Remote Fault, Binding Fault & Custom Fault
and follow the paradigm of Java, assuming we have Inner Scopes
     [ OR ]
2) In BPEL main Scope have all exceptions defined like
     Remote Fault,
     Binding Fault,
     anyOther System Fault (selectionFailure / forcedTermination),
     Custom Fault (if required) and
     CatchALL
     and also
     each Invoke is surrounded by a Scopes Acitivity with Custom Fault (business fault) exception Handling
I feel 1st one may not be a good practice, may be i am wrong...
Any Suggestions from experts.
Thanks in Advance
anvv sharma

Hi-
In you can create different scope and use catch branch to catch binding, remote, custom faults, business faults etc. If an error happens in a scope it will not move to the next scope( eg: you have 3 scope, error occured in 2nd scope then it will not propogate to the 3rd scope. One thing to be noticed here is your transaction in the 1st scope doesnt gets commited when an error happens in 2d scope).
You can have a catch all to catch error which are not being caught at catch level. So if any error happens which is not defined in catch block then then it will be caught in catch all branch.
Edited by: 333333 on Apr 12, 2011 9:39 AM

Oracle Error Handling in Shell Scripts

I need to manage 2 diferente class of errors :
Oracle Errors(produced in compilation time) and
Operating Syste Error(e.g. No Datbase conection ORA-1017,etc) my shell its KSH.
Please can you help me how can I manage then?
this my alternative but is not correct ;
#creating conexion with sql
exit | sqlplus -s $USERPV_DB/$PWDPV_DB @$VORDSQLPATH/ord.extractor_porven.sql $VFDESDE $VFHASTA > $VORDDATOS_PATH/ord.extractor_porven$VDATE.dat 2>> $VLOG
     #Evaluating last sentence (sqlplus . . . . )
     VERROR=$?
     #Si VERROR=0 should stop process execution and alert with echo ".."Oracle error handling before compilation time
     if [ $VERROR != 0 ]
     then
     echo "value of VERROR are:$VERROR"
     echo "`date +"$V_FORMATDATE"` DATA EXTRACTION WAS NOT SUCESSFUL ERROR BEFORE COMPILATION TIME" >> $VLOG 2> /dev/null
     " Here show VERROR
     else #Oracle error handling in compilation time
     echo "`date +"$V_FORMATDATE"` DATA EXTRACTION WAS NOT SUCESSFUL ERROR BEFORE COMPILATION TIME " >> $VLOG
     " Here show VERROR
else if [ $VERROR = 0 ]
" DATA EXTRACTION WAS SUCESSFUL"
fi
Would apreciate your help its very urgent.
Best Regards
Antonio

user5647282 wrote:
I need to manage 2 diferente class of errors :
Oracle Errors(produced in compilation time) and
Operating Syste Error(e.g. No Datbase conection ORA-1017,etc) my shell its KSH.
Please can you help me how can I manage then?
this my alternative but is not correct ;
#creating conexion with sql
exit | sqlplus -s $USERPV_DB/$PWDPV_DB @$VORDSQLPATH/ord.extractor_porven.sql $VFDESDE $VFHASTA > $VORDDATOS_PATH/ord.extractor_porven$VDATE.dat 2>> $VLOG
Piping the output of 'exit' to sqlplus????????? what do you expect from this?
     #Evaluating last sentence (sqlplus . . . . )
     VERROR=$?any error returned by sqlplus as $? would be a fatal error of sqlplus itself, not any error returned by processing a sql statement. If your script ord.extractor_porven.sql were to generate, say, an ORA-00001, that is NOT an error in sqlplus and so does not return to the OS as an error of sqlplus.
     #Si VERROR=0 should stop process execution and alert with echo ".."Oracle error handling before compilation time
     if [ $VERROR != 0 ]
     then
     echo "value of VERROR are:$VERROR"
     echo "`date +"$V_FORMATDATE"` DATA EXTRACTION WAS NOT SUCESSFUL ERROR BEFORE COMPILATION TIME" >> $VLOG 2> /dev/null
     " Here show VERROR
     else #Oracle error handling in compilation time
     echo "`date +"$V_FORMATDATE"` DATA EXTRACTION WAS NOT SUCESSFUL ERROR BEFORE COMPILATION TIME " >> $VLOG
     " Here show VERROR
else if [ $VERROR = 0 ]
" DATA EXTRACTION WAS SUCESSFUL"
fi
Would apreciate your help its very urgent.
there is no "urgent" here.
"Urgent" means one of two things -
1) people are dying, or
2) you have a customer-facing, revenue-producing production system that is down.
(And to get some perspective on the second case, keep the first in mind.)
For the first, you call whatever civil emergency service seems appropriate.
For the second, you open an SR with Oracle - which requires a paid-up support contract. For them to consider your problem "urgent", you will need to demonstrate that your problem falls under item #2. I seriously doubt your problem fits that criteria.
Best Regards
Antonio

ICM Scripting Error Handling Best Practice

Similar Messages

Maybe you are looking for