It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×7,478
×6,113
×403

question asked: Dec 25 '13, 8:50 a.m.
question was seen: 4,958 times
last updated: Dec 31 '13, 8:24 a.m.

Related questions

Not able to Deploy reporting components during RRDI configuration. RRDI 2.0.5 with CLM 4.0.5

0
Tariq Ashraf (25●10●17) | asked Dec 25 '13, 8:50 a.m.
edited Dec 25 '13, 9:16 a.m.

RRDI Installation And Configuration

Server 1: RRDI 2.0.5 and WAS 8.0.0 , DB2 9.7 Enterprise 32-Bit, Windows 2008 R2

Server 2: CLM 4.0.5 and WAS 8.0.7, DB2 9.7 Enterprise 64-Bit, Windows 2008 R2

I have stuck at STEP : Build and Deploy Reporting Components.

I have following issue during configuring RRDI with CLM

the issue appears on the step "Deploying the EAR file to the specified application.."

Does anyone know what could be the issue?

Thanks & Regards,

Tariq Ashraf

Accepted answer

0
permanent link
Francesco Chiossi (5.7k●1●11●19) | answered Dec 30 '13, 4:07 a.m.
Hello Tariq

The error "ADMA0207E: Module p2pd.war contains an unsupported xmi format bindings or extensions file." is similar to the one discussed in this WAS technote:

You cannot deploy applications or modules that use Java EE 5 descriptors with XMI bindings or extensions
http://www-01.ibm.com/support/docview.wss?uid=swg21498622

However the defect is reported as fixed in WAS 8.0.0.1; I understand that you are probably already on a later version but you might want to double check.

Best Regards,

Francesco Chiossi
Tariq Ashraf selected this answer as the correct answer
Comments
1
Tariq Ashraf commented Dec 31 '13, 8:24 a.m.

Hi Francesco,

      I am very thankful to you. The problem was the same you have mentioned.

I was using WAS 8.0.0 for RRDI setup. I have upgraded the WAS 8.0.0 to WAS 8.0.0.7 and the problem resolved.

Thanks & Regards,

Tariq Ashraf

2 other answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Francesco Chiossi (5.7k●1●11●19) | answered Dec 27 '13, 3:50 a.m.
Hello Tariq,

you might want to check the RRDI Setup logs ( found here: [Rational_Reporting_installation_directory]\setup\logs\rrdi_setup.log ) and the WebSphere logs to get more information on why the setup fails.

Best Regards,

Francesco Chiossi


0
permanent link
Tariq Ashraf (25●10●17) | answered Dec 29 '13, 3:14 a.m.

Hi Francesco,

         Thanks for your help. I have checked the log file but couldn't find the loophole, I have set the maximum heap size to 2048 but it is still showing 1024 in log file. Can you please check the below log file and trace out the issue.

