on 10-28-2008 7:22 PM
Hi people,
I have got a tricky question. How can i write a PDF to a target destination using FTP? It seems easy but i have got same constraints, which are:
1 - I will get data from PDF in one string element (xstring in R/3, base64Binary in PI 7.0), that i get from an RFC call.
2 - I can not have anything from this PDF in monitoring, string or PDF file. (A must be)
3 - I can't add any beans. (I am not allowed)
4 - I can´t write or keep this PDF file in a PIs UNIX machine directory. Neither R/3 can do that. (We are not allowed)
5 - I am not allowed to change stuff in J2EE engine, or any kind of engine. Can't add/change adapters either.
You may ask, what can you do then? Well, i can write code for mappings. And put that mapping anywhere it fits, taking in consideration the 5 constraints above.
Is ABAP mapping a solution? Is it possible to write code in ABAP without saving PDF file in a directory?
Ideas, who can give me some?
Thank you for you attention,
Pedro Pereira
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Henrique,
Well i must use XI, i like it :).
I just have hard constraints, which are not imposed by me.
Well, with ABAP mapping i think i can send file to destiny via FTP, but i can not write it in PIs machine before send it...I am going to try to get authorization to keep this file temporarily in PIs machine, that would be good news for me...
Thank you for your attention,
Pedro Pereira
Hello all,
I have a similar problem in a WS->XI->WS scenario.
My idea was to somehow run some code in the XI server that would make the transfer of the file (an XML with data to update another database) instead of running the file directly through XI, but I could not find a way to solve the J2EE Engine constraint Pedro also seems to have.
Any help would be appreciated.
Regards
Hi Pedro,
I'm not sure if you can avoid msgs being monitored, but you can definitely avoid a user from seeing it.
In the S_XMB_MONI authorization object, you can define the access level for the users in the monitor by parameters like component, party, interface name etc.
By default, it's probably "*" but you could limit access of all users to this message.
Other than that, try to set the TRACE lvl to 0 in SXMB_ADM.
Regards,
Henrique.
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.