Update CONNECT Build with CONNECTAdminGUI in WebLogic Servers.

Description

For the CONNECT WebLogic EAR, CONNECTAdminGUI should only build within the CONNECT EAR when the "AdminGUI" profile is explicitly activate. The build should successfully deploy on WebLogic, where AdminGUI functionality can be tested (See CC). Access via http://localhost:8080/CONNECTAdminGUI/Login.xhtml

CC:

1. CONNECTAdminGUI does not built into the EAR by default – only when using the AdminGUI profile.
2. CONNECTAdminGUI can be deployed as part of the CONNECT EAR on WebLogic; once deployed, able to log in.
3. Run the ValidationSuite in both Passthrough and Standard mode for services like PD,DQ,DR,DS and AD.
4. Able to follow these test cases: https://connectopensource.atlassian.net/wiki/display/FCPT/ADMIN+GUI+Test+cases

QA:

See CC.

Resolution Details

The AdminGUI dependencies are added to ear/lib and jsf packages are used that is packaged within application and is specified in weblogic-application.xml.

https://github.com/CONNECT-Solution/CONNECT/pull/779

Activity

Show:

Srinivas Murthy May 15, 2014 at 12:00 AM

Tested the following:
1. Build with AdminGUI in glassfish, weblogic. Deployed in glassfish and weblogic. Tested AdminGUI in both glassfish and weblogic. Executed validation suite in standard and passthru modes.
2. Build without Admingui and verified that the CONNECTAdminGUI war file not exist in the ear. Deployed in glassfish and weblogic. AdminGUI not workinng. Executed validation suite in standard and passthru modes.

Srinivas Murthy May 14, 2014 at 1:23 PM

Taken for QA

Alamelu Chidambaram May 5, 2014 at 6:17 PM

Weblogic.xml to use the application bundled jsf which let the ear to deploy.

javax.faces.application.ViewExpiredException: viewId:/Login.xhtml - View /Login.xhtml could not be restored.
at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:205)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
at org.apache.myfaces.webapp.MyFacesServlet.service(MyFacesServlet.java:112)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:242)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:216)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:132)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:338)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3288)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3254)
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:2163)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2089)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2074)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1513)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:254)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Alamelu Chidambaram May 5, 2014 at 6:11 PM

The weblogic-application.xml is updated to include jsf jars within CONNECTAdminGUI project war/lib.But the ear is not deployable getting

Unsupported protocol: https'
at com.ctc.wstx.sr.StreamScanner.throwFromIOE(StreamScanner.java:699)
at com.ctc.wstx.sr.ValidatingStreamReader.findDtdExtSubset(ValidatingStreamReader.java:480)
at com.ctc.wstx.sr.ValidatingStreamReader.finishDTD(ValidatingStreamReader.java:341)
at com.ctc.wstx.sr.BasicStreamReader.skipToken(BasicStreamReader.java:3353)
at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:1970)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1114)
at weblogic.servlet.internal.dd.glassfish.GlassFishWebAppParser.parseDescriptor(GlassFishWebAppParser.java:113)
at weblogic.servlet.internal.dd.glassfish.GlassFishWebAppParser.getWeblogicWebAppBean(GlassFishWebAppParser.java:97)
at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1486)
at weblogic.servlet.internal.WebAppModule.init(WebAppModule.java:253)

Resize issue view side panel

Fixed

Details
Assignee
Srinivas Murthy
Reporter
Alamelu Chidambaram
Labels
AdministrationGUI
LOE
Unknown
Story Points
3
Time tracking
1w 4d 3h logged
Sprint
None
Fix versions
Release 4.4
Priority
Minor
Parent
CONN-48 As a CONNECT developer, I want to provide a mechanism to manage gateway configuration, so that my team and our adopters can more easily manage their gateway.

Created May 5, 2014 at 1:57 PM

Updated May 15, 2014 at 12:00 AM

Resolved May 14, 2014 at 1:05 PM