Wrong message server ms://host:8120/P4

[Former Member]

Hello All,

We have PI 7.1 installation on Windows OS.

In Runtime Workbench -> Component Monitoring we have wrong http server name for Adator Engine, I had chech all parameter in Echange profile for :

com.sap.aii.connect.* all parameter are correcet and i donot know where can change that.

When I try to start the Integration Builder that has the wrong http server name.

Thanks for any help

Reza

[hemanth2 · Accepted solution]

Hi Reza ,

Hope you are doing good.

There are some steps that you need to check:

Note:1911741 - PI ESR: Cannot connect to server using message server ms:// P4
and

Note:note 1571274:Cannot connect to server using message server ms:// .

Also ensure that port is open in firewall .I am not sure if you are using high availability, but if so,

inorder to limit the P4 port to only one network address, you can use the HOST argument of the icm/server_port_x parameter, e.g.:

icm/server_port_1 = PROT=P4,PORT=<port>,HOST=<hostname>

More info:
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/3ae05299c172d0e10000000a42189c/frameset.htm

Thank you!

____________

Kind Regards,

Hemanth

SAP AGS

[Former Member · Accepted solution]

Hi Hemanth,

Thanks Again for reply.

We had splet central instance and application server for this  PI installation.

Now we use webdispatcher  to connecet with PI.

I had change alle parameter on Exchange Profile with correcet http name and port.

But still Adator Engine use the old URL.

Thanks

Reza

[hemanth2 · Accepted solution]

Hi Reza,

Is the port correct?

Please see:

SAP Library - PI (Process Integration)

These ports should be the SCS message server host name, HTTP port, and HTTPS port.Can you check if the P4 port is available? Note 1925352 will help you to check this (you can
use the sapcontrol command) to ascertain whether the P4 port is correct and a live access point.

Also connect to "http:<message server host>:<message server HTTP

port>/msgserver/text/logon?version=1.2" as the note states to check if the port is right.

regards,
hemanth

[hemanth2 · Accepted solution]

Is the port right? I think it should be 8121 instead of 8120.
You should be using the SCS MS port (not the abap MS port).

[madasamy_arunachalam · Accepted solution]

Hi

In general, P4 port is 50004 if Central Instance # 00.

To confirm this, you can check under Instance details of "System info" (Select Central Instance from the NW Admin/System Info.).

Ensure, port 50004 is opened across firewall if communication/application ports are restricted in your network.

regards

Swami

[Former Member · Accepted solution]

Hi Hemanth,

Thanks Again

Yes the port i correcet. Will try run PI SLD Self Registration fron NWA to see it helps

Thanks Again I will come back with result

Reza

[hemanth2 · Accepted solution]

Great.
try with both ports and check whether they are accessible (using Note 1925352).
Basically both links should work:

http:<ABAP message server host>:<message server HTTPport>/msgserver/text/logon?version=1.2

and

http:<J2EE SCS message server host>:<message server HTTPport>/msgserver/text/logon?version=1.2

and you should be good to go

[hemanth2 · Accepted solution]

Hi reza,

I have also requested the owner of the notes to amend them and add more detail (like the one I mentioned earlier), so that this is more clear: Note:1911741 and note 1571274

Regards,
hemanth

[hemanth2 · Accepted solution]

Great.

Please keep us posted.
I would gather that both links are working:

http:<ABAP message server host>:<message server HTTPport>/msgserver/text/logon?version=1.2

and

http:<J2EE SCS message server host>:<message server HTTPport>/msgserver/text/logon?version=1.2

[Former Member · Accepted solution]

Hello,

I need some advice for PI SLD.

I had tried to PI SLD Self Registration from NWA for fix this issue. Before start PI SLD Self Registration I took an export for of All CIM Instances.

After I
done PI SLD Self Registration I got much
more issue in PI.

Now I start again for import the backup for All CIM Instances in sld. I get
some warning, but I decide to continue because the export was from the same
sld-

   Now I am not sure if this kind export and
import of All CIM Instances for the same system can had any
impact.

Any body has done this kind
of export and import of All CIM Instances.

Thanks for any advice

Reza

[Former Member · Accepted solution]

Hi Hemanth,

Thanks Again for reply:

My scenario is

We had split central instance and application server for this  PI installation.
Now we use webdispatcher  to connecet with PI.

I had tried the URL for MS server.  http://sapqxa.vestas.net:50200/text/logon?version=1.2

Result was :

This page can't be displayed

• Make sure the web address http://sapqxa.vestas.net:50200 is correct.
• Look for the page with your search engine.
• Refresh the page in a few minutes.

The

http://sapqxa.vestas.net:50200 is url for MS server and we should use webdispatcher sapqxw:8100.

