Application of the useCapture parameter

so with the help of David Stiller and LiveDocs, i am coming
to an understanding of how buttons work in as3. i've discovered the
useCapture parameter of addEventListener and while it makes sense,
i am afraid i am missing something because i can't see any use for
it. could someone give me an example how the ability to pass events
to the parent node of the target, both before and after they are
passed to the target, is useful? how can this new event flow be
applied?

Hi Sudir,
sorry for the delayed reply.
>
Sudhir Tiwari wrote:
> Hi arnab,
>
> SM58 comes into picture whenever there is any transaction takes place in XI system. the processing of any msg in XI in integratin engine involves its execution first and then it goes to inbound/outbound queues and is processed in the queue with FM's.
> This process executes within
> fractions of second that we can not see them in any of these transactions. SM58 contains LUWS which has three steps, transaction recorded,executing,executed.
>
> hope it helps.
>
> thanks
But i didnt get ur reply!
What do u mean by SM58 comes into picture whenever there is any transaction takes place in XI system, you mean to say, we dont need to check sm58 in R/3 with perspective to my idoc to xi to file and file to xi to idoc scenerio?
What exactly happens in this lUW, and how is it important in monitering?
What kind of error do SM59 reflect??
Pls explain EXPERTS!
Regards,
Arnab !

Similar Messages

Calling third party application that needs the HttpServletRequest parameter

Hi,
I am doing the customizations to the Webcenter portal(since the issue is specific to ADF, I am posting the thread in this group) wherein I need to invoke a Java API provided by third party. That Java API expects the HttpServletRequest parameter.
To obtain the HttpServletRequest , I used the below code: -
FacesContext context = FacesContext.getCurrentInstance();
HttpServletRequest request =
+(HttpServletRequest)context.getExternalContext().getRequest();+
Besides, I need to set some parameters to the request, as the API needs those parameters to connect to the 3rd party application. Hence I have set the attributes as below: -
request.setAttribute("HttpProxyHost", "https://thirdparty.com");
request.setAttribute("HttpProxyPort", "2021");
request.setAttribute("HttpProxyUser", "abcd");
request.setAttribute("HttpProxyPass", "efgh");
The call to the API works fine when tested standalone. But after deploying this to the application, I see the following issue.
The ADF application interacts with other 3rd party applications too. Once the above code is executed, the application is trying to connect to the above host(https://thirdparty.com) only for the subsequent requests from any user of that application, even if the actual call is meant to connect to different hosts.
Can I create a custom servlet class to invoke the Java API? If so, how can I call that servlet API from my ADF managed bean?
Even if I create a custom servlet, the parameters that I set like HttpProxyHost will persist, right?
Please provide any suggestions
Thanks,

Hi,
1) what is the problem you think makes this specific to ADF?
2) Have you tried : http://docs.oracle.com/javase/tutorial/networking/urls/connecting.html
Your requirement of changing a request that is in process sounds weird to be honest
Frank

Two commands in the report using the same parameter - fail under Java

I have a report that contains 2 SQL commands.
Both of these commands use one parameter X of type Number in their 'WHERE' clause.
When i'm viewing the report in CR 2008, i'm asked for a value of this parameter and all data is filled in the report - OK
The problem occurs when the same report is printed through Crystal Java Runtime:
Report is printed without data! - it's empty.
What we noticed in the debug information thrown by the Crystal libraries is that parameter value is set only in one of these commands:
Original statement 1:
select a.something
from ANM_T a
where a.anmid = {?PARAMETER01Id}
Original statement 2:
SELECT * from ANM_T a
WHERE a.anmid={?PARAMETER01Id}
OUTCOME of Statement 1:
select a.something
from ANM_T a
where a.anmid = 0
OUTCOME of Statement 2:
SELECT * from ANM_T a
WHERE a.anmid=9825
In above example we may see that crystal set the value only in the second statement - first one got 0 - i suspect its some default value.
Parameter in the Java code is set in the right way. In case of using only one statement it works. If we use two separate parameters (whose values are equal ) it also works.
// we have also the loop over the parameters
ParameterFieldController paramFieldController =
                report.getDataDefController().getParameterFieldController();
