on 07-11-2006 9:38 AM
Hi All,
When sending messages through our XI server, everything works fine, but there is one thing that is bugging me, and that might lead to problems with some upcoming interface modifications.
In the message header there is a field called TimeSent. This field is automatically filled by XI with the time the message was sent, in the following format: YYYY-MM-DDTHH:MM:SSZ
This is all nice and cosy, but in our system (DEV, QA and PRD) this time is off by two hours. The time in the field is always two hours earlier than the REAL time it was sent.
Does anyone have an idea about how to correct this? It would be greatly appreciated, since we have to do a modification on an interface that uses this field...
Thanks and regards,
Yordy
Edit: We checked this against another XI system (A completely different system, with a completely different company) and it seems they have the same problem...
Could someone check this in their system? Just open a message in SXMB_MONI, and look at the header data. Then check if the TimeSent is out of sync with the time displayed in the list of SXMB_MONI...
Thanks and regards,
Yordy
Message was edited by: Yordy Minderhoud
hi,
this is probably taken from the system time
on your operaiton system
can you check the time setting on your server (current time, zone etc.)?
Regards,
michal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
I'm sorry to say that we not yet found a fix to this problem...
We are using some workarounds in several scenario's, mostly using a java module in the XSLT mapping to get the current date and time, but for now, the problem persists on the XI system itself.
Regards,
Yordy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think some of the following might be few reasons.
If you multiple Java clusters running for you and each with different time zones then this might occur. Ask you XI admin to look at clusters time zones in Visual Admin ...More on clusters below
http://help.sap.com/saphelp_nw04/helpdata/en/53/97583c2439e66fe10000000a114084/content.htm
The other one , As the J2EE Engine makes use of the time zone features of the JDK this will cause problems if the JDK does not contain the DST fix.
Refer SAP note : 983147 , 896209
Hi,
In the SXMB_MONI the time XI specifies is the time of the local machine from which the request is sent.
where as inside the TimeSent tag in Header the time XI uses its Server time.
So say for example,if i test an interface from my system which has CET time zone and where as the server is in california with PST time zone,the SXMB_MONI entry will have CET time and Header would have PST time.
RGds,
Vasanth.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michal and Vasanth,
Thank you for your replies.
We have checked the OS times on the server, but they are set correctly. Also, we have a local adapter, and this gives us the same problem. So it's not just on the central server intance, but also the local adapter. So if we test on the local adapter, it should be the exact same time...
All systems (OS, R/3, XI) have the same timezone set. All are set to GMT+1, Amsterdam.
Might this have something to do with the different systems of time used by Java and SAP? (SAP uses GMT, and Java uses UTC?)
Hi Yordy,
the mapping gets executed in the JAVA Stack and so, if you are getting the Execution time during the mapping in the java stack, then the time reflected will be the time in the Java Stack.
So, one option would be to modify this time in the mapping accordingly with respect to your ABAP stack time zone.
regards,
Bhavesh
hi,
you can the java timezone from
http://server:port/sap/monitoring/SystemInfo
and then click on <b>system properties... </b>
parameter:
user.timezone should be the one
Regards,
michal
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.