How to install and configure J2EE server in ECC 6.0

Question

hi,
I created a web service in ECC and I want to test it via SOAMANAGER but when I clik on open web service for selected naviagator binfing it gives me an error
wsnavigator call WAS TERMINATED Because The Corresponding Service is not available.
I searched the forum, apparently it is because the J2EE server is not configured
thank you for your help

Answer 1

Try this-----
Setting Up a Connection to a J2EE Server for the Web Services Navigator
To be able to use the Web Service Navigator to test a Web service, you need to set up a connection to a J2EE server, because the Web Service Navigator runs on the Java stack.
Procedure
Go to the Technical Administration tab.
Choose Global System Settings.
Choose the Web Services Navigator tab.
Choose Edit / Display.
Specify a host name and a port number.
If you are working with a J2EE engine with SAP NetWeaver 2004 or 7.0, select J2EE engine is 6.40 / 7.0.
If this option is not selected, the system assumes that you are working with a J2EE engine with version 7.10 or later.
Save.
Setting Up the Connection to the Services Registry
To create a connection between the provider system and the Services Registry, perform the following steps for each consumer.
From the SOA Manager main screen, go to the Technical Administration tab.
Choose Global System Settings.
Go to the Services Registry tab.
Choose New to create a new connection.
Note
To change the settings of an existing connection, choose Edit. To delete an existing connection, Choose Delete.
End of the note.
Specify a Services Registry.
The Services Registry name has to be written as a single word, for example, ERP_REGISTRY.
To make this the primary Services Registry, select Primary.
Each time a provider is configured, its endpoints are automatically published to the primary Services Registry.
Choose Next.
Choose a proxy class to use for communication with the Services Registry.
You can choose either of the following:
CO_SERVICES_REGISTRY_FLAT_SI
The recommended consumer proxy to configure the connection to the Services Registry. CO_SERVICES_REGISTRY_FLAT_SI is the interface between the ABAP back-end system and the Services Registry system, and contains the appropriate authentication information.
CO_ESREGISTRY_WSSI
This consumer proxy was used in previous versions.
The service path is determined automatically based on the proxy class name.
Specify a logical port.
Use uppercase characters for the logical port name.