paramFieldController.setCurrentValue( "", paramName, paramValue );
What is strange for me is that Crystal Reports enables to use the same parameter in two commands but if you edit one of them you may change the type of this parameter for a command ( for example from Number to String) but the parameter type in the second command remains unchanged ( it's strange because in my opinion it is the same parameter). In the Field Explorer under the Parameter Fields i still see one parameter of type used in the second command.

Hello all,
We have prepared some sample code to illustrate the issue.
We have modified the sample application (Link: [http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/c07fec3e-3e11-2c10-1991-8c0fb0b82b75]) to that it also changes the parameter value. Parameter is used in two commands saved in report.
The code changing the parameters value looks like this:
private static void changeParameters(ReportClientDocument reportClientDoc) throws ReportSDKException {
          DataDefController dataDefController = reportClientDoc.getDataDefController();
        Fields fields = dataDefController.getDataDefinition().getParameterFields();
        for( int i = 0; i < fields.size(); i++ ){
            Field field = (Field)fields.getField( i );
            if( field.getKind() == FieldKind.parameterField ){
                        setParameter( ((ParameterField)field).getName(), "9825" , reportClientDoc);
private static void setParameter( String paramName, String paramValue, ReportClientDocument document ) throws ReportSDKException {
     ParameterFieldController paramFieldController =
                document.getDataDefController().getParameterFieldController();
     paramFieldController.setCurrentValue( "", paramName, paramValue );
We have tried the following codes to change the connection info used in commands:
Attempt 1
          Tables tables = databaseController.getDatabase().getTables();
          //Set the datasource for all main report tables.
          for (int i = 0; i < tables.size(); i++) {
               ITable table = tables.getTable(i);
               //Keep existing name and alias.
               table.setName(table.getName());
               table.setAlias(table.getAlias());
               //Change connection information properties.
               IConnectionInfo connectionInfo = table.getConnectionInfo();
               //Set new table connection property attributes.
               connectionInfo.setAttributes(propertyBag);
               //Set database username and password.
               //NOTE: Even if these the username and password properties don't change when switching databases, the
               //database password is *not* saved in the report and must be set at runtime if the database is secured.
               connectionInfo.setUserName(DBUSERNAME);
               connectionInfo.setPassword(DBPASSWORD);
               connectionInfo.setKind(ConnectionInfoKind.SQL);
               table.setConnectionInfo(connectionInfo);
               //Update old table in the report with the new table.
               databaseController.setTableLocation(table, tables.getTable(i));
               //databaseController.setTableLocation(tables.getTable(i), table);
Attempt 2
         newConnectionInfo.setAttributes(propertyBag);
         connectionInfo.setUserName(DBUSERNAME);
         connectionInfo.setPassword(DBPASSWORD);
         //preserve subreport links
         SubreportController src = doc.getSubreportController();
         Map<String, SubreportLinks> linkMapper = new HashMap<String,SubreportLinks>();
         for(String subreportName : src.getSubreportNames()){
             linkMapper.put(subreportName,
                 (SubreportLinks) src.getSubreportLinks(subreportName).clone(true));
         //If this connection needed parameters, we would use this field.
         Fields<IParameterField> pFields = doc.getDataDefController().getDataDefinition().getParameterFields();
         replaceConnectionInfos(doc.getDatabaseController(), newConnectionInfo, pFields);
         IStrings strs = src.getSubreportNames();
         Iterator<String> it = strs.iterator();
         while (it.hasNext()) {
           String name = it.next();
           ISubreportClientDocument subreport = src.getSubreport(name);
           pFields = subreport.getDataDefController().getDataDefinition().getParameterFields();
           replaceConnectionInfos(subreport.getDatabaseController(), newConnectionInfo, pFields);
         //reconnect subreport links since when using replaceConnection links are erased
         for(String subreportName : src.getSubreportNames())
           src.setSubreportLinks(subreportName, linkMapper.get(subreportName));
private static void replaceConnectionInfos(DatabaseController aDc, IConnectionInfo aNewConnInfo, Fields<IParameterField> aParameterField) throws ReportSDKException {
         ConnectionInfos cis = aDc.getConnectionInfos(null);
         for (IConnectionInfo oldConnInfo : cis)
           aDc.replaceConnection(oldConnInfo, aNewConnInfo, aParameterField, DBOptions._useDefault
               + DBOptions._doNotVerifyDB);
In both cases, the observed problem occurred. In one query the parameter was set properly, while on the other it was set to 0 (or empty string in case of string parameters). What is more, no data appeared on the print.
Do you happen to know the reason of this issue?How can we fix the problem?
Best regards
Mateusz Błaż

Need Help-How Store the input parameter through java bean

Hello Sir,
I have a simple Issue but It is not resolve by me i.e input parameter
are not store in Ms-Access.
I store the input parameter through Standard Action <jsp:useBean>.
jsp:useBean call a property IssueData. this property exist in
SimpleBean which create a connection from DB and insert the data.
At run time servlet and server also show that loggging are saved in DB.
But when I open the table in Access. Its empty.
Ms-Access have two fields- User, Password both are text type.
Please review these code:
login.html:
<html>
<head>
<title>A simple JSP application</title>
<head>
<body>
<form method="get" action="tmp" >
Name: <input type="text" name="user">
Password: <input type="password" name="pass">
<input type="Submit" value="Submit">
</form>
</body>
</html>LoginServlet.java:
import javax.servlet.*;
import javax.servlet.http.*;
public class LoginServlet extends HttpServlet{
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException{
try
String user=request.getParameter("user");
String pass=request.getParameter("pass");
co.SimpleBean st = new co.SimpleBean();
st.setUserName(user);
st.setPassword(pass);
request.setAttribute("user",st);
request.setAttribute("pass",st);
RequestDispatcher dispatcher1 =request.getRequestDispatcher("submit.jsp");
dispatcher1.forward(request,response);
catch(Exception e)
e.printStackTrace();
}SimpleBean.java:
package co;
import java.util.*;
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
import java.sql.*;
import java.util.*;
public class SimpleBean {
private String user="";
private String pass="";
private String s="";
public String getUserName() {
return user;
public void setUserName(String user) {
this.user = user;
public String getPassword() {
return pass;
public void setPassword(String pass) {
this.pass = pass;
public String getIssueData() //method that create connection with database
try
System.out.println("Printed*************************************************************");
getUserName();
getPassword();
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
System.out.println("Loading....");
Connection con=DriverManager.getConnection("jdbc:odbc:simple");
System.out.println("Connected....");
PreparedStatement st=con.prepareStatement("insert into Table1 values(?,?)");
System.out.println("~~~~~~~~~~~~~~~~~~~~");
String User=getUserName();
st.setString(1,User);
String Password=getPassword();
st.setString(2,Password);
st.executeUpdate();
System.out.println("Query Executed");
con.close();
s= "Your logging is saved in DB ";
System.out.println("Your logging is saved in DB *****************");
return(s);
catch(Exception e)
e.printStackTrace();
return "failed";
}submit.jsp:
This is Submit page
<html><body>
Hello
Student Name: <%= ((co.SimpleBean)request.getAttribute("user")).getUserName() %>
<br>
Password: <%= ((co.SimpleBean)request.getAttribute("pass")).getPassword() %>
<br>
<jsp:useBean id="st" class="co.SimpleBean" scope="request" />
<jsp:getProperty name="st" property="IssueData" />
</body></html>web.xml:<web-app>
<servlet>
<servlet-name>one</servlet-name>
<servlet-class>LoginServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>one</servlet-name>
<url-pattern>/tmp</url-pattern>
</servlet-mapping>
<jsp-file>issue.jsp</jsp-file>
<jsp-file>submit.jsp</jsp-file>
<url-pattern>*.do</url-pattern>
<welcome-file-list>
<welcome-file>Login.html</welcome-file>
</welcome-file-list>
</web-app>Please Help me..Thanks.!!!
--

Dear Sir,
Same issue is still persist. Input parameter are not store in database.
After follow your suggestion when I run this program browser show that:i.e
This is Submit page Hello Student Name: vijay
Password: kumar
<jsp:setProperty name="st" property="userName" value="userValue/> Your logging is saved in DB
Please review my code.
login.html:
{code}<html>
<head>
<title>A simple JSP application</title>
<head>
<body>
<form method="get" action="tmp" >
Name: <input type="text" name="user">
Password: <input type="password" name="pass">
<input type="Submit" value="Submit">
</form>
</body>
</html>{code}
LoginServlet.java:
{code}import javax.servlet.*;
import javax.servlet.http.*;
public class LoginServlet extends HttpServlet{
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException{
try
String userValue=request.getParameter("user");
String passValue=request.getParameter("pass");
co.SimpleBean st = new co.SimpleBean();
st.setuserName(userValue);
st.setpassword(passValue);
request.setAttribute("userValue",st);
request.setAttribute("passValue",st);
RequestDispatcher dispatcher1 =request.getRequestDispatcher("submit.jsp");
dispatcher1.forward(request,response);
catch(Exception e)
e.printStackTrace();
}{code}
SimpleBean.java:
{code}package co;
import java.util.*;
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
import java.sql.*;
import java.util.*;
public class SimpleBean {
private String userValue="";
private String passValue="";
private String s="";
public String getuserName() {
return userValue;
public void setuserName(String userValue) {
this.userValue = userValue;
public String getpassword() {
return passValue;
public void setpassword(String passValue) {
this.passValue= passValue ;
public String getissueData() //method that create connection with database
try
System.out.println("Printed*************************************************************");
getuserName();
getpassword();
Class.forName("oracle.jdbc.driver.OracleDriver");
System.out.println("Connection loaded");
Connection con=DriverManager.getConnection("jdbc:oracle:thin:@VijayKumar-PC:1521:XE","SYSTEM","SYSTEM");
System.out.println("Connection created");
PreparedStatement st=con.prepareStatement("insert into vij values(?,?)");
System.out.println("~~~~~~~~~~~~~~~~~~~~");
String userName=getuserName();
st.setString(1,userName);
String password=getpassword();
st.setString(2,password);
st.executeUpdate();
System.out.println("Query Executed");
con.close();
s= "Your logging is saved in DB ";
System.out.println("Your logging is saved in DB *****************");
return(s);
catch(Exception e)
e.printStackTrace();
return "failed";
}{code}
submit.jsp:
{code}This is Submit page
<html><body>
Hello
Student Name: <%= ((co.SimpleBean)request.getAttribute("userValue")).getuserName() %>
<br>
Password: <%= ((co.SimpleBean)request.getAttribute("passValue")).getpassword() %>
<br>
<jsp:useBean id="st" class="co.SimpleBean" scope="request" />
<jsp:setProperty name="st" property="userName" value="userValue/>
<jsp:setProperty name="st" property="password" value="passValue"/>
<jsp:getProperty name="st" property="issueData" />
</body></html>web.xml:<web-app>
<servlet>
<servlet-name>one</servlet-name>
<servlet-class>LoginServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>one</servlet-name>
<url-pattern>/tmp</url-pattern>
</servlet-mapping>
<jsp-file>submit.jsp</jsp-file>
<url-pattern>*.do</url-pattern>
<welcome-file-list>
<welcome-file>Login.html</welcome-file>
</welcome-file-list>
</web-app>Sir I can't use EL code in jsp because I use weblogic 8.1 Application Server.This version are not supported to EL.
Please help me...How store th input parameter in Database through Java Bean

Trying to Understand the PostSyncCleanup parameter

I've got a problem with running my application on the Australian version of Windows. We have a "test" application built around SQL Server Compact Merge Replication Library (thanks ErikEJ) and that works but our application doesn't.
One of the main differences with our application code is that we do not set the PostSyncCleanup value to anything and the library sets it to 2 per this link:
http blogs.msdn.com/b/sqlblog/archive/2009/04/15/sql-compact-performance-postsynccleanup-to-turn-off-updatestatistics-during-initial-download-of-sql-compact-replication.aspx (put the :// back to get the link)
I'm trying to understand the impact of making that our "production" configuration since we haven't been using it. The description looks harmless enough but I don't really understand what statistics I'm turning off and what the impact
would be and what even the default setting is. Anything that could enlighten me would be appreciated along with a guess as to why that might be causing a problem on the Australian version of Windows would be appreciated.

So we've been running with the default value (0) and have not really had any "problems". I haven't done any testing but I'm ok with faster, like everyone would be, but am also a bit risk averse so want to know what exactly I'm turning off.
I also saw this advice from Rob Tiffany:
Use the appropriate x64, x86 or ARM version of SQL Server Compact 3.5 SP2 to take advantage of the
PostSyncCleanup property of the SqlCeReplication object that can reduce the time it takes to perform an initial synchronization. Set the
PostSyncCleanup property equal to 3 where neither
UpdateStats nor CleanByRetention are performed.
Here: http robtiffany.com/microsoft-sql-server-compact-3-5-sp2-has-arrived/
So, is the best advice to use that parameter and set the value to 3 or 2
I don't really know what I'm losing to "not performing" UpdateStats or CleanByRetention and does making that change need I need to do something else on the server or client to "clear out" or "clean up" something that this is
doing.

How to get the source code of a PRT application in the portal

Hi!
Does anybody know how to get the source code of a PRT application in the portal?
Thanks in advance,
Celso

Celso,
If its Java-based code have a look at the properties of an iView that belongs to the application in question and copy the value of the Code Link parameter e.g. 'com.sap.pct.hcm.rc_vacancyrequestov.default'.
Search the Portal installation directory under /j233/cluster/server/ for a .par.bak file of the same name, removing .default from the codelink parameter
e.g. com.sap.pct.hcm.rc_vacancyrequestov.par.bak
Copt this locally and import into Netweaver Developer Studio. You will have to decompilte the class files with a decompiler such as DJ Decompiler or Cavaj (search with Google).
Cheers,
Steve

How Insert the input parameter to database through Java Bean

Hello To All..
I want to store the input parameter through Standard Action <jsp:useBean>.
jsp:useBean call a property IssueData. this property exist in
SimpleBean which create a connection from DB and insert the data.
At run time when I click on submit button servlet and server also show that loggging are saved in DB.
But when I open the table in Access. Its empty.
Ms-Access have two fields- User, Pass both are text type.
Please review these code:
login.html:
<html>
<head>
<title>A simple JSP application</title>
<script language=javascript>
function f(k)
document.forms['frm'].mykey.value=k;
document.forms['frm'].submit();
</script>
<head>
<body>
<form method="get" action="tmp" name="frm">
Name: <input type="text" name="User">
Password: <input type="password" name="Pass">
<input type=hidden name="mykey" value="">
<input type="button" value="Submit" onclick="f('submit.jsp')">
<input type="button" value="Issue" onclick="f('issue.jsp')">
</form>
</body>
</html>LoginServlet.java:import javax.servlet.*;
import javax.servlet.http.*;
public class LoginServlet extends HttpServlet{
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException{
try
String User=request.getParameter("User");
String Pass=request.getParameter("Pass");
co.SimpleBean st = new co.SimpleBean();
st.setUser(User);
st.setPass(Pass);
request.setAttribute("User",st);
request.setAttribute("Pass",st);
RequestDispatcher dispatcher1 =request.getRequestDispatcher("/"+request.getParameter("mykey"));
dispatcher1.forward(request,response);
catch(Exception e)
e.printStackTrace();
}SimpleBean.java:package co;
import java.util.*;
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
import java.sql.*;
import java.util.*;
public class SimpleBean
private String User="";
private String Pass="";
private String s="";
public SimpleBean(){}
public String getUser() {
return User;
public void setUser(String User) {
this.User = User;
public String getPass() {
return Pass;
public void setPass(String Pass) {
this.Pass = Pass;
public String getissueData() //method that create connection with database
try
System.out.println("Printed*************************************************************");
getUser();
getPass();
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
System.out.println("Loading....");
Connection con=DriverManager.getConnection("jdbc:odbc:simple");
System.out.println("Connected....");
PreparedStatement st=con.prepareStatement("insert into Table1 values(?,?)");
System.out.println("~~~~~~~~~~~~~~~~~~~~");
String User=getUser();
st.setString(1,User);
String Pass=getPass();
st.setString(2,Pass);
int y= st.executeUpdate();
System.out.println(y);
System.out.println("Query Executed");
con.commit();
con.close();
s= "Your logging is saved in DB ";
System.out.println("Your logging is saved in DB *****************");
return this.s;
catch(Exception e)
e.printStackTrace();
return "failed";
}submit.jsp:
This is Submit page
<html><body>
Hello
Student Name: <%= ((co.SimpleBean)request.getAttribute("User")).getUser() %>
<br>
Password: <%= ((co.SimpleBean)request.getAttribute("Pass")).getPass() %>
<br>
<jsp:useBean id="st" class="co.SimpleBean" scope="request"/>
<jsp:setProperty name="st" property="User" value="request.getParamaeter("Pass")"/>
<jsp:setProperty name="st" property="Pass" value="request.getParamaeter("Pass")"/>
<jsp:getProperty name="st" property="issueData"/>
<% st.getissueData(); %>
</body></html>web.xml:<web-app>
<servlet>
<servlet-name>one</servlet-name>
<servlet-class>LoginServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>one</servlet-name>
<url-pattern>/tmp</url-pattern>
</servlet-mapping>
<jsp-file>issue.jsp</jsp-file>
<jsp-file>submit.jsp</jsp-file>
<url-pattern>*.do</url-pattern>
<welcome-file-list>
<welcome-file>Login.html</welcome-file>
</welcome-file-list>
</web-app>Please Help me..

Dear Sir,
Accordingly your suggestion I check the SimpleBean class putting the constant values in this bean class.That is Sucessfully Inserted constant values in database.
Like for example..
myfirstjavabean.java:
package myfirstjava;
import java.io.*;
import java.sql.*;
public class myfirstjavabean
private String firstMsg="Hello world";
private String s="";
public myfirstjavabean()
public String getfirstMsg()
return firstMsg;
public void setfirstMsg(String firstMsg)
this.firstMsg=firstMsg;
public String getissueData() //method that create connection with database
try
System.out.println("Printed*************************************************************");
getfirstMsg();
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
System.out.println("Loading....");
Connection con=DriverManager.getConnection("jdbc:odbc:sampleMsg");
System.out.println("Connected....");
PreparedStatement st=con.prepareStatement("insert into Table1 values(?)");
System.out.println("~~~~~~~~~~~~~~~~~~~~");
String Msg=getfirstMsg();
st.setString(1,Msg);
int y= st.executeUpdate();
System.out.println(y);
System.out.println("Query Executed");
con.commit();
con.close();
s= "Your logging is saved in DB ";
System.out.println("Your logging is saved in DB *****************");
return this.s;
catch(Exception e)
e.printStackTrace();
return "failed";
}Vij.jsp:
<html>
<body>
<jsp:useBean id="st" class="myfirstjava.myfirstjavabean" scope="request" />
<jsp:getProperty name="st" property="firstMsg" />
<jsp:getProperty name="st" property="issueData" />
</body>
</html>These above example sucessfully inserted the Hello World message in database.
But which value I put user input at run time Its not inserted in database.
Which is my previous problem that is persist.
Please Help..

How to get the URL parameter value when navigating from JSP Page to portal

Hi All,
I have web Dynpro application with one button, while clicking that button It will navigate to JSP page as external window. In the JSP page I have a input field and Button.
In the JSP page input field I will enter some values and press submit button, it will navigate to Portal page by passing some URL parameter with values.
Once user entering to portal by default WD page displayed, the same WD page I try to get the URL Parameter which I have passed from JSP page, but I am not able to get the URL parameter value.
If same application running in without portal, I can able to get the URL parameter values. I am getting the URL parameter by interface view default inbound plug parameter.
How do we resolve this problem?
Regards,
Boopathi M

Hi
Please try these link might helpful for you
1.[How to call WebDynPro application from JSP |/thread/452762 [original link is broken];
2.[How to get the previous page url from abstract portal component? |/thread/1289256 [original link is broken];
3.[how to launch and pass a parameter |/thread/5537 [original link is broken];
Best Regards
Satish Kumar

Save the export parameter as an excel or notepad file in ecatt

Hello,
Que: I want to save the export parameter value to an excel or a notepad file in my ecatt script?
Importing of notepad file can be handled as an external file variant input from test data container.
But I am not able to export the value to a file.
Kindly help.

Well, dont know if that is like VB-Script
but you could give it a try ...
set xclapp = createObject("Excel.Application")
set xclwbk = xclapp.Workbook.New
set xclsht = xclwbk.Sheets("Tabelle1")
xclsht.Cells(1,1).Value = [your Parameters go here!]
set xclsht = Nothing
xclwbk.close
set xclwbk = nothing
xclapp.quit
set xclapp = Nothing

KIMYONG : Applications Database Connection Pool 관련 parameter 설명

Purpose
JVM 이 과도한 CPU / Memory를 사용하게 되어 Application Performance에 영향을 미칠때가 있으며 이럴경우 Connection Pool 관련하여 Parameter Tunning을 해야 할때가 있습니다. 이때 사용되는 Parameter들의 의미를 설명하고자 합니다.
The Applications Database Connection Pool is a pool of JDBC database connections that are shared among java applications. Applications obtain connections from the pool by using the getJDBCConnection(...) methods of AppsContext.
Essentially, each AppsContext has a single database connection associated with it at all times.
The AOL/J layer internally borrows and returns this connection to the pool as needed to maintain connection reference that is properly initialized for the current Java tier AOL security context and NLS state.
FND_MAX_JDBC_CONNECTIONS
============================
The maximum pool size is the maximum allowed sum of the number of available connections and thenumber of locked connections. If the pool reaches the maximum size and all connections are locked, new clients will not be able to borrow a connection until one of the current clients has returned one. The default setting for this parameter is essentially unlimited (about 2 billion).
FND_JDBC_BUFFER_MIN
======================
The buffer minimum is the minimum number of connections that the pool should try to maintain in the available list. When the buffer size falls below the buffer minimum, the pool maintenance thread will be notified to create new connections. When notified, the thread will immediately attempt to create the number of connections to fill the difference. New connections will not be created if the pool is already at its maximum size. When creating new connections the thread uses the attributes of the most recent client request that resulted in a new connection being created.
Setting this parameter to "0" will disable maintenance of the buffer minimum.
However, the buffer maximum will still be maintained.
Setting this parameter to a number greater than the maximum pool size(FND_MAX_JDBC_CONNECTIONS) will disable all buffer maintenance.
FND_JDBC_BUFFER_MAX
======================
The buffer maximum is the maximum number of connections that the pool should try to maintain in the available list. During heavy usage, the buffer may exceed this maximum. However, during periods of low usage, the maintenance thread will decrease the buffer size until the buffer maximum is reached.
If the value of this parameter is an integer, (for example "20") the buffer maximum is static. If the value is a percent (for example, "20%"), the buffer maximum is not constant but instead is calculated dynamically as a percent of total pool size. The buffer minimum is also taken into account when
determining a dynamic buffer maximum.
The exact expression used is:
maximum(t) = buffer minimum + ( (FND_JDBC_BUFFER_MAX/100) * size(t) )
where maximum(t) and size(t) are the buffer maximum and pool size at some time t.
The thread is configured to periodically check the buffer size. If the buffer size is greater than the maximum, the thread will remove either the number of available connections specified by FND_JDBC_BUFFER_DECAY_SIZE or the number of connections in excess of the buffer minimum, whichever is smaller. When connections are removed from the available list, the least recently used ones are removed first.
Setting this parameter to100%, or to a number equal to FND_MAXIMUM_JDBC_CONNECTIONS, or to a number less than or equal to FND_JDBC_BUFFER_MIN will effectively prevent the maintenance thread from ever removing any connections.
FND_JDBC_BUFFER_DECAY_INTERVAL
===================================
The buffer decay interval specifies how often the connection pool maintenance thread should check the buffer size. The thread will check the buffer size at most once every FND_JDBC_BUFFER_DECAY_INTERVAL seconds. The actual time between consecutive thread cycles will vary somewhat depending on the JVM load.
This parameter, along with FND_JDBC_BUFFER_DECAY_SIZE, allows the buffer decay rate to be tuned. For example, if the buffer decay size is 2 and the buffer decay interval is one minute, the buffer decay rate will never exceed two connections per minute. When connections are removed, the least recently used ones are removed first.
FND_JDBC_BUFFER_DECAY_SIZE
=============================
The buffer decay size specifies the maximum number of connections that should be removed during any single thread cycle during which the number of available connections is greater than the buffer size. This parameter, along with FND_JDBC_BUFFER_DECAY_INTERVAL, allows the buffer decay rate to be tuned.
FND_JDBC_MAX_WAIT_TIME
=========================
The maximum wait time specifies how much time a client should spend trying to get a connection. The borrow algorithm, used to borrow an object from the pool, contains check points at which the elapsed time is compared to the maximum wait time. If it exceeds the maximum wait time, then a null object will be returned to the client. The pre-configured value for the maximum wait time is
10 seconds.
FND_JDBC_SELECTION_POLICY
============================
The selection policy determines how a connection is selected from the list of available connections for a particular client. The connection pool is pre-configured to use a cost-based selection algorithm, which selects the connection that will require the smallest amount of initialization to match the
client's context.
FND_JDBC_USABLE_CHECK
===========================
The FND_JDBC_USABLE_CHECK parameter governs whether a pl/sql query is performed before giving a connection to a client. The pool checks whether a connection is usable before handing it to a client. This always involves checking that the connection is not null and is not closed. If FND_JDBC_USABLE_CHECK is set to true, then it also verifies that the connection can be used to perform a simple PL/SQL query. (This parameter may have to be set to "true" in order to clean up
connections to a database that has been restarted.)
FND_JDBC_CONTEXT_CHECK
==========================
The FND_JDBC_CONTEXT_CHECK parameter governs whether the AOL security context and NLS state is obtained from the database when the connection is returned to the pool. If FND_JDBC_CONTEXT_CHECK is "true", when the connection is returned to the pool, the AOL security context and NLS state will be obtained from the database. (This is implemented in the DBConnObj.isReusable() method). This check must be done when the connection is returned (rather than when it is borrowed) so that the selection matching algorithm has access to the actual
session context of the connections in the available list.
FND_JDBC_PLSQL_RESET
========================
The PL/SQL reset flag, set using the variable FND_JDBC_PLSQL_RESET, governs whether the PL/SQL state associated with a connection should be freed before the pool hands the connection to the client. By default this flag is false.
If the flag is set by true, by including the line "FND_JDBC_PLSQL_RESET=true" in the .dbc file, each connection to the database will have its PL/SQL state cleared before the pool returns the connection to the client.
This is how it works. After the pool selects a connection from the available list for a client, it initializes the connection. One of the things initialization does is to set a flag that is later used by SessionManager to determine if the apps initialization routine needs to be performed for the connection. When FND_JDBC_PLSQL_RESET has been set to "true", this flag will always be set to true. After the pool initializes the connection, it also checks whether the connection is usable. In this case, this check will include a call to DBMS_SESSION.RESET_PACKAGE, which frees the PL/SQL state. The table below summaries the affect of FND_JDBC_PLSQL_RESET and the other safety check parameters on borrowing a connection from the pool.
The FND_JDBC_PLSQL_RESET parameter has been added to only to address the case where production PL/SQL global bugs are known to exist. The performance of the pool is reduced by setting this flag to true.
Reference : Note 264599.1

Purpose
JVM 이 과도한 CPU / Memory를 사용하게 되어 Application Performance에 영향을 미칠때가 있으며 이럴경우 Connection Pool 관련하여 Parameter Tunning을 해야 할때가 있습니다. 이때 사용되는 Parameter들의 의미를 설명하고자 합니다.
The Applications Database Connection Pool is a pool of JDBC database connections that are shared among java applications. Applications obtain connections from the pool by using the getJDBCConnection(...) methods of AppsContext.
Essentially, each AppsContext has a single database connection associated with it at all times.
The AOL/J layer internally borrows and returns this connection to the pool as needed to maintain connection reference that is properly initialized for the current Java tier AOL security context and NLS state.
FND_MAX_JDBC_CONNECTIONS
============================
The maximum pool size is the maximum allowed sum of the number of available connections and thenumber of locked connections. If the pool reaches the maximum size and all connections are locked, new clients will not be able to borrow a connection until one of the current clients has returned one. The default setting for this parameter is essentially unlimited (about 2 billion).
FND_JDBC_BUFFER_MIN
======================
The buffer minimum is the minimum number of connections that the pool should try to maintain in the available list. When the buffer size falls below the buffer minimum, the pool maintenance thread will be notified to create new connections. When notified, the thread will immediately attempt to create the number of connections to fill the difference. New connections will not be created if the pool is already at its maximum size. When creating new connections the thread uses the attributes of the most recent client request that resulted in a new connection being created.
Setting this parameter to "0" will disable maintenance of the buffer minimum.
However, the buffer maximum will still be maintained.
Setting this parameter to a number greater than the maximum pool size(FND_MAX_JDBC_CONNECTIONS) will disable all buffer maintenance.
FND_JDBC_BUFFER_MAX
======================
The buffer maximum is the maximum number of connections that the pool should try to maintain in the available list. During heavy usage, the buffer may exceed this maximum. However, during periods of low usage, the maintenance thread will decrease the buffer size until the buffer maximum is reached.
If the value of this parameter is an integer, (for example "20") the buffer maximum is static. If the value is a percent (for example, "20%"), the buffer maximum is not constant but instead is calculated dynamically as a percent of total pool size. The buffer minimum is also taken into account when
determining a dynamic buffer maximum.
The exact expression used is:
maximum(t) = buffer minimum + ( (FND_JDBC_BUFFER_MAX/100) * size(t) )
where maximum(t) and size(t) are the buffer maximum and pool size at some time t.
The thread is configured to periodically check the buffer size. If the buffer size is greater than the maximum, the thread will remove either the number of available connections specified by FND_JDBC_BUFFER_DECAY_SIZE or the number of connections in excess of the buffer minimum, whichever is smaller. When connections are removed from the available list, the least recently used ones are removed first.
Setting this parameter to100%, or to a number equal to FND_MAXIMUM_JDBC_CONNECTIONS, or to a number less than or equal to FND_JDBC_BUFFER_MIN will effectively prevent the maintenance thread from ever removing any connections.
FND_JDBC_BUFFER_DECAY_INTERVAL
===================================
The buffer decay interval specifies how often the connection pool maintenance thread should check the buffer size. The thread will check the buffer size at most once every FND_JDBC_BUFFER_DECAY_INTERVAL seconds. The actual time between consecutive thread cycles will vary somewhat depending on the JVM load.
This parameter, along with FND_JDBC_BUFFER_DECAY_SIZE, allows the buffer decay rate to be tuned. For example, if the buffer decay size is 2 and the buffer decay interval is one minute, the buffer decay rate will never exceed two connections per minute. When connections are removed, the least recently used ones are removed first.
FND_JDBC_BUFFER_DECAY_SIZE
=============================
The buffer decay size specifies the maximum number of connections that should be removed during any single thread cycle during which the number of available connections is greater than the buffer size. This parameter, along with FND_JDBC_BUFFER_DECAY_INTERVAL, allows the buffer decay rate to be tuned.
FND_JDBC_MAX_WAIT_TIME
=========================
The maximum wait time specifies how much time a client should spend trying to get a connection. The borrow algorithm, used to borrow an object from the pool, contains check points at which the elapsed time is compared to the maximum wait time. If it exceeds the maximum wait time, then a null object will be returned to the client. The pre-configured value for the maximum wait time is
10 seconds.
FND_JDBC_SELECTION_POLICY
============================
The selection policy determines how a connection is selected from the list of available connections for a particular client. The connection pool is pre-configured to use a cost-based selection algorithm, which selects the connection that will require the smallest amount of initialization to match the
client's context.
FND_JDBC_USABLE_CHECK
===========================
The FND_JDBC_USABLE_CHECK parameter governs whether a pl/sql query is performed before giving a connection to a client. The pool checks whether a connection is usable before handing it to a client. This always involves checking that the connection is not null and is not closed. If FND_JDBC_USABLE_CHECK is set to true, then it also verifies that the connection can be used to perform a simple PL/SQL query. (This parameter may have to be set to "true" in order to clean up
connections to a database that has been restarted.)
FND_JDBC_CONTEXT_CHECK
==========================
The FND_JDBC_CONTEXT_CHECK parameter governs whether the AOL security context and NLS state is obtained from the database when the connection is returned to the pool. If FND_JDBC_CONTEXT_CHECK is "true", when the connection is returned to the pool, the AOL security context and NLS state will be obtained from the database. (This is implemented in the DBConnObj.isReusable() method). This check must be done when the connection is returned (rather than when it is borrowed) so that the selection matching algorithm has access to the actual
session context of the connections in the available list.
FND_JDBC_PLSQL_RESET
========================
The PL/SQL reset flag, set using the variable FND_JDBC_PLSQL_RESET, governs whether the PL/SQL state associated with a connection should be freed before the pool hands the connection to the client. By default this flag is false.
If the flag is set by true, by including the line "FND_JDBC_PLSQL_RESET=true" in the .dbc file, each connection to the database will have its PL/SQL state cleared before the pool returns the connection to the client.
This is how it works. After the pool selects a connection from the available list for a client, it initializes the connection. One of the things initialization does is to set a flag that is later used by SessionManager to determine if the apps initialization routine needs to be performed for the connection. When FND_JDBC_PLSQL_RESET has been set to "true", this flag will always be set to true. After the pool initializes the connection, it also checks whether the connection is usable. In this case, this check will include a call to DBMS_SESSION.RESET_PACKAGE, which frees the PL/SQL state. The table below summaries the affect of FND_JDBC_PLSQL_RESET and the other safety check parameters on borrowing a connection from the pool.
The FND_JDBC_PLSQL_RESET parameter has been added to only to address the case where production PL/SQL global bugs are known to exist. The performance of the pool is reduced by setting this flag to true.
Reference : Note 264599.1

How do i change the enable_row_shipping parameter in oracle11g?

Here is my Oracle version..
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning and Real Application Testing options
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
PL/SQL Release 11.1.0.7.0 - Production
CORE 11.1.0.7.0 Production
TNS for Linux: Version 11.1.0.7.0 - Production
NLSRTL Version 11.1.0.7.0 - Production
SQL>
I do want to change the below parameter value from TRUE to FASE. How do i change this value? since this is hidden parameter.
enablerow_shipping
Regards

alter system set "_enable_row_shipping"=false;maybe with scope=spfile, test it.
why you would set it?

[svn] 4804: Bugs: LCDS-548: add code to deal with contentType="application/ xml" with one parameter (avoid

Revision: 4804
Author: [email protected]
Date: 2009-02-02 17:56:22 -0800 (Mon, 02 Feb 2009)
Log Message:
Bugs: LCDS-548: add code to deal with contentType="application/xml" with one parameter (avoid
name/value encoding in that case)
LCDS-405: baseURL on HTTPMultiService should accept URLs which start with "/"
Added convertParametersHandler and convertResultsHandler function hooks to RemoteObject
to support framework code which wants to modify the service behavior.
Moved "properties" from rpc/http/AbstractOperation to rpc/AbstractOperation so we can use
it for customizing the handling of remote object results
Couple of minor ASDoc fixes and one tab -> spaces change
Doc: minor asdoc edits
QE: LCDS QE will verify the bugs in this one
Reviewers: Mete, Pete, Seth, Ed reviewed different parts of this checkin
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-548
http://bugs.adobe.com/jira/browse/LCDS-405
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/AbstractInvoker.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/AbstractOperation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/AbstractOperation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/HTTPMultiService.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/Operation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/remoting/Operation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/remoting/RemoteObject.as

Hello,
How about this as an alternative:
Use a functional global which has 3 cases:
1. open config file - it opens the config file and reads the contents into a string (which is the functional global data), and you only do this one time at the beginning of the program.
2. edit config data - it edits the string, which are really the contents of the file, but doesn't worry about writing to the file. you could even get fancy here, and allow an array of tags and an array of values as input, and it would go update/edit all the tags to have the corresponding values.
3. close config file - it writes the current string data (the functional global data) to the file and closes it.
Using the functions in the string palette, I think you'll find most of the code for that module/functional global will be easy to write.
I hope this helps!
Best Regards,
JLS
Best,
JLS
Sixclear

Multiple Values in the Return Parameter

Hi,
My application has a decision table , with material group, division fields and has agent as the return parameter.
I need to maintain more than 1 user for each material group/division combination?
I even tried using return parameter 'agent' as structure and table too.
Can I maintain multiple entries. I don't want to maintain multiple rows for multiple agents.
Is this feasible? If yes, how can I do it?
Regards,
Hiranmayi
Edited by: Hiranmayi Praturi on Dec 8, 2010 7:32 AM

Thank you Carsten . I did as you suggested. But in the 2nd decision table (result decision table) , it gives me an error saying it has no condition columns.
Does this have anything to do with the SP , we have SAP_BASIS 701 .
PS: Your blogs and pdfs have been great help to learn BRFPlus. Thank you.

Exception: "The type "Collection" as used in the variable/parameter declarations

I am getting the following exception when I try to run the test code.
What could be causing it ?
I am running Kodo 2.4.3 with JDK 1.4.1
EXCEPTION
javax.jdo.JDOFatalInternalException: [agencyNames:[AGENCY1, AGENCY2]]
NestedThrowables:
javax.jdo.JDOUserException: The type "Collection" as used in the
variable/parameter declarations could not be found in the imports.
TEST CODE
JDOFactory jdoFactory = new JDOFactory();
PersistenceManager pm = jdoFactory.getPersistenceManager("");
try
Class agencyClass = Agency.class;
Extent agencyExtent = pm.getExtent(agencyClass, false);
String filter = "agencyNames.contains(agencyName)";
List agencyNames = Arrays.asList(new String[]{"AGENCY1",
"AGENCY2"});
String param = "Collection agencyNames";
Query q = pm.newQuery(agencyExtent, filter);
q.declareParameters(param);
Collection deps = (Collection) q.execute(agencyNames);
System.out.println("SIZE :" + deps.size());
catch (Exception ex)
ex.printStackTrace();
JDO Mapping and Class
package test;
import java.util.*;
public class Agency
private String agencyName;
private String hostCarrierCode;
//Getter and Setter
public static class Id
public String agencyName;
public String hostCarrierCode;
//Application ID definition
?xml version="1.0"?>
<jdo>
<package name="test">
<class name="Agency" identity-type="application"
objectid-class="Agency$Id">
<extension vendor-name="kodo" key="table" value="AGENCIES"/>
<extension vendor-name="kodo" key="lock-column" value="none"/>
<extension vendor-name="kodo" key="class-column" value="none"/>
<field name="agencyName" primary-key="true">
<extension vendor-name="kodo" key="data-column"
value="AGENCY_NAME"/>
</field>
<field name="hostCarrierCode" primary-key="true" >
<extension vendor-name="kodo" key="data-column"
value="CARRIER_CODE"/>
</field>
</class>
</package>
</jdo>

Kodo 2.4.3 does not support using collections as parameters.
Kodo 2.5.0, due to be released shortly, does support this. See
http://solarmetric.com/Software/beta/2.5.0 to get the latest release
candidate.
-Patrick
On Thu, 05 Jun 2003 22:26:36 +0000, B K Adarsh wrote:
I am getting the following exception when I try to run the test code.
What could be causing it ?
I am running Kodo 2.4.3 with JDK 1.4.1
EXCEPTION
javax.jdo.JDOFatalInternalException: [agencyNames:[AGENCY1, AGENCY2]]
NestedThrowables:
javax.jdo.JDOUserException: The type "Collection" as used in the
variable/parameter declarations could not be found in the imports.
TEST CODE
JDOFactory jdoFactory = new JDOFactory();
PersistenceManager pm = jdoFactory.getPersistenceManager("");
try
Class agencyClass = Agency.class;
Extent agencyExtent = pm.getExtent(agencyClass, false);
String filter = "agencyNames.contains(agencyName)";
List agencyNames = Arrays.asList(new String[]{"AGENCY1",
"AGENCY2"});
String param = "Collection agencyNames";
Query q = pm.newQuery(agencyExtent, filter);
q.declareParameters(param);
Collection deps = (Collection) q.execute(agencyNames);
System.out.println("SIZE :" + deps.size());
catch (Exception ex)
ex.printStackTrace();
JDO Mapping and Class
package test;
import java.util.*;
public class Agency
private String agencyName;
private String hostCarrierCode;
//Getter and Setter
public static class Id
public String agencyName;
public String hostCarrierCode;
//Application ID definition
?xml version="1.0"?>
<jdo>
<package name="test">
<class name="Agency" identity-type="application"
objectid-class="Agency$Id">
<extension vendor-name="kodo" key="table" value="AGENCIES"/>
<extension vendor-name="kodo" key="lock-column" value="none"/>
<extension vendor-name="kodo" key="class-column" value="none"/>
<field name="agencyName" primary-key="true">
<extension vendor-name="kodo" key="data-column"
value="AGENCY_NAME"/>
</field>
<field name="hostCarrierCode" primary-key="true" >
<extension vendor-name="kodo" key="data-column"
value="CARRIER_CODE"/>
</field>
</class>
</package>
</jdo>--
Patrick Linskey
SolarMetric Inc.

How to invoke a java application in the middle of the process

In the middle of one process, I want to invoke a java application. After the java application, the process will continue and select a path based on the result of the java application. Which activity can be used to invoke a java application in the middle of the process?
Thanks

BPM Changes:
1. Under 'External Resources' create a new resource of type 'Server Configuration'. Specify the host port and path of your servlet here. This will be invoked from your process. Lets name this configuration as 'myExternalConf'.
2. Create an interactive activity say 'InvokeMyApplication' in your process. The main task of this application should be external task. (Implementation Type = External)
3. Create the prepareMethod method say 'prepareExternal'. Set the arguments for this method as output arguments. These arguments will be available to you in your external servlet.
4. Create the commit method say 'commitExternal'. Set the arguments as input arguments. The external servlet will return these arguments back to the process.
5. Check the 'Use configuration' checkbox for your main task (external task). Select 'myExternalConf' here.
Servlet changes:
When the user executes your 'InvokeMyApplication' activity, he will be taken to the external servlet of your external application. You will be passed the currentActivity, currentParticipant, instanceID and one more argument (which I dont remember :( ) as url parameters.
1. In this servlet, open a PAPI/PAPI WS session for the participant passed to the servlet as url parameter
2. Use the currentActivity ( passed in url parameter), to call prepare method on this activity. This will return you with the arguments defined in 'prepareExternal' method.
3. Using these argumets, or otherwise, you can do whatever you want in this servlet. When done prepare the arguments to pass back to BPM.
4. call papiService.activityCommit and return the arguments.
5. Flow goes back to your BPM application
Some code that might help:
Servlet calling prerpare:
ProcessServiceSession papisession = null;
try{
papisession = initializePapi();
fuego.papi.Arguments args = fuego.papi.Arguments.create();
args = papisession.activityPrepare(activity, instanceId, args);
Map<String, Object> argsMap = args.getArguments();
return argsMap;
protected ProcessServiceSession initializePapi(){
Properties configuration = new Properties();
try {
InputStream inputStream = getClass().getClassLoader().getResourceAsStream("bpm.properties");
if(inputStream == null)
throw new IOException();
configuration.load(inputStream);
} catch (IOException ex) {
log.log(Level.WARNING, "Could not load bpm.properties", ex);
return null;
Servlet calling commit:
public void commitToALBPM(Map parameters){
try{
papisession = initializePapi();
fuego.papi.Arguments args = fuego.papi.Arguments.create();
Set s = parameters.keySet();
Iterator propNames = s.iterator();
while (propNames.hasNext()){
String key = (String)propNames.next();
String val = (String)parameters.get(key);
args.putArgument(key, val);
papisession.activityCommit(activity, instanceId, args);
catch (OperationException e)
HTH
Satinder

Application of the useCapture parameter

Similar Messages

Maybe you are looking for