transaction "soamanager"

[Former Member]

Hello

Does anyone knos since which version of ECC transaction "soamanager" exists. I think it exists in all supported products(it is just metter of configuration or?)

can you help me in this regards

Thank you in advance

Jan

[Former Member · Accepted solution]

SOAMANAGER is part of SAP_BASIS 700 and newer.

[Former Member]

Thank you Samuli, thank you Kishore

as the metter of fact I can see our system is SAP_BASIS 700 SP 22.

After some research I found there is another (solution manager system) running on this host.

Also trx "soamanager" today opens an internet explorer window however from solution manager.

I am sure one of the reason is port which is same on both systems for HTTP.

The url is http://sapis2:8080/sap/bc/webdynpro/sap/appl_soap_management?sap-language=SK

I wander what else is prerequisite for "soamanager" to function in such an environment

If important platform is win/sql

Thank you in advance

Jan

[Former Member]

Yes, SOAMANAGER is an Web Dynpro ABAP application. Depending on which SAP instance you start the transaction the URL or at least the port should be different. You can go to transaction SMICM ->Services to see what port is being used for HTTP.

[Former Member]

Hello

I had to enter parameter "icm/server_port_0" with value "PROT=HTTP,PORT=8081" however I had timeout: I solved it in trx "smicm"->"goto"->"services"->choosed HTTP->"change"->entered 3600 for "max processing time"->after restart of smicm "soamanager" started to function

However after restart of system I had to enter again the max. processing time.

Is it possible to enter this setting permanaently?

Thank you in advance

Jan

[Former Member]

Yes, by editing the instance profile in transaction RZ10.

[Former Member]

Hi Jan,

Note 1120273 - Migration of 6.40 and 7.00 WS configurations to 7.20

The new WS framework was introduced with NetWeaver Release  7.10 and was also ported to NetWeaver Release 7.00, Support Package 14  and higher (Enhancement Packages). The introduction of a new WS  framework is required because the previous SAP WS framework does not  meet specific requirements, in particular, requirements concerning the  security and the usage of Web Services Reliable Messaging (WSRM).

The WS framework of NetWeaver 6.40/7.00 does not support the additional  requirements (such as WSRM or additional security logs). Furthermore,  this is a framework that can be managed only manually. There is no  option to automatically set up required WS configuration scenarios or to manage several WS configurations in one step.

The features described above that are missing in the ABAP WS framework from NetWeaver 6.40 are provided in the WS framework NetWeaver 7.10.

FYI... please refer below notes.

Note 1120273 - Migration of 6.40 and 7.00 WS configurations to 7.20

Note 1318499 - Transportability of Web services

Thanks

Kishore Cherukumalla