License Manager Inquiry

PIVOTAL CRM FORUM
Free Pivotal CRM advice from experts

Welcome, Guest. Please login or register.
Did you miss your activation email?
September 10, 2010, 02:01:42 AM

A reputed Pivotal CRM consultant starts a Pivotal CRM blog www.pivotalcrm.info

2147 Posts in 649 Topics by 1169 Members
Latest Member: Errotoush

Hi all, we will be implementing License Manager 5.9 SP3 in the next little while. I've heard that when the License Manger first became available there were a lot of issue with it (locking users out) but now that a grace period has been put in, it's much more stable. I'm wondering if anyone has any lessons learn or things for us to watch out for as we prepare for this install. Thanks in advance.

Betty

Always use a replicate if you intend to restore a BM as the backup/Restore process will crash the PLM.
The replicate/restore allow the GUID to be respawned.
If 2 databases have the same GUID then the PLM cannot process license.

Jérôme BERGES
Carmis
France

We just upgraded to 5.9 from 5.7 and in the past we have always just replicated the bm from dev to prod for our integration.
Now when we do this it appears to also replicate the GUID over to prod, which causes the problem you mention.

Is there a different way we are suppose to move our changes from dev to prod?

Hi,

We always upgrade our offline system from development using Transporter, but if you wish to replicate BM, you can do it:
You just need to have the same Database Id and the same users which have a licenses in the Development BM and in the target BM (not sure which BM you means: Production directly or Offline).

Complete the following steps:
1) Open Enterprise Manager, ensure that you have the same license files for both systems, for example Customization_0001
2) Open Database tab on Development system for example (I assume that Development system have a valid users with assigned licenses)
3) Copy Database Id value, for example 11abcabc-cc11-1111-b111-1c1e11111abc
4) Open SQL Editor, connect to your target database (Production or Offline)
5) Execute this Query (for example, if you have Oracle): UPDATE BM.RSYS_SYSTEM_FLAGS SET RN_VALUE = '11abcabc-cc11-1111-b111-1c1e11111abc' WHERE RN_FLAG = 'DatabaseId'.
6) Commit your changes

Thats all.

Now you can replicate your BM from Development environment to the target.

Hope it helps,
Sergey

Thank you Serk, I will give this a try.