Polarion integration with HP Quality Center

Description
maucasal
Posts: 2
Joined: Fri May 16, 2014 12:32 pm

Polarion integration with HP Quality Center

Postby maucasal » Fri May 16, 2014 12:51 pm

Hi, I'd like to get some help in order to have our Polarion ALM 2013 integrated with the HP ALM Quality Center 12.

I'm struggling to setup the Connectors part, where I need to configure the Connections and Synchronization Pairs.

I read the link "Read full documentation" that is available at the top of the Connectors screen, but unfortunately the information provided there is really high level.

So, when I configure the Connections part, there are 2 setups: Rest Connection and Database Connection. I configured the Rest Connection only, and the Database Connection I left blank. This setup seems to be ok, the configuration was successfully saved.

When I try to configure the Synchronization Pairs, the Polarion Configuration seems to be ok (there is a green mark saying it's ok), but I never managed to configure the HP ALM Configuration part. I filled the Domain name and Project name. When I click on "Test Connection" I receive the following message: "ERROR: The Domain 'DEFAULT' or project 'wii' is unknown". On the HP ALM Quality Center side, the domain and project names are correct, also I'm providing a userid that has administrative rights on the 'test' project.

How can I troubleshot this problem? Do I need to install any kind of Add-in on the HP ALM Quality Center side?

Whenever I try to test the REST connection, I see the following error on the HP ALM QC 12 side:
INFO | jvm 1 | 2014/05/16 14:48:31.105 | 2014-05-16 14:48:31.089:WARN:oejs.CookieCutter:java.lang.IllegalArgumentException: Cookie name "Version" is a reserved token
INFO | jvm 1 | 2014/05/16 14:48:31.105 | 2014-05-16 14:48:31.089:WARN:oejs.CookieCutter:java.lang.IllegalArgumentException: Cookie name "Path" is a reserved token
INFO | jvm 1 | 2014/05/16 14:48:31.105 | 2014-05-16 14:48:31.089:WARN:oejs.ServletHandler:/qcbin/rest/domains/DEFAULT/projects/wii/customization/entities/defect/fields
INFO | jvm 1 | 2014/05/16 14:48:31.105 | org.hp.qc.web.restapi.exceptions.NoQCSessionCookieException: QCSession cookie missing from request.
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.hp.qc.web.restapi.sessionmanagement.HttpLayerSessionUtils.initializeSession(HttpLayerSessionUtils.java:258)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.hp.qc.web.restapi.sessionmanagement.SessionValidatorFilter.doFilter(SessionValidatorFilter.java:82)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at com.hp.sw.bto.ast.security.lwsso.authenticator.springSecurity.LWSSO2SpringSecurityIntegrationFilter.doFilter(LWSSO2SpringSecurityIntegrationFilter.java:319)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.hp.qc.web.restapi.authentication.QC2SpringIntegrationFilter.doFilter(QC2SpringIntegrationFilter.java:36)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.hp.qc.web.restapi.sessionmanagement.AlmExceptionTranslationFilter.doFilter(AlmExceptionTranslationFilter.java:33)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.hp.qc.web.restapi.authentication.FilterChainProxyWrapper.doFilter(FilterChainProxyWrapper.java:90)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1330)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at com.mercury.optane.core.state.ServerStatusFilter.doFilter(ServerStatusFilter.java:35)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1330)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at com.hp.alm.platform.web.HTTPMethodsFilter.doFilter(HTTPMethodsFilter.java:52)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1330)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:478)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:312)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.Server.handle(Server.java:345)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:919)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:582)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:218)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:51)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:586)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:44)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)
INFO | jvm 1 | 2014/05/16 14:48:31.105 | at java.lang.Thread.run(Thread.java:722)

Thanks for any help!

steffenw
Posts: 9
Joined: Mon Jun 25, 2012 8:37 am

Re: Polarion integration with HP Quality Center

Postby steffenw » Thu Oct 23, 2014 2:35 pm

Hello,

were you able to solve the problem described above? Because I found exactly the same behavior. But I was using Polarion 2014 SR1 together with HP ALM Quality Center 2014.

Kind regards

Steffen

engeleb
Posts: 199
Joined: Wed Aug 09, 2006 10:55 am

Re: Polarion integration with HP Quality Center

Postby engeleb » Fri Oct 31, 2014 10:59 am

Hello,
support for HP ALM 12 was added in Polarion 2014 SR2, with earlier versions it was not possible to connect to HP ALM 12.

Best Regards,
Benjamin

steffenw
Posts: 9
Joined: Mon Jun 25, 2012 8:37 am

Re: Polarion integration with HP Quality Center

Postby steffenw » Tue Nov 04, 2014 7:47 am

Hello Benjamin,

thanks for your reply. These are not very good news. I've been told that it will take a while until the newest SR will be rolled out in our company. Therefore we stick on 2014 SR1 for the next months. What do you think, would it be possible to get a patch for SR1 to solve this issue?

Thanks for your help

Steffen

engeleb
Posts: 199
Joined: Wed Aug 09, 2006 10:55 am

Re: Polarion integration with HP Quality Center

Postby engeleb » Tue Nov 04, 2014 8:51 am

Hello Steffen,
usually we don't deliver new features as patch.
You could discuss the issue with support, maybe an exception is possible.


Best Regards,
Benjamin


Return to “Polarion Application Lifecycle Management (ALM)”

Who is online

Users browsing this forum: No registered users and 9 guests