Valued Contributor.. NDatta Valued Contributor..
Valued Contributor..
233 views

Portfolio status update taking too long

Jump to solution

Hi Experts,

We are facing an issue while trying to update portfolio status (seAssignment) for 'Computer' type assets. It's taking too long to complete.

Through trail and error, we have found out that it takes a long time if a PC record has multiple software installations associated to it (Component tab - AddOn link). Each of the associated softwares are getting updated(seAssignment same as that of the PC) and a workflow is also being triggered - "Update installations (portfolio items)".

Our end users are waiting for 30 mins while mass updating 100 records. If someone faced the same issue, please provide a suggestion or workaround. Is there anything that can be done from a record indexing standpoint?

Thanks,

ND

 

 

 

 

0 Likes
1 Solution

Accepted Solutions
Valued Contributor.. NDatta Valued Contributor..
Valued Contributor..

Re: Portfolio status update taking too long

Jump to solution

If anyone else is facing the same problem with a large number of component association, please refer to Mark's comment where he mentioned a method to identify installations without associating them to Portfolio items.

This can be achieved by checking 'amModel.bCompact' field under 'Software installation' tab. This will simply create only a record in 'amSoftInstall' table but not in the 'amPortfolio' table. Association to IT equipment can be tracked from 'amSoftInstall' table with correct customizations, but this will not show in the Components tab of the PC/Server record, hence reducing unnecessary background processing time.

Note: If any existing customizations exist for a software installation record using portfolio item fields, we won't be able to use those.

Thank you,

ND

0 Likes
7 Replies
Highlighted
Acclaimed Contributor.. Mark Cullen_1 Acclaimed Contributor..
Acclaimed Contributor..

Re: Portfolio status update taking too long

Jump to solution

Have you performed a diagnostic/repair for broken links against the database (see Designer application action)?  Component assignment is getting udpated via background agent which we cannot change without Micro Focus permission.  The workflow can be controlled by processing via server (APM service), based on execution group, instead of immediately (if this is the case).

0 Likes
Valued Contributor.. NDatta Valued Contributor..
Valued Contributor..

Re: Portfolio status update taking too long

Jump to solution

Hi Mark,

Thank you for your reply.

Here's what we got when we ran diagnostic for broken links -

2019/04/25 06:58:1.000 0 4 Starting verification: 'amPortfolio'
2019/04/25 06:58:1.000 0 4 LastID Diagnostic
2019/04/25 06:58:2.000 1 2 Current Last ID is: 676307425.
2019/04/25 06:58:2.000 1 2 Remaining capacity to reach the biggest possible ID is: 1471176222.
2019/04/25 06:58:2.000 0 4 Search for broken normal links
2019/04/25 06:58:41.000 1 2 Table 'Portfolio items (amPortfolio)': 5 incorrect record(s) for link 'Model (Model)'
2019/04/25 07:00:4.000 0 4 Search for broken typed links
2019/04/25 07:04:21.000 1 2 Table 'Workflow instances (amWfInstance)', link 'Workflow instance (DocRecord)': 14980 incorrect record(s) pointing to table 'Portfolio items (amPortfolio)'
2019/04/25 07:05:56.000 1 2 Table 'Messages (amMail)': 141 incorrect record(s) for link 'Referenced object (RefObject)'
2019/04/25 07:05:56.000 0 4 Search for bad denormalized fields: 'amPortfolio'
2019/04/25 07:05:56.000 0 4 Search incorrect overflow links
2019/04/25 07:06:2.000 1 2 Table 'Assets (amAsset)': 100 incorrect record(s) for link 'Portfolio item (PortfolioItem)'
2019/04/25 07:06:2.000 0 4 End of verification

 

Agreed on the backend agent, but the workflow I mentioned is a 'Database' type, OOTB workflow which gets triggered on seAssignment field change. It has an execeution group, which is enabled in APM and period is 10 minutes.

Thanks,

ND

0 Likes
Valued Contributor.. NDatta Valued Contributor..
Valued Contributor..

Re: Portfolio status update taking too long

Jump to solution

Also, to add some more context to the problem, we haven't faced this issue before. Recently we completed the SAM initiative successfully which brings in a lot of software installations, it's association to end points and hence greater number of installations associated, longer it takes to update a PC.

0 Likes
Acclaimed Contributor.. Mark Cullen_1 Acclaimed Contributor..
Acclaimed Contributor..

Re: Portfolio status update taking too long

Jump to solution

If a database repair has never been performed, or it has been awhile, then I would definitely let the Designer application action perform.  It may even make sense to perform against every table and not just amPortfolio.  Regardless whether this speeds up updates, broken links mean the foreign key no longer exists in related table and this just confuses the system.  Be careful with the Model link as this is a mandatory element and any update to portfolio item without it will generate an error (same goes for amAsset model link since it is the same).  I would handle model links manually to ones that actually exist.

This should not be the case, however, if there are any backend objects (ie. Oracle views, procedures, packages, package bodies, etc.), then these may need re-compiling after the repair.

My oob version of that workflow does not look like it is complete.  Please review.  If needed, then there is nothing wrong with adjusting for server side processing instead of immediate (this should speed up updates).  If not needed, then there is nothing wrong with turning off (set end date to yesterday or earlier, then stop and start APM service).

SAM is not my area of expertise, however, I thought there used to be a way to identify installations WITHOUT associating to assets.  This may have changed but something to look into.  Less components means less background processing needed (ie. agents, validity scripts, calculated fields, etc.).

After all this, if you don't see any improvement, I would contact Micro Focus Support directly for help.

Good luck.

Valued Contributor.. NDatta Valued Contributor..
Valued Contributor..

Re: Portfolio status update taking too long

Jump to solution

Thank you Mark for your suggestions.

Do you think a DBA should do this step vs AM Admin -

"This should not be the case, however, if there are any backend objects (ie. Oracle views, procedures, packages, package bodies, etc.), then these may need re-compiling after the repair."

Thanks,

ND

0 Likes
Acclaimed Contributor.. Mark Cullen_1 Acclaimed Contributor..
Acclaimed Contributor..

Re: Portfolio status update taking too long

Jump to solution

A DBA can help with this, however, the concern is only with any "custom" objects (sorry I didn't write this earlier).  If there are no "custom" backend objects, then no issue of doing anything.  if there are "custom" backend objects, then the person that created it/them can help, the DBA, or an AM Admin (unless there is real complexity, a recompile is a simple right-click mouse\Compile operation on object).

If you know of no other "system" requiring access to these "custom" backend objects, then there most likely are no "custom" backend objects.

I write "backend objects" becuase this means outside of AM where everything is done via Designer application.  This also means no AM application can be used...only actual database application (ie. SQLPlus, Embarcadero, etc.).

0 Likes
Valued Contributor.. NDatta Valued Contributor..
Valued Contributor..

Re: Portfolio status update taking too long

Jump to solution

If anyone else is facing the same problem with a large number of component association, please refer to Mark's comment where he mentioned a method to identify installations without associating them to Portfolio items.

This can be achieved by checking 'amModel.bCompact' field under 'Software installation' tab. This will simply create only a record in 'amSoftInstall' table but not in the 'amPortfolio' table. Association to IT equipment can be tracked from 'amSoftInstall' table with correct customizations, but this will not show in the Components tab of the PC/Server record, hence reducing unnecessary background processing time.

Note: If any existing customizations exist for a software installation record using portfolio item fields, we won't be able to use those.

Thank you,

ND

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.