ALE Configurations for JDBC to PROXY scenario

Can some body tell me what are the ALE configurations that needs to be done in both the systems and also in XI system.

Hi there
No need for ALE confihuration unless you are using IDocs in your scenario.
You need to configure the integration engine in the Proxy system using SXMB_ADM and create an RFC for the Integration server.
on the JDBC side you'll need the database bridge configured in the communication chanell...
what is your scenario specific...which system types and versions?
Nimrod

Similar Messages

Database error for JDBC to Proxy Scenario

Hello SAP PI Gurus,
I am having a JDBC to Proxy Scenario .And the interface is running at 10 min of duration.
However, my other interface are running fine with the same details.
But for this interface, it giving the belwo error :
Database-level error reported by JDBC driver
while executing statement 'call proc_dtdc_prod_summary'.
The JDBC driver returned the following error message: '
com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Table
'dtdc_prod_summary_temp' already exists'. For details,
contact your database server vendor.
So increased the time from 10 min to 20 min to 30 min. But the erro remians.
So pls look into this and give your suggestion.
Regards,
Ravi

Hi Ravi,
Please check execution of your stored procedure is resulting with creation of Table : dtdc_prod_summary_temp.
Modify your stored procedure to just fetch records or insert records in the existing table. Or change the code to Create a table 'dtdc_prod_summary_temp only if it doesn't exits in the Table data base.
Regards
Praveen K

ALE Configuration for PEXR2002 IDoc and PAYEXT message type sending to XI

Hi all,
I need ALE Configuration for PEXR2002(Basic Type) IDoc , it's message type PAYEXT.
I don't know ALE Configuration for sending data from SAP IDS to SAP XI.????
I need ALE Configuration doc/pdf??
Please give me some guidline for this..
Regards,
Umesh

Umesh,
I was wondering if you have had any luck creating the configuration for PEXR2002 Idoc, PAYEXT message types, and sending the result set to XI.
I need to perform the same task within our R3 environment using the FTP protocol in XI to send the file to the Bank to be processed.
Any help or direction would be great.
Thanks,
Dave

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 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

JDBC To Proxy Scenario Problem

Dear All,
I am doing JDBC to Proxy scenario. In SXMB_MONI in XI Message is sucessful and JDBC Adaptor fetching records also. These records are seen in SXMB_MONI.
When I check in SXI_MONOTOR in R/3 , message is sucessful, but payload is Blank. The selected records in JDBC are not reaching R/3 . What may be the problem
Raghvendra

Check the mapping between the JDBC response and the Proxy response in XI?
Does the JDBC response have the valid rows? If yes, check what is the output mapping that is sent to the Proxy.
Regards
Bhavesh

ALE Configurations for IDOC2IDOC scenario

Hi Experts,
Can anyone list down wht r the ALE configurations are required for IDOC2IDOC scenario?
1. Sender SAP ---> XI
2. XI ---> Reciever SAP
Please provide me the TCodes with the details that are needed for the above scenario?
Your help is higly appreciated
Rgds
Faisal....
Edited by: Abdul Faisal on Jul 28, 2008 11:49 AM

Hey,
Steps for ALE settings:-
Steps for XI
Step 1)
 Goto SM59.
 Create new RFC destination of type 3(Abap connection).
 Give a suitable name and description.
 Give the Ip address of the R3 system.
 Give the system number.
 Give the gateway host name and gateway service (3300 + system number).
 Go to the logon security tab.
 Give the lang, client, username and password.
 Test connection and remote logon.
Step 2)
 Goto IDX1.
 Create a new port.
 Give the port name.
 Give the client number for the R3 system.
 Select the created Rfc Destination.
Step 3)
 Goto IDX2
 Create a new Meta data.
 Give the Idoc type.
 Select the created port.
Steps for R3.
Step 1)
 Goto SM59.
 Create new RFC destination of type 3(Abap connection).
 Give a suitable name and description.
 Give the Ip address of the XI system.
 Give the system number.
 Give the gateway host name and gateway service (3300 + system number).
 Go to the logon security tab.
 Give the lang, client, username and password.
 Test connection and remote logon.
Step 2)
 Goto WE21.
 Create a port under transactional RFC.(R3->XI)
 Designate the RFC destination created in prev step.
Step 3)
 Goto SALE.
 Basic settings->Logical Systems->Define logical system.
 Create two logical systems(one for XI and the other for R3)
 Basic settings->Logical Systems->Assign logical system.
 Assign the R3 logical system to respective client.
Step 4)
 Goto WE20.
 Partner type LS.
 Create partner profile.
 Give the outbound or inbound message type based on the direction.
 In your Sender R3:- outbound
 In your Receiver R3:- Inbound.
