on 05-23-2013 6:51 AM
I have luck getting an example work. So I have reply from SAP and I almost happy now 😉 but here are one thing making me sad :
I do not like saving SAPLogin and password into any text file. Is there any way to avoid this?
Documentation says: "The first step defines destination names and properties.
NOTE
For this example the destination configuration is stored in a file that is called by the program. In practice you should avoid this for security reasons." How to code without storing properties into the file?
I am sorry I am not Java-programmer. I had some programming skill but it was on pre-OOP epoch.
So Java it's somekind of AbraKadabra for me.
As long as you run your application on a NetWeaver AS Java in the end you can just skip the first 32 lines of code you have posted and define the Destination in the NWA (http://<server>:<port>/nwa/destinations).
The code you have posted should be just for local testing ONLY where you usually don't have installed a complete NW AS
Greethings
Ingo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dmitry,
You can as well create a RFC destination and store a password in it. From your program you just need to call the existing destination. Check section Establishing an RFC Connection Using an Existing Destination in this link http://help.sap.com/saphelp_nw73/helpdata/en/17/d609b48ea5f748b47c0f32be265935/content.htm
Cheers!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.