SOLVED Completing Wizard

orclahmaad · Oct 29, 2016, 10:24 AM

When I try to insall last version, everything is fine, can see the wizard screen. But in one step, WLSDM asks password, then I’m entering the valid weblogic username/password, but is warns me as below and could not bypass this screen. Could you plase help me to overcome this issue.

####<Oct 29, 2016 12:47:12 PM EEST><SEVERE><WLSDM><BEA-000000><java.lang.ClassNotFoundException: oracle.security.jps.wls.providers.trust.TrustServiceIdentityAsserterMBean

java.lang.RuntimeException: java.lang.ClassNotFoundException: oracle.security.jps.wls.providers.trust.TrustServiceIdentityAsserterMBean
	at weblogic.management.jmx.MBeanServerInvocationHandler.newProxyInstance(MBeanServerInvocationHandler.java:623)
	at weblogic.management.jmx.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:435)
	at com.sun.proxy.$Proxy174.getAuthenticationProviders(Unknown Source)
	at com.wlsdm.B.F.checkConn(MBSConnection.java:215)
	at com.wlsdm.K.F.y(Data.java:4067)
	at com.wlsdm.K.F.A(Data.java:266)
	at com.wlsdm.K.F.doGet(Data.java:102)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:844)
	at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:280)
	at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:254)
	at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:136)
	at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:346)
	at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
	at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
	at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
	at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
	at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3436)
	at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3402)
	at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
	at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
	at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
	at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2285)
	at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2201)
	at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
	at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1572)
	at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:255)
	at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
	at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
Caused by: java.lang.ClassNotFoundException: oracle.security.jps.wls.providers.trust.TrustServiceIdentityAsserterMBean
	at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:357)
	at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:318)
	at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:80)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
	at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:186)
	at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:50)
	at weblogic.management.jmx.MBeanServerInvocationHandler.newProxyInstance(MBeanServerInvocationHandler.java:621)
	... 28 more
>
####<Oct 29, 2016 12:47:41 PM EEST><SEVERE><WLSDM><BEA-000000><null

WLSDM Support · Oct 29, 2016, 1:06 PM

Could you please give below details?

WebLogic version?
Any installed FMW product like SOA, ADF… etc.?

By the way, it’s for sure you did not setup boot.properties on your domain. Add boot.properties to your WebLogic domain, then WLSDM would not ask username|password. You will bypass that screen. This is not a workaround, it’s just the configuration that your WebLogic domain must be configured with.

For the error above, we’re going to investigate and it’s important to reply us your environment details.

Secondly, make sure your nodemanager.properties is configured as "startScriptEnabled=true"

WLSDM Support · Oct 29, 2016, 1:06 PM

Could you please give below details?

WebLogic version?
Any installed FMW product like SOA, ADF… etc.?

By the way, it’s for sure you did not setup boot.properties on your domain. Add boot.properties to your WebLogic domain, then WLSDM would not ask username|password. You will bypass that screen. This is not a workaround, it’s just the configuration that your WebLogic domain must be configured with.

For the error above, we’re going to investigate and it’s important to reply us your environment details.

Secondly, make sure your nodemanager.properties is configured as "startScriptEnabled=true"

orclahmaad · Oct 29, 2016, 1:45 PM

Thanks, I have tested on my local environment, it worked when I add boot.properties.

Weblogic version --> 12.1.3
Domain type --> OSB

SOLVED Completing Wizard

WLSDM: Native WebLogic Monitoring & Diagnostics