HP SM9.30 with HP UD 10.10 integration. (496 Views)
Reply
Frequent Advisor
Posts: 52
Registered: ‎05-04-2013
Message 1 of 11 (496 Views)

HP SM9.30 with HP UD 10.10 integration.

Experts,

 

I am doing UD integration with HP SM 9,30. THe application version of HP SM is 9,.32 and RTE is on 9.3.

THe CP 13.x is UD 10.10 is on.

I have done an OOB integration, i followed the steps mentioned in the installation guide. After the integration point is set and the SM push adapter jobs are run, the SM push for COmputer, network components are failing.

These are the only CITypes which are having values in UD. The error whic I am getting is something related to the dataflow probe postgre sql, error comitting the transaction something.

 

Has any1 faced similar errors in HP SM integration wtih UD? . Please guide.

 

Thank you

dev

HP Expert
Posts: 480
Registered: ‎02-15-2010
Message 2 of 11 (492 Views)

Re: HP SM9.30 with HP UD 10.10 integration.

Hi

 

Can you send the errror message you are getting ?

 

Thank you

Lisa

"HP Support
If you find that this post or any post resolves your issue, please make sure to mark it as an accepted solution."
Honored Contributor
Posts: 4,177
Registered: ‎07-21-2008
Message 3 of 11 (488 Views)

Re: HP SM9.30 with HP UD 10.10 integration.

Without the error message, it's hard to exactly say.

 

But here's what you can try.

 

First, modify the hostData TQL.  Open the TQL in the Modeling Studio in the Modeling environment and edit the ROOT CI.  Go to the Identity tab, and pick a handful of CIs to push (rather than trying ALL your hosts).

 

Then, in the Integration Studio in the Data Flow Management environment, edit your Integration point, and select Development Mode: true.  That will give you more information in the log file.

 

Then go ahead and run the integration job to push the hostData information into HPSM, and attach your log file.

Honored Contributor
Posts: 3,933
Registered: ‎07-13-2007
Message 4 of 11 (476 Views)

Re: HP SM9.30 with HP UD 10.10 integration.

9.32 Applications require the 9.32 RTE  (Running 9.32 applications on the 9.30 RTE is not supported).

Did you mean to say that you are on the 9.32 RTE and 9.30 Application release?

 

 

----------------------------------------------------
Kudos - what, where, how, and why
Want Good Answers? Ask Good Questions...
Frequent Advisor
Posts: 52
Registered: ‎05-04-2013
Message 5 of 11 (468 Views)

Re: HP SM9.30 with HP UD 10.10 integration.

All,

Thank you for the reply.

 

Attaching the initial log whcih I got when I ran the SM Data push jobs.

 

In the HPLN, we found a content pack for HP SM9.30 for integration wtih HP UD10.10. After applying the content pack, in the version information, i see

Application version as 9.32

RTE Version as 9.30.021

Content Release Installed is : UCMDB_ENHANCEMENT

 

Jacob,

I will try what you have pointed out.

 

HP Expert
Posts: 480
Registered: ‎02-15-2010
Message 6 of 11 (453 Views)

Re: HP SM9.30 with HP UD 10.10 integration.

Hi Jacob

 

The log didnt post.. Can you copy and paste part of it that mght show an error message

 

Thank you

LIsa

 

or at the below of the POST there is a place for attachments

 

Thank you

LIsa

"HP Support
If you find that this post or any post resolves your issue, please make sure to mark it as an accepted solution."
Frequent Advisor
Posts: 52
Registered: ‎05-04-2013
Message 7 of 11 (441 Views)

Re: HP SM9.30 with HP UD 10.10 integration.

Guess the attachments are not going thru.

 

************************************************

org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
 at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)
 at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886)
 at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
 at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555)
 at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403)
 at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:331)
 at org.apache.commons.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228)
 at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalStatementImpl$FlowControlUpdateExecuter.execute(CmdbDalStatementImpl.java:342)
 at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalStatementImpl$FlowControlUpdateExecuter.execute(CmdbDalStatementImpl.java:331)
 at com.mercury.topaz.cmdb.shared.manage.flowmanagement.api.FlowManager.execute(FlowManager.java:227)
 at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalStatementImpl.executeUpdate(CmdbDalStatementImpl.java:223)
 ... 75 more

*************************************************


org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
 at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)
 at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886)
 at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
 at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555)
 at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403)
 at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:331)
 at org.apache.commons.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228)
 at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalStatementImpl$FlowControlUpdateExecuter.execute(CmdbDalStatementImpl.java:342)
 at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalStatementImpl$FlowControlUpdateExecuter.execute(CmdbDalStatementImpl.java:331)
 at com.mercury.topaz.cmdb.shared.manage.flowmanagement.api.FlowManager.execute(FlowManager.java:227)
 at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalStatementImpl.executeUpdate(CmdbDalStatementImpl.java:223)
 ... 75 more


*************************************************

HP Expert
Posts: 480
Registered: ‎02-15-2010
Message 8 of 11 (435 Views)

Re: HP SM9.30 with HP UD 10.10 integration.

HI Ironman_3

 

Thank you for the error message . I am researching this now and will let you know what I find out

 

Thank you

LIsa

"HP Support
If you find that this post or any post resolves your issue, please make sure to mark it as an accepted solution."
Honored Contributor
Posts: 3,933
Registered: ‎07-13-2007
Message 9 of 11 (430 Views)

Re: HP SM9.30 with HP UD 10.10 integration.

[ Edited ]

Application version as 9.32

RTE Version as 9.30.021

 

You are using an unsupported application/RTE combination. Multiple 9.32 application components require the 9.32 RTE. Because of this, several SM components may not actually be functioning as designed.

 

From the 9.32 compatibility matrix:

Platform/Application Compatibility

The Service Manager client/server version should be no earlier than the applications version. For

example, if you are using the 9.32 applications, you must use a client/server[RTE] version of 9.32 or

greater; if you are using the 9.32 client/server[RTE], you can use the 7.11, 9.21, 9.30, 9.31, or 9.32

applications.

----------------------------------------------------
Kudos - what, where, how, and why
Want Good Answers? Ask Good Questions...
Frequent Advisor
Posts: 52
Registered: ‎05-04-2013
Message 10 of 11 (410 Views)

Re: HP SM9.30 with HP UD 10.10 integration.

Hi John,

 

The SM patch for UD integration was provided to us by HP itself.

 

Thank you

Dheeraj.

HP Expert
Posts: 480
Registered: ‎02-15-2010
Message 11 of 11 (404 Views)

Re: HP SM9.30 with HP UD 10.10 integration.

Hi

Do you have an old case # where they gave you the 9.32?

 

Thank you

LIsa

"HP Support
If you find that this post or any post resolves your issue, please make sure to mark it as an accepted solution."
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.