sfc site2site transfer to remote site

[Former Member]

Hi all,

when transferring SFC from local site to a remote site I do receive an error message in Collaboration Log Report:

Server returned HTTP response code: 500 for URL: http://remoteserver:port/manufacturing-xml/com/sap/me/integration/xchange/client/ProductionInterface...

The URL in general seems to be correct. When calling it manually in internet explorer I receive the following message:

Login and password for site * are required to run Xchange via HTTP (Message 18613)

data set up in remote site:

• system, rules according to How To Guide for Collaboration Features
• material maintained, with routing assigned
• user for site2site transfer maintained

Assigning the user configured for site2site transfer also to site * does not help any.

data set up in source site

• collaboration link, system rule, site maintenance including remote site according to How-To-Guide
• export template NO_SFC_DATA to ensure the error is not caused by missing data straucture in destination site

Transfer of SFCs of this material between local sites works fine.

For me it seems to be a problem of remote site2site transfer only.

Does anyone know if there are more settings to be considered?

Thanks

Ulrike

[former_member182330]

Hi Ulrike,

1. What is ME version?

2. Have you provide credentials on Collaboration tab in Site Maint.?

3. Check NW defaultTrace on remote system. It should have details why request failed.

Br,

Konstantin

[Former Member]

Hi Konstantin,

1. ME 6.0

2. yes, credentials have been provided

3. I found several messages like this in NW log:

Cannot process an HTTP request to servlet [jsp] in [manufacturing-xml] web application.

For more details on the problem please check traces searching by logId: C000AC11100503BD00000001000054E7

Can you say from this what is missing?

Do HTTP requests have to be configured somewhere?

Or maybe the user does not have sufficient user rights? Can you say which netweaver roles have to be assigned to the user?

Thanks

Ulrike

[former_member182330]

If you attach NW defaultTrace files, maybe I would be able to figure it out. Error message should be there. Just make sure the trace file covers timeframe when you get this error.

Br,

Konstantin

[Former Member]

I just found those two message in system logs and traces which might indicate what's going wrong:

warning:

LOGON to DX by */null attempt from ... with result: FAILURE: 18613

error:

Cannot process an HTTP request to servlet [jsp] in [manufacturing-xml] web application.

[EXCEPTION]

Message Type "PRODUCTION_XML_ERROR" does not exist (Message 12103)

at com.sap.me.messaging.adapter.AlarmToMessageAdapter.send(AlarmToMessageAdapter.java:211)

at com.sap.me.messaging.adapter.AlarmToMessageAdapter.logProductionXMLError(AlarmToMessageAdapter.java:502)

at JEE_jsp_com_sap_me_integration_xchange_client_ProductionInterface_2077950_1352212392000_1376573916867._jspService(JEE_jsp_com_sap_me_integration_xchange_client_ProductionInterface_2077950_1352212392000_1376573916867.java:274)

at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:428)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:147)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)

at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

[former_member182330]

Is this error message in the logs on destination server? If so, check if PRODUCTION_XML_ERROR message exists in Message Type Maintenance in destination site. If no - reload initial data for the site in Site Maintenance.

Br,

Konstantin

[Former Member]

Yes, this was a message from logs on destination server.

I checked message type maintenance at destination site. PRODUCTION_XML_ERROR did already exist. I additionally assigned the user group of the transfer user to this message type. But the same error message occurs in netweaver log.

Reload of initial data did not change anything also.

Any other ideas?

BR Ulrike

[sergiy_katerinich]

Hi Urlike,

Issue of missing RODUCTION_XML_ERROR is a side-effect of S2S failure.

Provided the warning from the log, it looks as if wrong user credentails are given for authorization. If both users at te source and destination sites have SAP_ME_INTERGATOR roles in addition, then it might be a bug of S2S that requires further invesitgation within a support ticket.

Regards,

Sergiy.

[Former Member]

I checked the user role assignment. At destination site SAP_ME_INTEGRATOR role was missing. I added it but still receive the same error message. We will log a support ticket.

Thanks a lot for your help so far

BR Ulrike

[former_member323997]

hi Sergiy,

the ticket has been created: Site2site not successful ( 765312 / 2013 )

Thanks & regards,

Leon