ALE connection for E-reruitment to ECC

Hi Experts,
Need help with the steps to configure ALE for sending data from E-Recruitment to ECC 6.0. Or send me the relevant doc to oscar.miak at g mail
Thanks.
Oscar

Please post it here. It will help many others.
Thanks.

Similar Messages

Connecting Enterprise Portal with SAP ECC 6.0 for ESS/MSS

Hi,
I am trying to connect my Portal with the ECC backend but getting the error "SAP_R3_SelfServiceGenerics_MetaData". However when I tried to set the configuration in the JCo destination, I am not able to locate the message server for my ECC instance in the configuration page.
Any idea on this?

Hi,
Do the following steps.
1. Login to your SLD URL
http://hostname of sld:5<NN>00/sld
give the input as administrator username and password.
Once you are IN.
click on administrator TAB
Click on Profile TAB
In section TAB select DATASUPPLIER
Fil the detail in GATEWAY HOST and GATEWAY SERVICE ( SAPGW<NN>)
Gateway information should be on newly install gateway instance.
Then click on save.
Again click on Administrator TAB and click on STOP SERVER and then click on START SERVER.
Once above actvity done on SLD syste,.
Then go back to your ABAP stack in RZ70 and mainain the neccesary detatils and start the job, it should work now.
Thanks
Anil

Message server for ALE connection

Hi Gurus,
i have a query on ALE. Can message server be used for ALE connection?
what needs to be do to enable it for ALE?
how can we configure all the interfaces on message server?
please provide me the inputs.
thanks in advance.

hi vergese
i appolozise for the previous post ,
for the Ale connection you may Refer the below thread link as refernce
ALE connection between HR and R/3 system
regards
Saurabh Goel

Connection between webdynpro java and ECC.

Hi experts,
I am very new to webdynpro java, I want to learn webdynpro java since I know little bit of java.
So here is my question,
I want to connect my webdynpro java to ECC to get data from ECC and display it on front end and as well i want to send data to ECC, can anyone help me to resolve this one.
Thanks and Regards,
Santoshkumar.

Hi Santosh,
This is pretty basic stuff in the world of Web Dynpro Java - I'd suggest you search SCN, read content on help.sap.com and then come back here with more specific questions. All anyone can do to answer your current question is search for you and post links to documents that you could find for yourself.
Cheers,
G.

IDOC type for interface between SAP ECC and SAP F&R

Hi Experts,
I need SAP standatd IDOC type for interfacing between SAP ECC and SAP F&R [SAP Forecasting and Replenishment] using message type u201CFRE_LOC_SITEu201D.
Please help me in finding the idoc type?
Regards,
Krishan

Hi Denish,
You have 2 ways of loading data from R/3 to APO.
1. R/3 to BW cube to APO-BW cube to APO planning area
or
2. R/3 to APO-BW cube to APO planning area
BW can be a enterprise BW system ( independent) or you can use the BW inbuilt in APO also referred to as APO-BW.
The only difference between the 2 BW systems is APO-BW can not take the load of reporting where as the enterprise BW can.
Unless your company policy requires the enterprie BW system, I suggest using 2nd way.
You can load the data from R/3 to APO-BW cube using extractors either generic or standard depending on your data. You need to have a RFC connection setup between APO-BW and R/3. ( This is not CIF).
When you load the data into the APO-BW cube, you just have to load the data from the cube to APO planning area using the transaction /sapapo/tscube.
Refer to [DP Data Mart|http://help.sap.com/saphelp_scm50/helpdata/en/13/5ada58309111d398250000e8a49608/frameset.htm] for more information about the data transfer between APO-BW and APO.

ALE configuration for Outbound Idoc - Help me

Hi Experts,
I am newbee in SAP and XI. I was trying to send MATMAS Idoc from R3 and i was running into some issues. So i would appreciate if someone can help me.
I am using following link as reference. /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I did all the steps mentioned in the above link ( Creating Logical Systems, Assigning Client and RFC destnations, Creating distribution models ..... etc)
and then everything went well and i saw success messags in all the steps.
I used BD10 to send material and it went well. But when i check TRFC queue, i see some error messages; "No service for system SAPRDI, client 800 in Integrion Directory"
And all the messages are hanging in the TRFC queue.
Note: I havent configured anything in XI yet. I wanted to make sure IDoc gets to XI client first.
Thank you in advance. Pls help me its very urgent.
Thanks,
Surya

I created RFC destination (SM59) and Port (IDX1)
Then i sent another material (BD10) and checked tRFC queue. i found bunch of error in the Queue.
1.connection to host 10.4.23.120, service sapgw00 timed out / CPI-C error C
No service for system SAPRDI, client 800 in Integration Directory
partner not reached (host 10.16.176.29, service sapgw00) / CPI-C error CM
connection to host 10.16.136.127, service sapgw58 timed out / CPI-C error
Note: i have noticed entries for R3 in SLD as below
System Name: RDI ( not SAPRDI as mentioned in the error message)
System Home: r3ides
That might be reason. If so, how to change it in R3 box? Any suggestions?
Please send me if you guys have any links or docs to address this issue.
Thanks,
Surya

ALE Settings For File-IDOC Scenario

Hi All,
While Doing IDOC-File Scenario we have to do the Following Settings
In XI
1) Create RFC Destination towards R/3
2) Create Port
3) Load Meta data
In R/3
1) Create RFC Destination towards XI
2) Create Port
3) Create PF
Q1) Coming to File-IDOC Scenario do we need to do the Same Settings ????
Q2) In this File-IDCO Scenario do we need to create RFC Destination in R/3 towards XI ????
Clarify me these Confusions
Regards
Bopanna