Step 5)
 Goto WE19
 Give the basic type and execute.
 fill in the required fields.
 Goto IDOC->edit control records.
 Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
 Click outbound processing.
Step 6)
 Go to SM58
 if there are any messages then there is some error in execution.
 Goto WE02.
 Check the status of the IDOC.
 Goto WE47.
 TO decode the status code.
Step 7)
 Not mandatory.
 Goto BD64.
 Click on Create model view.
 Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
WE42 process code
WE47 status info.
<removed by moderator>
regards,
 Milan
Edited by: Mike Pokraka on Jul 28, 2008 5:04 PM

ALE Configurations in File to IDOC Scenario

Hi All,
We are doing File to IDOC Scenario.
ALE Configurations done:
R/3 Side:
1. Created RFC dest, pointing to XI and tested the connection for remote login to XI.
2. Created port in R/3(using automatically generated port name) and assigned the RFC dest created above.
3. Created partner profile and assigned the ports to the message types.
4. Created Logical system
XI side:
1. Created RFC dest, pointing to XI and tested the connection for remote login to r/3.
2. Created port using IDX1 transaction with port name starting with SAP<SID> and assigned the RFC dest created above. (SID of XI)
3. Unable to load metadata in XI.
Now we are unable to test the scenario as it provides an error message in MONI as "Error: Transaction IDX1: Port SAP<SID>, client , RFC destination contain errors".
Also Let me know whether the steps mentioned above are correct for the scenario.
Regards,
Nithiyanandam

Hello,
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 XI 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 #####+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.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
With Regards,
Vidya.
*******Reward with Points if found useful

EOIO is not working for file- BPM- Proxy scenario.

Hi All,
I have one File to BPM (Merge pattern ) to Proxy scenario.
I have two file communication channel at the sender side and defined QOS as EOIO for both. In SXMB_MONI it assings same queue for all messages.
BPM is merging that messages. However during that it assings different queue for merged messages.
When it comes to proxy , again different queues are assingned to the messages.
Is there any way I can define QOS in BPM or at the proxy side ( I know it should be at the sender side only , but it's not working..)
Thanks & Regards,
Dijesh Tanna.

HI,
Within the current release the BPM will always only use EO (SAP Note 833740).
May be the SAP note 905049 will help you on this ...
Thanks
Swarup

Alert Configuration for File to IDoc scenario

I have followed Alerts : Step-by-Step /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
and configured Alerts for file to IDoc scenario.
But the problem is, I did not notice any alerts being generated. I could notice the IDocs being posted to destination system. So I was going through Alerts-Troubleshoute Guide. In intension to maintain monitoring level, I clicked Configuration tab. But I did not notice my sender and receiver system there to maintain.
Can any body help me to detail out the procedure to add sender and receiver systems to maintain the monitoring level?
Regards,
Suraj Kumar

hi Suraj,
WHich SP version are you on??
If you are on Sp14 or above, then unfortunately, Michal's Trouble Shooting for Alerts will not help.
From SP14 onwards, activation of end to end monitoring is not needed for Alerting. Refer to this note 870232 for this info.
Next, to test if your Alerts have been defined correctly, go to SE38. In the program , type RSALERTTEST and then click on EXECUTE button ( F8 ). In the next window, it will ask you for your ALERTCATEGORY. Just give the name of your ALERT CATEGORY and click EXECUTE.
If you have configured your alerts correctly, you will receive a message that tells ALERT IS GENERATED and will give the ALERT ID.
Now, go to your Run TIme workbench and then select ALERT INBOX and see if you have got the ALERT message in your ALERT INBOX.
If this is working fine, then the last step, implement the note 913858.
Regards,
Bhavesh

ALE Configuration for Transactional Data (Purchase Order)

Dear Experts,
I want to configure ALE for Purchase Orders(Transactional Data).
For that:
I have done neccessary Condition Records at NACE with necessary Output Type Configuration. Configured Port and Partner Profile with Message Types: ORDERS and ORDECHG (as Outbound Parametrs) .Assigned those Message Types against defined Sender and the Receiver at Customer Distribution Model . Configured Port and Partner Profile at the Receiver System also.
Now I have 2 queries.
i) Is this much of ALE configuration is enough for Transactional Data for communication between 2 systems or I have to do something more?
ii) For Master Data we configure Change Pointer(we can see field assignments against Change Document Object at BD52 for Master Data Messaage Types) . Is it necessary to configure Change Pointer for Transactional Data or it will autometically handled by the system(field assignments cannot be seen against Change Document Objects at BD52 for Transactional Data Messaage Types)?
Regards
Arnab

Hi kumar,
what Alexander said is absolutely correct .
from your second question no master data distribution configuration is required for the transactional data distribution.
let us know once if you face any problems.
~linagnna