The Adaptor Engen not working
Unable to establish connection to http://sapqxa.vestas.net:50200/AdapterFramework/rtc
Unable to establish connection to "http://sapqxa.vestas.net:50200/AdapterFramework/rtc?FromRWB=true" 

Now I am not sure we can use webdispatcher for this connection

When I try with http://sapqxw.vestas.net:8100/sapqxa/text/logon?version=1.2 from webdispatcher.

Result is

404   Not Found

  Error: The requested resource does not exist.
  Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/JSTS/Home
Details: Go to main page of this application!

Thanks

Reza

[hemanth2 · Accepted solution]

Hi Reza,

The link is incorrect:

http://sapqxa.vestas.net:50200/text/logon?version=1.2

50200 is the HTTP port of the server node, not the message server.
To find the J2EE message server port, check the dev_ms file in /usr/sap/<SID>/SCS<nr>/work and for the

ABAP server , check the /usr/sap/<SID>/DV.../work/dev_ms file.

For example in the above server, 8177 is the message server port.

Regards,
Hemanth

[hemanth2 · Accepted solution]

Hi Reza.can you attach some screenshots of the issue; the exact error that you get.

[Former Member · Accepted solution]

Hi Hemanth,

Thanks again for reply.

You are right the sapqxa:50200 is the HTTP port for the server node.

The massage server port for abap is 8144 and for java is  8146.

If you see the screenshot from my first post,

We use wedbdispatcher with port sapqxw:8100 to contact  Pi server node.

From my screenshot the Adator Engine using sapqxa:50200 and it should be as we use webdispatcher server sapqxw:8100.

And I donot know where I can change that parameter for this connection to saåqxw:8100. I had check and change alle parameter in exchangeprofile. But  still Adator Engine using sapqxa:50200.

The http://sapqxa.vestas.net:50200/text/logon?version=1.2  give

Result was :
This page can't be displayed
• Make sure the web address http://sapqxa.vestas.net:50200 is correct.

Thanks

Reza

[hemanth2 · Accepted solution]

Hi Reza,

Perhaps this is a port iccue and not an SAP issue. To check this, can you use sapcontrol or any other technique mentioned in Note 1925352 to see if the ports that you mentioned are live and actual access points?

regards,
Hemanth

[Former Member · Accepted solution]

Hi Hemanth,

This problem is solved by using note 804124.

Now I have another question.

IS it possible to use wendispatcher for start PI integration Builder?

I get a error as is in this note

1571274 - Cannot connect to server using message server ms://

But not help me

Thanks Again for help

Reza

[hemanth2 · Accepted solution]

Hi Reza,

Great news!!!

Yes, this can be done. Please see SAP Note 1614690 and implement all the properties.

Also as the below linkmentions, there is a bug in oracle end; so please check all the points mentioned:

http://wiki.scn.sap.com/wiki/display/XI/Troubleshooting+PI+ESR+and+Integ ration+Builder+Logon+Issues

If the issue persists, check the:

1) The output of "sapwebdisp -checkconfig pf=<WDP profile>";

2) dev_webdisp trace: set the following parameter in the    Web Dispatche trace: "rdisp/TRACE = 3". Restart it, reproduce the issue and more details should b available.

Regards,
Hemanth

[Former Member · Accepted solution]

Hi Hemanth,

Thanks  the SAP Note 1614690 was a very good  help. it is working.

Reza

[hemanth2 · Accepted solution]

Great news Reza .
Please let us know if you face any other issues.

Kind regards,
Hemanth

[Former Member · Accepted solution]

Thanks for asking.

Reza

[former_member184720]

Your SLD registrations seems to be inconsistent.

I would suggest you to go through the below wiki to register them again.

How to Manually Correct the Registration of XI Components Within the SLD - Process Integration - SCN...

[Former Member]

Hello Hareesh,

Thanks for help, I will try that and come back with result.

Thanks

Reza

[Former Member]

I had tried to remove just Adapter Engine from sld  but after restart the XI components are registered once more with the same infomation. in sld

[former_member184720]

Did you check the mentioned note?

1. For RWB, please enter the following URL in your browser and send the request:

http://<host>:<port>/rwb/rtc?op=init

This triggers self-registration of RWB.

2. To register the Adapter Engine, you have to restart the following applications:

sap.com/com.sap.aii.af.app

sap.com/com.sap.aii.af.cpa.ap

1031321 - Self-Registration of Adapter Engine and RWB fails

[Former Member]

Hello,

Yes I did check this not and had used the URL and restart

applications:

sap.com/com.sap.aii.af.app

sap.com/com.sap.aii.af.cpa.ap

from NWA

Thanks Again

Reza