cancel
Showing results for 
Search instead for 
Did you mean: 

MessageServlet URL is not working

Former Member
0 Kudos

Hi all,

I just done a SOAP to RFC scenario in a newly installed XI server environment.

Earlier this scenario worked for me in other XI servers.

Since it is a newly installed XI server, I am getting a problem with webservice.

The problem is when I point, my browser to the URL

http://<hostname>:8000/XISOAPAdapter/MessageServlet?channel=:<BusinessSystem>:<SenderCommunicationCh...;

It is giving the message as follows:

**********************************************************************************************

Service cannot be reached

What has happened?

URL http://<hostname>:8000/XISOAPAdapter/MessageServlet call was terminated because the corresponding service is not available

error code is 404

***********************************************************************************************

Actually when I point the mentioned URL, I should get the message something like "MessageServlet OK".

Because of this I am not able to run my scenario.

Can any body help me in this regard, what should be done in basis activites.

Advacne Thanks......

Praveen Gujjeti

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

http://<hostname>:8000/ in port give ur XI port number not of HTTP port

former_member181985
Active Contributor
0 Kudos

Thanks SreeRam,

As you mentioned, it is working for XI port which is 50000, in my case

But, I still have one doubt, regarding these XI port, HTTP port.

In my previous XI server, the same thing worked for me with http port: 8000

In my current XI server, it is working with xi port : 50000, as you mentioned.

can you clarify me in this......

Once again thanks for your time.

Thanks

Praveen Gujjeti

Former Member
0 Kudos

good it works. if ur using httport then ur directly tryingpoint to intergation server not through adapter .

can you close the thread.

Sreeram Reddy

Answers (2)

Answers (2)

Former Member
0 Kudos

check ur port number for new XI installation in SMICM seriveces and http

Former Member
0 Kudos

Hi,

Description: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.

Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404

• 404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)

• Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port

• If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system

• If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Regards

Chilla

former_member181985
Active Contributor
0 Kudos

Hi Chandra and Sriram,

Sorry for my late reply to your response. As you mentioned, I checked everypoint.

They are correct as you mentioned.The http port is 8000 only.

I have two Communication channels in my scenario, one is for SOAP Sender, the other is RFC receiver.

When I look into communication channel monitoring,

CC_SOAPSender Channel started but inactive THIRDPARTY_BS SOAP Sender

Still I am not able to find the solution for it.

Help me in this regard.

thanks,

praveen gujjeti

Former Member
0 Kudos

then activate this THIRDPARTY_BS SOAP Sender

Former Member
0 Kudos

Hi,

Started and inactive means , i hope check the Adapter Configuration details.

And reactivate

Regards

Chilla

former_member181985
Active Contributor
0 Kudos

My communcation channel is CC_SOAPSender. It is in the business system "THIRDPARTY_BS".

In Adapter communication channel monitoring, it is showing yellow triangular button, with status message as "Channel started but inactive".

For your reference, I have activated the businness system and CC in the standard ChangeList.

Do I have to install or deploy any services in visual adminstrator for SOAP adapter?

Advance Thanks,

Praveen Gujjeti

former_member181985
Active Contributor
0 Kudos

Hi Chandra,

Is Adapter Cofiguration your mentioning should be done in Visual Administrator or it is something else.

Please help me in this.

Thanks,

Praveen Gujjeti

Former Member
0 Kudos

activate ur sender agreement , saop sender adapter

former_member181985
Active Contributor
0 Kudos

All the objects are already activated in Integration Repository and Integration Directory which are relevent my scenario.

Are there any other possibilities.

Thanks.............

Former Member
0 Kudos

Hi,

No not in Vis Admin. it is in your Communication Channel , check the configurations

and just modify ,save and reactivate .

Also refresh the Cache.

Regards

Chilla