Issue in EM installation in wily.

[former_member201800]

Hi Team,

I am installing Wily version=9.5.6.0 on solman 7.1 SP12(Windows 2012).

I downloaded the below files:

osgiPackages.v9.5.6.0.windows

WILYISEM06_0-70000324

WILYWORK06_0-70000140

eula.txt

I unzip WILYISEM06_0-70000324 and kept the file osgiPackages.v9.5.6.0.windows and eula.txt in this folder. Also, i have accepted the license in eula.txt and ca-eula. Now i am trying to install EM using the file introscope9.5.6.0windowsAMD64SAP, but it is creating the dir apmintroscope once, then deletes it.

I have changed the installation dir in installer file also.

Would request you to please suggest me, how to resolve this issue.

[patelyogesh · Accepted solution]

Hello Shyam,

You need to modify installer.properties file to make sure its pointing to right files.

You can find installation guide @ https://websmp105.sap-ag.de/~sapidb/012002523100016951232015E/SAPISDOC97.pdf

Note: Please read Section 3 carefully..

Alternatively you can use link below for your reference

Thanks

Yogesh

[former_member201800 · Accepted solution]

Hi All,

Solman 7.1 SP12

I am using http://hostname:8000/ as sld.

But i am not able to access http://hostname:50000/.

How can i access http://hostname:50000/ link.

Regards,

Shyam

[patelyogesh · Accepted solution]

Hello Shya,

Since you are using dual stack system this is right URL. Use 8000 port for your all configuration.

-Yogesh

[former_member201800 · Accepted solution]

Hi Yogesh,

I am using 8000 port only for all configuration.

But http://hostname:50000/. should work. I am not able to open it.

There is no log update in work dir or server0/log dir.

Also, in jcmon, all the processess are running fine.

How can i rectify this issue?

[hemanth2 · Accepted solution]

Dear Shyam,

Hope you are doing good.

Can you check whether the HTTP ports are right in the visual admin -> dispatcher settings.

If teh port is busy, you need to check if it was due to some other process.

netstat -an   grep <portname>

The state of the socket associated with the specified port number is returned. If the socket is listening for incoming connections (and therefore in use), then its state is "LISTEN".

Also the Network Diagnosis with NIPING tool will be useful (sap note: 500235). Please check this along with the OS/network colleagues.

For example:

1) if port 15001 is in use, then use the following

command:

netstat -a   grep 15001

The result will be similar to the following:

*.15001 .... LISTEN

I would also recommend to check note 1925352 and use the SAPControl webservice interface

or message server monitoring to ascertain whether the 50000 port is correct and a live access point.

Hope this helps.

_ _ _ _ _ _ _ __ _ _

Kind Regards,

Hemanth

SAP Product Support

_ _ _ _ _ _ _ _ _ _ _

Join me online: <http://scn.sap.com/people/hemanth.kumar/content>

[former_member201800 · Accepted solution]

Hi Hemanth,

Thanks for the reply. I checked in MMC.

50000 port is maintained correctly.

Also, i have restarted the server0 but there is no log updated in /server0/log and work dir.

Regards,

Shyam

[patelyogesh · Accepted solution]

Hello Shyam,

Please look for HTTP ports and let me know what you see there? The one you have selected its "dospatcher"

Regards,

Yogesh

[former_member201800 · Accepted solution]

Hi Yogesh,

HTTP port has the status LISTEN status. Also, i am getting below error in SLD:

#195 06/27/2016 09:05:23.795 [SAPEngine_Application_Thread[impl:3]_21] ERROR com.sap.lcr.sagent.DataSupplierServlet: IO Error

Thrown:

com.sap.engine.services.httpserver.exceptions.HttpIOException: The connection is closed.

at com.sap.engine.services.httpserver.server.io.HttpInputStream.read(HttpInputStream.java:184)

at com.sap.engine.services.httpserver.server.io.ChunkedInputStream.unchunkNext(ChunkedInputStream.java:95)

at com.sap.engine.services.httpserver.server.io.ChunkedInputStream.read(ChunkedInputStream.java:57)

at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)

at java.io.BufferedInputStream.read(BufferedInputStream.java:277)

at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.readData(EncodedDataReader.java:271)

at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.fetchData(EncodedDataReader.java:334)

at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:167)

at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)

at com.sap.engine.lib.xml.parser.XMLParser.scanName(XMLParser.java:392)

at com.sap.engine.lib.xml.parser.XMLParser.scanName(XMLParser.java:363)

at com.sap.engine.lib.xml.parser.XMLParser.scanQName(XMLParser.java:351)

at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1892)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1858)

at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2454)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1855)

at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2454)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1855)

at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2857)

at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:235)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)

at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)

at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)

at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)

at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)

at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)

at com.sap.lcr.sagent.DataSupplierServlet.doPost(DataSupplierServlet.java:170)

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

at com.sap.lcr.sagent.DataSupplierServlet.service(DataSupplierServlet.java:242)

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

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

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

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

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

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Please suggest.

Regards,

Shyam

[former_member201800 · Accepted solution]

Hi Hemanth,

Thanks for the solution..

Regards,

Shyam Kumar