|
Home > Archive > WebSphere Portal Server > November 2004 > Portlet Installation - Failed to get WPS SOAP Port
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Portlet Installation - Failed to get WPS SOAP Port
|
|
| Jochen Boehringer 2004-11-08, 5:51 pm |
| Hello,
I try to install portlets on a WPS 5.0.2.2 installation, running on WAS SF
5.1.1 (Windows 2000 Server SP4).
When I select the war file containing the portlet and upload it, I get an
error message APIN0003E. (Error installing war file).
In the detail view I can see several stack traces. The last one ist:
java.lang.ArrayIndexOutOfBoundsException: 0
at
com.ibm.wps.pe.mgr.appserveradmin.WAS5AdminServiceHelper.getSoapPort(WAS5Adm
inServiceHelper.java:647)
at
com.ibm.wps.pe.mgr.appserveradmin.WAS5AdminServiceHelper.getAdminProperties(
WAS5AdminServiceHelper.java:462)
at
com.ibm.wps.pe.mgr.appserveradmin.WAS5AdminServiceHelper.getAdminClient(WAS5
AdminServiceHelper.java:315)
at com.ibm.wps.pe.mgr.appserveradmin.WAS5Admin.initVars(WAS5Admin.java:341)
at com.ibm.wps.pe.mgr.appserveradmin.WAS5Admin.(WAS5Admin.java:241)
at
com.ibm.wps.pe.mgr.appserveradmin.WAS5Admin.getInstance(WAS5Admin.java:268)
at
com.ibm.wps.pe.mgr.appserveradmin.AppServerAdminManagerFactory.getManager(Ap
pServerAdminManagerFactory.java:60)
at
com.ibm.wps.pe.mgr.PortletApplicationManagerImpl.getAppServerAdminManager(Po
rtletApplicationManagerImpl.java:204)
at
com.ibm.wps.pe.mgr.PortletApplicationManagerImpl.installWebModule(PortletApp
licationManagerImpl.java:793)
And leads to the following exception:
com.ibm.wps.pe.mgr.exceptions.InitException: PEAS0009E: Failed to get WPS
SOAP port.
at
com.ibm.wps.pe.mgr.appserveradmin.WAS5AdminServiceHelper.getSoapPort(WAS5Adm
inServiceHelper.java:695)
at
com.ibm.wps.pe.mgr.appserveradmin.WAS5AdminServiceHelper.getAdminProperties(
WAS5AdminServiceHelper.java:462)
at
com.ibm.wps.pe.mgr.appserveradmin.WAS5AdminServiceHelper.getAdminClient(WAS5
AdminServiceHelper.java:315)
at com.ibm.wps.pe.mgr.appserveradmin.WAS5Admin.initVars(WAS5Admin.java:341)
at com.ibm.wps.pe.mgr.appserveradmin.WAS5Admin.(WAS5Admin.java:241)
at
com.ibm.wps.pe.mgr.appserveradmin.WAS5Admin.getInstance(WAS5Admin.java:268)
at
com.ibm.wps.pe.mgr.appserveradmin.AppServerAdminManagerFactory.getManager(Ap
pServerAdminManagerFactory.java:60)
at
com.ibm.wps.pe.mgr.PortletApplicationManagerImpl.getAppServerAdminManager(Po
rtletApplicationManagerImpl.java:204)
at
com.ibm.wps.pe.mgr.PortletApplicationManagerImpl.installWebModule(PortletApp
licationManagerImpl.java:793)
I think that this problem is caused by an invalid portal configuration. I
have a configuration with active global security (was security). So I guess
the wps soap port configuration is missing? Where can I configure the
missing parameter the portal is looking for?
Any help would be greatly appreciated!
Jochen
| |
| Oliver Meyer 2004-11-09, 2:50 am |
| Jochen,
you have to add the user who installs the portlet to the "monitor" role
of the application server. Otherwise the user will not get the SOAP
port. This behavior changed with WSAS 5.1.1
Oliver
| |
| Jochen Boehringer 2004-11-11, 5:53 pm |
| > you have to add the user who installs the portlet to the "monitor" role
> of the application server. Otherwise the user will not get the SOAP
> port. This behavior changed with WSAS 5.1.1
Oliver,
thanks, this solved my problem:-)
Jochen
|
|
|
|
|