HI,
for IDOC TO FILE
We need to create the rfc destination at XI side so as to send the acknowledgement to sap r/3 as soon as idoc has been received.This is the reason WHY WE NEED RFC DESTINATION AT XI SIDE
There are are only 2 major difference in Ale settings for FILE TO IDOC AND IDOC-FILE
i.e for FILE-IDOC
1) No need to Distribute the modal view
2) For partner profile Specify the INBOUND PARAMETERS
FOR STEP BY STEP U CAN SEE THE SETTINGS GIVEN BELOW
We need to do the following settings in XI
1)   Create an RFC Destination to the Receiving System in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a)   Select Create New button
b)   Enter the port name as SAP+SID (The starting char should be SAP)
c)   Enter the destination client
d)   Enter the RFC Destination created in XI towards R/3
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client, user & Password details of Destination system
h)   Test the connection and remote logon.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(We21)
a)   First Select Transactional RFC and then click create button
b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Inbound Parameters (WE20)
a)   Create New
b)   Create the Partner no. name as same the logical system name of the destination system
c)   Select Partner type LS
d)   Enter details for Type: US/USER, Agent, and Lang
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Message Type and Process Code.
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
ALSO WE NEED TO CONFIGURE THE IDOC ADAPTER AS RECEIVER TO CONVERT THE IDOC-XML TO IDOC
PLZ REFER THE LINK BELOW.
PLZ REWARDS THE POINTS
VIKAS JAIN
                                                                                [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098]
Edited by: vikas jain on Jan 22, 2008 11:49 AM

ALE Settings for IDOC

Hi,
For configuration of IDOC adapter
1) we need to create RFC Desination both XI System and R3 System.For port creation if v given same port name in both XI system and R3 system it will work or not ?
2) On Receiver SAP system, we need to configure the logical system normally for XI system, were v can find logical system of XI System.
3) Can RFC Destination b same on both systems( R3 system, XI System)
Regards,
Praveen

Hi
The following configurations are needed for Idoc scenarios
1) ECC Configuration : a) Create RFC connections from ECC to XI in SM59. rfc connection name should be target XI logical system name . BD54 or SALE are the tcodes for checking the logical system for respective client.
                                   b) Create port in we21 & provide the above RFC destination.
                                   c) Now Create Partner Profile in we20 ...partner profile name should be target logical system name.
                                        assign the outbound parameters with receiver port created in we21.
2) XI Configuration : a) Create a RFC connection for XI to ECC ...rfc name should be target logical system name(ecc).
                                  b) Create port in IDX1...it should be SAPXXX..where XXX is the ecc system id.
                                  c) Import the idoc metadata in IDX2.
For Outbound idocs generate the model view in BD64.
Regards
Abhijit

Ale configurations for IDoc?

hi..
What are the ALE configurations need for an IDOC?
bye.

Hi,
Perform the following ALE configurations
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Also gothru this Blog <a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a> by Swaroopa Vishwanath
Regards
Santhosh
<a href="Remember to set the thread to solved when you have received a solution to set the thread to solved when you have received a solution</a>
Use a Good Subject Line, One Question Per Posting - Award Points

Urgent: Creating ALE IDOC for SALES ORDER