12/25/2013 01:46:55,328 INFO  com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService : CRRRA2029I: Change and save the Cognos configuration.
12/25/2013 01:46:59,328 INFO  com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService : CRRRA2042I: Configure Jazz Namespace.
12/25/2013 01:47:02,625 INFO  com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService : CRRRA2043I: Enabled Jazz Namespace.
12/25/2013 01:47:02,765 INFO  com.ibm.rational.rrdi.setup.resources.ResourceService : CRRRA0137I: Loading the model
12/25/2013 01:47:02,781 INFO  com.ibm.rational.rrdi.setup.resources.ResourceService : CRRRA0139I: Loaded the model
12/25/2013 01:47:02,781 INFO  com.ibm.rational.rrdi.setup.resources.BackupDataService : CRRRA0004I: The backup data is not found.
12/25/2013 01:47:02,781 INFO  com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService : CRRRA2030I: Prepare to deploy p2pd.ear file on the WebSphere Application Server.
12/25/2013 01:47:02,781 INFO  com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService : CRRRA2031I: Check whether the p2pd.ear file was deployed.
12/25/2013 01:47:31,359 INFO  com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService : CRRRA2033I: Set the maximum heap size on the WebSphere Application Server: 1024.
12/25/2013 01:47:38,203 INFO  com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService : CRRRA2034I: Set the environment entries on the WebSphere Application Server.
12/25/2013 01:47:38,234 INFO  com.ibm.rational.rrdi.setup.resources.ResourceService : CRRRA0137I: Loading the model
12/25/2013 01:47:38,234 INFO  com.ibm.rational.rrdi.setup.resources.ResourceService : CRRRA0139I: Loaded the model
12/25/2013 01:47:38,250 INFO  com.ibm.rational.rrdi.setup.biserver.utils.WASUtil : PATH
12/25/2013 01:47:38,250 INFO  com.ibm.rational.rrdi.setup.biserver.utils.WASUtil : {C:\Program Files\IBM\RRDI\cognos\bin64;C:\Program Files\IBM\RRDI\cognos\bin}
12/25/2013 01:47:38,250 INFO  com.ibm.rational.rrdi.setup.biserver.utils.WASUtil : true
12/25/2013 01:47:38,250 INFO  com.ibm.rational.rrdi.setup.biserver.utils.WASUtil : COGNOS_DIR
12/25/2013 01:47:38,250 INFO  com.ibm.rational.rrdi.setup.biserver.utils.WASUtil : {C:\Program Files\IBM\RRDI\cognos}
12/25/2013 01:47:38,250 INFO  com.ibm.rational.rrdi.setup.biserver.utils.WASUtil : false
12/25/2013 01:47:38,250 INFO  com.ibm.rational.rrdi.setup.biserver.utils.WASUtil : \"cells/RCWIN2K8Node01Cell/nodes/RCWIN2K8Node01/servers/server1|server.xml\"
12/25/2013 01:48:17,484 INFO  com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService : CRRRA2035I: Add Java security provider to WebSphere Application Server installation location.
12/25/2013 01:48:45,046 INFO  com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService : CRRRA2036I: Deploy the p2pd.ear file on the WebSphere Application Server.
12/25/2013 01:48:45,046 INFO  com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService : wasRoot=C:\Program Files (x86)\IBM\WebSphere\AppServer earPath=C:/Program Files/IBM/RRDI/cognos/p2pd.ear COGNOS_APP_NAME=IBM Cognos COGNOS_WAR_NAME=p2pd profileName=appsrv01 enableAdminSecurity=true
12/25/2013 01:49:27,781 ERROR com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService : WASX7209I: Connected to process "server1" on node RCWIN2K8Node01 using SOAP connector;  The type of process is: UnManagedProcess
WASX7015E: Exception running command: "$AdminApp install "C:/Program Files/IBM/RRDI/cognos/p2pd.ear" {-appname "IBM Cognos" -MapWebModToVH {{ "IBM Cognos" p2pd.war,WEB-INF/web.xml default_host }} -target WebSphere:cell=RCWIN2K8Node01Cell,node=RCWIN2K8Node01,server=server1}"; exception information:
 com.ibm.websphere.management.application.client.AppDeploymentException: com.ibm.websphere.management.application.client.AppDeploymentException: ADMA0207E: Module p2pd.war contains an unsupported xmi format bindings or extensions file.


12/25/2013 01:49:27,781 ERROR com.ibm.rational.rrdi.setup.steps.DeployCognosToWASStepService : com.ibm.rational.rrdi.setup.biserver.common.RRDIBIServerException: CRRRA2076E: Cannot deploy the Cognos components to the WebSphere application server.
com.ibm.rational.rrdi.setup.biserver.common.RRDIBIServerException: CRRRA2076E: Cannot deploy the Cognos components to the WebSphere application server.
 at com.ibm.rational.rrdi.setup.biserver.service.WasDeploymentService.executeWasCognosConfigurationStep3(WasDeploymentService.java:675)
 at com.ibm.rational.rrdi.setup.steps.DeployCognosToWASStepService.deployCognosStep4(DeployCognosToWASStepService.java:588)
 at com.ibm.rational.rrdi.setup.steps.DeployCognosToWASStepService.handleActions(DeployCognosToWASStepService.java:193)
 at com.ibm.rational.rrdi.setup.steps.AbstractStepService.doPost(AbstractStepService.java:222)
 at com.ibm.rational.rrdi.setup.steps.DeployCognosToWASStepService.doPost(DeployCognosToWASStepService.java:211)
 at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:176)
 at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:281)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
 at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
 at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126)
 at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
 at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
 at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:68)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
 at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:133)
 at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:154)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:336)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
 at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
 at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
 at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:309)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:736)

 

Thanks & Regards,

Tariq Ashraf

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.