You will get Content administrator Shown below. Once you get to below screen , enter the JCo name. Give some logical name. On next screen, select the J2EE engine where you want to assign the JCo , b y default you should assign it to the local engine. Check with your portal developer if you are not sure about type of JCo. Here provide the connection details.
From the Message Server drop down you can select system details fetched from SLD , or you can enter the details manually. We'll send a magic link to your inbox. Email Address. All Sign in options. Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox.
Newsletter Topics Select minimum 1 topic. Tags: SAP Basis. Bhupinder Singh June 26, 0 Comments. Please help Thanks Bhupinder Singh. Many thanks!!! Glad to hear that. Well as I stated above I got it working, e.
It is functionality of SE37 which means to pick and use the specified destination from SM59 instead of a local execution. There is no other way. What you want is not possible and makes no sense. Why should I call system A and tell it to execute it on system B? In this case one would directly address system B. Could you please elaborate "use a different destination name with a different set of connection parameters"?
What exactly should be different and how? My client is now opening just single destination which finally ends up executing the default implementation and not my registered program. Not sure what do you mean by system B, there is just one SAP with one registered server program.
Oh, now I see you edited your question after my answer. This is now a completely different question. Please see my other answer for your modified question about calling a registered external RFC server program instead of an ABAP system.
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
0コメント