Sld configuration for rfc to soap scenario

Hi all,
The scenario which i am planning to do, describes how the Custom RFC client application in SAP R/3 System invokes a free Web service (that is hosted over the internet) using SAP XI. For our demo purpose, we have used a free web service available on the Internet.
In this scenario we will be using GetQuote method of Web service DelayedStockQuote. This method retrieves the Stock quote for the given Stock symbol. The method GetQuote has an input that takes in two parameters Stock Symbol and License Key and returns the following information.
StockSymbol,
LastTradeAmount,
LastTradeDateTime,
StockChange,
OpenAmount,
DayHigh,
DayLow,
StockVolume,
PrevCls,
ChangePercent,
FiftyTwoWeekRange,
EarnPerShare,
PE,
CompanyName.
Link to web service:
http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx?op=GetQuote
In this scenario, I planned to create two mappings, first between RFC Request to SOAP Request and second between SOAP Response to RFC Response .
Adapter in sender communication channel is RFC.(RFC Protocol)
Adapter in receiver communication channel is SOAP.(HTTP Protocol)
Result:
On testing this scenario, In the Sender R/3 system we have to Execute the Report program we have created earlier. When the program is executed with Stock symbol it should get the details of that stock symbol from the Web service.
My question here is what would be the sld configuration for webservice.whether it is a Java WAS or third party.If it is a third party or java WAS,what would be the system name and host name.
Any clarification from you all is welcome and will be highly appreciated.
With Regards
Karthik.

Hi,
I would suggest you is to use third party. It is a web service, and does not matter the technology behind it (if it is java, abap, .net, cobol, no difference! it will be described by a wsld).
System name and host name doesn't matter too, you will not use this information in runtime, and you will specify host name and so at integration directory. You can make your standard on it, for example, put the name as DelayedStockQuote and host as http://ws.cdyne.com.
regards.
roberti

ALE configuration for printer

Hi all,
Can u tell me how to configure printer setting using ALE.
Senario:
As we have 2 clients 200 and 500. 200 is open and 500 is closed.
If we configure printer from spad in 200 client the same should reflect on 500.

Umesh,
I was wondering if you have had any luck creating the configuration for PEXR2002 Idoc, PAYEXT message types, and sending the result set to XI.
I need to perform the same task within our R3 environment using the FTP protocol in XI to send the file to the Bank to be processed.
Any help or direction would be great.
Thanks,
Dave

Configuration for JDBC support in Jakarta-Tomcat-4.0

I have used JSP pages which call packaganame.classname in the useBean directive. This works fine when I have simple programs, but when my class uses JDBC connectivity, this does not work. I get NullPointerException on the browser. I am currently using Jakarta-tomcat4.0 web server.
I have added the following entry in the server.xml file for JDBC
connectivity, but it still does not work ...
" <Realm className="org.apache.catalina.realm.JDBCRealm"
debug="99"
driverName="sun.jdbc.odbc.JdbcOdbcDriver"
connectionURL="jdbc:odbc:<DSNName>"
userTable="Parts" userNameCol="<user_name>" userCredCol="<password>"
/>"
Does this support JDBC, if so do I need to do additional configurations
The Database used is Access2000.
Your suggessions would be of great help.

Hi there,
Firstly, check if you have the JDBC driver on the machine that runs Tomcat. You need this to talk to your database.
Secondly, "NullPointerException" can be caused by the connection to the database is not opened yet, make sure your code to open the conn before doing a query to the your database.
Thirdly, from what you stated below it looks like JDBC-ODBC bridge driver instead of pure JDBC driver connectivity.
In conclusion, you should provide more information abt your configuration for us to help you.
$-art

Issue with ALE configuration for creating the idoc for Purchase orders

Hello,
I am trying to send the purchase order through message type configuration using ALE.
I am using idoc ORDERS05, message ORDERS, Process Code in Partner profile ME10.
In NACE transaction for the Application EF, Output Type NEU the ALE Configuration is done for Program RSNASTED Form ALE_PROCESSING.
I have done ALE distribution using BD64.
Now the problem is that when an order is created or changed in the message output of the PO I am seeing the status as yellow i.e.not processed.
In NAST table, the entry is there but on executing RSNAST00 nothing happens.
Please provide me the pointers to solve the given problem.
Regards,
Mayank

Hi,
Guess it looks like the output is getting proposed but its not getting processed. Check the output type configuration. Check the TIme Settings in the output type configuration.
It is possible to set the Time when the output must be processed. Is it on SAVE or is it set to other settings. If its set to via background job then the background job must be run to process the output types.
Check and let me know if all is fine at the output type configuration.
Cheers
VJ

ALE Configurations for JDBC to PROXY scenario

Similar Messages

Maybe you are looking for