hi
please tell me step by step procedure to create ALE IDOC for SALES ORDER?
reward for sure
regards
ravish

Hi,
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards

Getting Error:closing a connection for you. Please help

Hello All,
I'm using jboss3.2.6. I used ejb2.1 (session bean and entity bean[BMP]). I did few data base transations in cmp and few in simple data source connection.
I'm getting below errors occasionally
'No managed connection exception
java.lang.OutOfMemoryError: Java heap space
[CachedConnectionManager] Closing a connection for you. Plea
se close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@11ed0d
5
I've given below my dao connection code here,
package com.drtrack.util;
import java.sql.Connection;
import java.sql.SQLException;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;
public class DAOUtil {
private static DataSource _ds;
public Connection con;
public DAOUtil() throws SQLException {
try {
if (_ds == null)
assemble();
if(_ds != null && con == null) {
con = _ds.getConnection();
}catch(SQLException ex) {
ex.printStackTrace();
private void assemble() {
Context ic = null;
try {
ic = new InitialContext();
DrTrackUtil drutil = new DrTrackUtil();
_ds = (DataSource) ic.lookup("java:/" + drutil.getText("SOURCE_DIR"));
drutil = null;
}catch (Exception e) {
e.printStackTrace();
}finally {
try {
ic.close();
}catch(NamingException ne) {}
public void closeConnection() throws SQLException {
if(con != null)
con.close();
con = null;
}below is the code with get connection and doing transaction in it.
public static AccountMasterValueBean getAccountMasterByAcctId(String acctId) {
AccountMasterValueBean bean = null;
DAOUtil dao = null;
CallableStatement cst = null;
ResultSet rs = null;
try {
dao = new DAOUtil();
cst = dao.con.prepareCall(DrTrackConstants.MSSQL_USP_ACCOUNTMASTER_BY_ACCTID);
cst.setObject(1, acctId);
rs = cst.executeQuery();
if(rs != null && rs.next()) {
bean = new AccountMasterValueBean(
Integer.valueOf(rs.getString("accountkeyid")),
rs.getString("latitude"),
rs.getString("longitude"));
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
if(rs != null){
try {
rs.close();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
rs = null;
if(cst != null) {
try{
cst.close();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
cst = null;
if(dao != null) {
try {
dao.closeConnection();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
dao = null;
return bean;
}I closed connections, resultsets and statements properly.
Why I'm getting these errors.? Where I'm doing wrong. ? Please help me. I have to fix them ASAP.
Thanks.

Hello All,
I'm using jboss3.2.6. I used ejb2.1 (session bean and entity bean[BMP]). I did few data base transations in cmp and few in simple data source connection.
I'm getting below errors occasionally
'No managed connection exception
java.lang.OutOfMemoryError: Java heap space
[CachedConnectionManager] Closing a connection for you. Plea
se close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@11ed0d
5
I've given below my dao connection code here,
package com.drtrack.util;
import java.sql.Connection;
import java.sql.SQLException;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;
public class DAOUtil {
private static DataSource _ds;
public Connection con;
public DAOUtil() throws SQLException {
try {
if (_ds == null)
assemble();
if(_ds != null && con == null) {
con = _ds.getConnection();
}catch(SQLException ex) {
ex.printStackTrace();
private void assemble() {
Context ic = null;
try {
ic = new InitialContext();
DrTrackUtil drutil = new DrTrackUtil();
_ds = (DataSource) ic.lookup("java:/" + drutil.getText("SOURCE_DIR"));
drutil = null;
}catch (Exception e) {
e.printStackTrace();
}finally {
try {
ic.close();
}catch(NamingException ne) {}
public void closeConnection() throws SQLException {
if(con != null)
con.close();
con = null;
}below is the code with get connection and doing transaction in it.
public static AccountMasterValueBean getAccountMasterByAcctId(String acctId) {
AccountMasterValueBean bean = null;
DAOUtil dao = null;
CallableStatement cst = null;
ResultSet rs = null;
try {
dao = new DAOUtil();
cst = dao.con.prepareCall(DrTrackConstants.MSSQL_USP_ACCOUNTMASTER_BY_ACCTID);
cst.setObject(1, acctId);
rs = cst.executeQuery();
if(rs != null && rs.next()) {
bean = new AccountMasterValueBean(
Integer.valueOf(rs.getString("accountkeyid")),
rs.getString("latitude"),
rs.getString("longitude"));
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
if(rs != null){
try {
rs.close();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
rs = null;
if(cst != null) {
try{
cst.close();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
cst = null;
if(dao != null) {
try {
dao.closeConnection();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
dao = null;
return bean;
}I closed connections, resultsets and statements properly.
Why I'm getting these errors.? Where I'm doing wrong. ? Please help me. I have to fix them ASAP.
Thanks.

How do I set miminum # of connections for pool with Oracle and Tomcat?

Hi,
I can't seem to find any attribute to initialize the number of connections for my connection pool. Here is my current context.xml file under my /App1 directory:
<Context path="/App1" docBase="App1"
debug="5" reloadable="true" crossContext="true">
<Resource name="App1ConnectionPool" auth="Container"
type="oracle.jdbc.pool.OracleDataSource"
driverClassName="oracle.jdbc.driver.OracleDriver"
factory="oracle.jdbc.pool.OracleDataSourceFactory"
url="jdbc:oracle:thin:@127.0.0.1:1521:oddjob"
user="app1" password="app1" />
</Context>
I've been googling and reading forums, but haven't found a way to establish the minimum number of connections. I've tried all sorts of parameters like InitialLimit, MinLimit, MinActive, etc, with no success.
Here is some sample code that I am testing:
package web;
import oracle.jdbc.pool.OracleDataSource;
import oracle.jdbc.OracleConnection;
import javax.naming.*;
import java.sql.SQLException;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.Properties;
public class ConnectionPool {
String message = "Not Connected";
public void init() {
OracleConnection conn = null;
ResultSet rst = null;
Statement stmt = null;
try {
Context initContext = new InitialContext();
Context envContext = (Context) initContext.lookup("java:/comp/env");
OracleDataSource ds = (OracleDataSource) envContext.lookup("App1ConnectionPool");
message = "Here.";
 String user = ds.getUser();
if (envContext == null)
throw new Exception("Error: No Context");
if (ds == null)
throw new Exception("Error: No DataSource");
if (ds != null) {
message = "Trying to connect...";
conn = (OracleConnection) ds.getConnection();
Properties prop = new Properties();
prop.put("PROXY_USER_NAME", "adavey/xxx");
if (conn != null) {
message = "Got Connection " + conn.toString() + ", ";
 conn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME,prop);
stmt = conn.createStatement();
rst = stmt.executeQuery("SELECT username, server from v$session where username is not null");
while (rst.next()) {
message = "DS User: " + user + "; DB User: " + rst.getString(1) + "; Server: " + rst.getString(2);
rst.close();
rst = null;
stmt.close();
stmt = null;
conn.close(); // Return to connection pool
conn = null; // Make sure we don't close it twice
} catch (Exception e) {
e.printStackTrace();
} finally {
// Always make sure result sets and statements are closed,
// and the connection is returned to the pool
if (rst != null) {
try {
rst.close();
} catch (SQLException e) {
rst = null;
if (stmt != null) {
try {
stmt.close();
} catch (SQLException e) {
stmt = null;
if (conn != null) {
try {
conn.close();
} catch (SQLException e) {
conn = null;
public String getMessage() {
return message;
I'm using a utility to repeatedly call a JSP page that uses this class and displays the message variable. This utility allows me to specify the number of concurrent web requests and an overall number of requests to try. While that is running, I look at V$SESSION in Oracle and occassionaly, I will see a brief entry for app1 or adavey depending on the timing of my query and how far along the code has processed in this example. So it seems that I am only using one connection at a time and not a true connection pool.
Is it possible that I need to use the oci driver instead of the thin driver? I've looked at the javadoc for oci and the OCIConnectionPool has a setPoolConfig method to set initial, min and max connections. However, it appears that this can only be set via Java code and not as a parameter in my context.xml resource file. If I have to set it each time I get a database connection, it seems like it sort of defeats the purpose of having Tomcat maintain the connection pool for me and that I need to implement my own connection pool. I'm a newbie to this technology so I really don't want to go this route.
Any advice on setting up a proper connection pool that works with Tomcat and Oracle proxy sessions would be greatly appreciated.
Thanks,
Alan

Well I did some more experiments and I am able to at least create a connection pool within my example code:
package web;
import oracle.jdbc.pool.OracleDataSource;
import oracle.jdbc.OracleConnection;
import javax.naming.*;
import java.sql.SQLException;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.Properties;
public class ConnectionPool {
String message = "Not Connected";
public void init() {
OracleConnection conn = null;
ResultSet rst = null;
Statement stmt = null;
try {
Context initContext = new InitialContext();
Context envContext = (Context) initContext.lookup("java:/comp/env");
OracleDataSource ds = (OracleDataSource) envContext.lookup("App1ConnectionPool");
message = "Here.";
 String user = ds.getUser();
if (envContext == null)
throw new Exception("Error: No Context");
if (ds == null)
throw new Exception("Error: No DataSource");
if (ds != null) {
message = "Trying to connect...";
boolean cache_enabled = ds.getConnectionCachingEnabled();
if (!cache_enabled){
ds.setConnectionCachingEnabled(true);
Properties cacheProps = new Properties();
cacheProps.put("InitialLimit","5");
 cacheProps.put("MinLimit","5");
cacheProps.put("MaxLimit","10");
ds.setConnectionCacheProperties(cacheProps);
 conn = (OracleConnection) ds.getConnection();
Properties prop = new Properties();
prop.put("PROXY_USER_NAME", "adavey/xyz");
if (conn != null) {
message = "Got Connection " + conn.toString() + ", ";
 conn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME,prop);
stmt = conn.createStatement();
//rst = stmt.executeQuery("SELECT 'Success obtaining connection' FROM DUAL");
rst = stmt.executeQuery("SELECT user, SYS_CONTEXT ('USERENV', 'SESSION_USER') from dual");
while (rst.next()) {
message = "DS User: " + user + "; DB User: " + rst.getString(1) + "; sys_context: " + rst.getString(2);
message += "; Was cache enabled?: " + cache_enabled;
rst.close();
rst = null;
stmt.close();
stmt = null;
conn.close(OracleConnection.PROXY_SESSION); // Return to connection pool
conn = null; // Make sure we don't close it twice
} catch (Exception e) {
e.printStackTrace();
} finally {
// Always make sure result sets and statements are closed,
// and the connection is returned to the pool
if (rst != null) {
try {
rst.close();
} catch (SQLException e) {
rst = null;
if (stmt != null) {
try {
stmt.close();
} catch (SQLException e) {
stmt = null;
if (conn != null) {
try {
conn.close();
} catch (SQLException e) {
conn = null;
public String getMessage() {
return message;
In my context.xml file, I tried to specify the same Connection Cache Properties as attributes, but no luck:
<Context path="/App1" docBase="App1"
debug="5" reloadable="true" crossContext="true">
<Resource name="App1ConnectionPool" auth="Container"
type="oracle.jdbc.pool.OracleDataSource"
driverClassName="oracle.jdbc.OracleDriver"
factory="oracle.jdbc.pool.OracleDataSourceFactory"
url="jdbc:oracle:thin:@127.0.0.1:1521:oddjob"
user="app1" password="app1"
ConnectionCachingEnabled="1" MinLimit="5" MaxLimit="20"/>
</Context>
These attributes seemed to have no effect:
ConnectionCachingEnabled="1" ; also tried "true"
MinLimit="5"
MaxLimit="20"
So basically if I could find some way to get these attributes set within the context.xml file instead of my code, I would be a happy developer :-)
Oh well, it's almost Miller time here on the east coast. Maybe a few beers will help me find the solution I'm looking for.

Performance degradation using Jolt ASP Connectivity for TUXEDO

We have a customer that uses Jolt ASP Connectivity for TUXEDO and is suffering
from a severe performance degradation over time.
Initial response times are fine (1 s.), but they tend to increase to 3 minutes
after some time (well, eh, a day or so).
Data:
- TUXEDO 7.1
- Jolt 1.2.1
- Relatively recent rolling patch installed (so no there are probably no JSH performance
issues and memory leaks as fixed in earlier patches)
The ULOG shows that during the night the JSH instances notice a timeout on behalf
of the client connection and do a forced shutdown of the client:
040911.csu013.cs.kadaster.nl!JSH.234333.1.-2: JOLT_CAT:1185: "INFO: Userid:
[ZZ_Webpol], Clientid: [AP_WEBSRV3] timed out due to inactivity"
040911.csu013.cs.kadaster.nl!JSH.234333.1.-2: JOLT_CAT:1198: "WARN: Forced
shutdown of client; user name 'ZZ_Webpol'; client name 'AP_WEBSRV3'"
This happens every 10 minutes as per configuration of the JSL (-T flag).
The customer "solved" the problem for the time being by increasing the connection
pool size on the IIS web server.
However, they didn't find a "smoking gun" - no definite cause for the problem.
So, it is debatable whether their "solution" suffices.
It is my suspicion the problem might be located in the Jolt ASP classes running
on the IIS.
Maybe the connection pool somehow loses connections over time, causing subsequent
users having to queue before they get served (although an exception should be
raised if no connections are available).
However, there's no documentation on the functioning of the connection pool for
Jolt ASP.
My questions:
1) What's the algorithm used for managing connections with Jolt ASP for TUXEDO?
2) If connections are terminated by a JSH, will a new connection be established
from the web server automatically? (this is especially interesting, because the
connection policy can be configured in the JSL CLOPT, but there's no info on how
this should be handled/configured by Jolt ASP connectivity for TUXEDO)
Regards,
Winfried Scheulderman

Hi,
For ASP connectivity I would suggest looking at the .Net client facility provided in Tuxedo 9.1 and later.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

We have an airport extreme wifi in house, but also want to set up a hardwired ethernet connection for gaming and streaming of netflix. The computer only sees one or the other not both at same time.

We have a new iMac 2.9ghz and are running an airport extreme set up in house with several express entenders. The problem is that our son is streaming netflix and doing on line gaming and hogging all the band width. Time Warner tech suggested a hard wired ethernet connection to computer base sattion next to computer so that it can have direct conenction to internet. After much fishing of wire the connection worked great, but the wifi connection for the house is gone. I unplugged the ethernet connection and everything is fine. I read the articles about adjusting network preferences, but the issue seems to be in the extreme not in the computer. the connection goes from cable modem to extreme, from extreme to house and to hard wired conenction to other computer. Do we need a splitter before the extreme?

No. Something else is going on.
Your son may be hogging all the bandwidth but your wireless network should never simply disappear. Moreover, if your son isn't doing anything the available bandwidth for other devices should remain unaffected.
I suspect that something is miswired, and from what you describe I suspect that link is between the Extreme and the "other computer".
The way to accomplish what you propose is
Modem > Ethernet cable to Extreme's WAN port
Extreme's LAN ports > wired Ethernet devices.
There should be nothing but an Ethernet cable linking an Extreme LAN port and any other wired device. If you run out of available LAN ports on the Extreme, you need to by an "Ethernet switch" - they are not expensive, but don't call it a "splitter" or you will only confuse yourself. The switch would be connected to one of the Extreme's LAN ports, and you would connect additional devices to it. You can also use one of your Expresses for that purpose, assuming it is the current generation model with two Ethernet ports.

ISA B2B logon Error: No valid private connection for internet user

Hello ,
i used isauseradm to create a user zzweb with all authorizations for B2B..
now when i try to log to
http://host:port/b2b/b2b/init.do with the user zzweb
i have a runtime error with the logs :
EXCEPTION]
#1#com.sap.isa.businessobject.BORuntimeException: Error getting private connection for internet user:com.sap.isa.core.eai.BackendException: Error: No valid private connection for internet userzzweb
     at com.sap.isa.businessobject.BusinessObjectHelper.splitException(BusinessObjectHelper.java:78)
     at com.sap.isa.user.businessobject.UserBase.login(UserBase.java:313)
     at com.sap.isa.businessobject.User.login(User.java:143)
     at com.sap.isa.user.action.UserActions.performLogin(UserActions.java:295)
     at com.sap.isa.user.action.UserActions.performLogin(UserActions.java:368)
     at com.sap.isa.user.action.UserBaseAction.performLogin(UserBaseAction.java:126)
     at com.sap.isa.user.action.LoginBaseAction.ecomPerform(LoginBaseAction.java:77)
     at com.sap.isa.isacore.action.EComBaseAction.doPerform(EComBaseAction.java:353)
     at com.sap.isa.core.BaseAction.execute(BaseAction.java:211)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at com.sap.isa.core.RequestProcessor.processActionPerform(RequestProcessor.java:674)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
     at com.tealeaf.capture.LiteFilter.doFilter(Unknown Source)
     at com.sap.isa.isacore.TealeafFilter.doFilter(TealeafFilter.java:61)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:373)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
what does this error means..?
i also realised that zzweb was not created in CRM backen? should it be created ?
many thnx for help ..
Message was edited by: Blackman

Its a late response... but if someone gets the same issue here is the solution.
When you register try uppercase password . That should take care of that issue.
The problem is with function module CRM_ISA_IUSER_SWITCH , Note 946536.
Although the note says 5.0 the problem exists with ISA 4.0 too

ALE connection for E-reruitment to ECC

Similar Messages

Maybe you are looking for