This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Dimensions Upgrade to 14.6 APLS config

Hello,

So I've hit a snag when attempting to follow the Microfocus guide for configuring Dimensions CM to use the APLS software.  Following this guide https://admhelp.microfocus.com/dimensionscm/en/14.6/online_help/Content/InstallConfigure/apls-licensing.htm, the second sub-step under Step 5 doesn't appear achievable since there are no active user licenses to log into Dimensions with to add the APLS admin user.

To assign named licenses automatically:

  1. On a licensed Dimensions CM server, edit the dm.cfg configuration file to add this variable:

    Copy code
    DM_LICENSE_USER Admin
  2. As the Dimensions CM administrator, register the DM_LICENSE_USER password in the dmpasswd utility:

    Copy code
    dmpasswd DM_LICENSE_USER –add

To assign named licenses manually in the APLS web interface, see the AutoPass License Server help.

When attempting to use dmpasswd utility the login prompt shows up then disappears upon login attempt.  Honestly, the documentation to make the switch to APLS software is not too descriptive and I'm kind of at my wit's end with trying to get this to work.  Can someone provide a simple guide to assign a license manually for Dimensions CM in APLS? Or even better, if someone else has made this switch from SLM to APLS, can you please provide a simple step-by-step to get this working?

Thank you

Grant Stevens

Parents
  • 0

    Thank you Richard. But don't we need an active account to be able to access the dmcli?  With no user licenses assigned, how am I supposed to authenticate to add the APLS user to Dimensions with dmpasswd utility?

    Thanks

    Grant

  • 0 in reply to 

    D'oh, my mistake was trying to use the dmcli, worked with cmd.  Sometimes it takes someone not pointing out what your wrong to actually see what your doing wrong.

  • 0   in reply to 

    Let me know how you get on and if you need any more help 

  • 0 in reply to   

    Thank you Richard!  Once I add the admin user, should I be able to log in to Dimensions admin console with that Admin user?

  • 0   in reply to 

    That admin user is specific to APLS. You won't be able to login to Dimensions CM as that user. 

    I would recommend restarting the Dimensions CM listener to make sure it picks up the new password you've registered. The registry.dat file is read when the listener is first started.

    You should then be able to connect to Dimensions CM as the standard admin user you specified during install normally dmsys (or any user you've used with CM before) as long as you've added a valid license to APLS. 

Reply
  • 0   in reply to 

    That admin user is specific to APLS. You won't be able to login to Dimensions CM as that user. 

    I would recommend restarting the Dimensions CM listener to make sure it picks up the new password you've registered. The registry.dat file is read when the listener is first started.

    You should then be able to connect to Dimensions CM as the standard admin user you specified during install normally dmsys (or any user you've used with CM before) as long as you've added a valid license to APLS. 

Children
  • 0 in reply to   

    Thank you.  For some weird reason, I've never been able to authenticate to Dimensions CM using the dmsys account.  I use it to create new projects, but that's the only place the auth works.  Perhaps this is due to our using AD for auth?  Note, I inherited this thing a few years back, and my main admin responsibilities lie with Splunk, so I've not dug too deeply into the inner guts of Dimensions. 

    Attempting to login using my AD account returns this error:

  • 0   in reply to 

    I mentioned earlier, is APLS installed on the same server as Dimensions CM? If it is you can avoid the need to install a valid certificate by using the following in the server dm.cfg file:

    DM_LICENSE https://localhost:5814/autopass

    Rather than using the 'real' hostname as that would require a valid certificate to have been installed. As with any change to dm.cfg you will need to restart the Dimensions CM listener. 

  • 0 in reply to   

    Okay, yes, I had the hostname being used for that setting.  Updated, restart of DM listener, attempted login using my personal admin account:

    Log In Failure: Client named user identifier is invalid for named feature '101450:1' checkout request. Could not connect to database hudtest@dmtest. Please check DB name and DB connection, and that the remote listener is running.

    Backtrack for a sec to the dmsys account, in order to log in to Dimensions with that account, is there a setting in the dm.cfg that would allow for me to login with that as a local account while also maintaining LDAP auth?

  • 0   in reply to 

    On the error, had you installed a valid license in APLS? Can you try a second time? I have seen cases of the very first connect attempt failing but subsequent attempts work (in the background that initial attempt registers the product in APLS which is why that happens). 

    Does dmsys exist only as a local OS user? Unfortunately once you configure Dimensions CM to authenticate through LDAP it will use that for all users. 

  • 0 in reply to   

    Unfortunately yes, the dmsys user only exists as local os user.  For the license, yes as well, it has been installed in APLS.  Still no dice with the auth though.

    The License type is Perpetual, with 5 licenses set aside for our test environment.  Capacity unit of measure is "Named User".

  • 0   in reply to 

    Perhaps it's easier if we get on a call tomorrow and work through this? I'll drop you an email Grant. It's late here in the UK now so hopefully tomorrow is ok

  • 0 in reply to   

    That works perfect.  Thank you so much Richard, you have been immensely helpful!  Can we set up a webex perhaps?