Repository > Log On / Log Off Greyed Out

[Mike]

Our version of XMetaL 5.1.1 + WebTop Connector has the options “Log On to Repository…” and “Log Off from Repository…” greyed out under the Repository menu. I don't see a way to change this, despite being logged into the Repository.

Does anyone else have this problem?

Reply

[ghkrause]

Mike,
This feature is not needed with every Component CMS. Our CMS offers auto-login and therefore no special account name or password needs to be entered by the user. Other setups could require a manual log-in step as well as allow explicit log-off and re-login. Our setup does not allow to play multiuser with a single PC session (I need to logout from my PC and use a different PC account to auto login to the CMS as a different user.)
So I see two issues:
a) Do you need to make login/logoff manually for your CMS?
b) How to hide the two menu items in case they are not needed due to auto-login.
For b I have no answer as I have not bothered 🙂

Reply

[Mike]

It's connecting to Documentum WebTop 5.3 SP6 and it connects manually through webtop in the Resource Manager pane. Often I need to switch between the admin and a normal user. The only other way is to close XMetaL and reopen.

Reply

[ghkrause]

You should talk to your Documentum specialist!
You need to update the code in
C:%%INSTALL FOLDER FOR XMAU%%CRCLjsCRCLToolbar.js

There is one routine to add the repository menu and anotherone that attaches code to it. I do not have the original code, my IT consultant gave me something without code attached to Login and Logout menu item and therefore it is grey as far as I can see.

What you want:
a) log off triggers Documentum to let your session end
b) log on to open a logon page with username and password

Does not seem to require a lot of code. But I am only a amateur programmer 🙂

Hope this helps to do the next step on your side!

Reply

[ghkrause]

Just to add some more insight:
C:%%INSTALL FOLDER FOR XMAU%%CRCLjsCRCLAdapterInterfaceBaseImpl.js
contains three routines for login, logout and logstatus:
// Login & logout

// success login([string userName], [string password])
CRCLAdapterInterfaceBaseImpl.prototype.login = function(userName, password) {
  // Return login success
  return 1;
}

// void logout()
CRCLAdapterInterfaceBaseImpl.prototype.logout = function() {
  // Do nada
}

// void getLoginStatus()
CRCLAdapterInterfaceBaseImpl.prototype.getLoginStatus = function() {
  return -1; // Unknown status – adapter will continue to work as if XM_QueryLoginStatus == false
}

These routines may need to be adopted and linked to menu items via the other JScript mentioned in my first answer.

Reply

[XMetaLOldTimer]

Hi Mike,

Currently, the XMetaL-Documentum connector doesn't support switching users during the same XMetaL session.  Doing so would likely result in unexpected behavior.  So, restarting XMetaL is the only way to do this.  I also urge you to close all documents before quiting and restarting XMetaL.

Can you describe what kind of operations you are doing from the admin login?

Regards,
Addam

Reply

[Mike]

The operations aren't any admin functions, but rather switching between users for checking permissions. Closing down open files makes sense, but it seems a bit clumsy to restart the program for a tittle of an operation. Thank you for verifying this is normal behavior and not anything wrong in our connections.

Reply

[Derek Read]

Please do not make any changes to files in the folder C:CRCL
This is core code that drives the “XMetaL Connector” system (the standardized system we provide to allow CMS vendors to create their own integrations with XMetaL) and should not be altered. Doing so could break the vendor's connector. XMetaL Support will also not support an installation of XMetaL Author that has been modified this way.

If you think there are problems with a portion of our code please submit a support case on the na.justsystems.com website detailing the issue so we can have a look and, if necessary, correct it in a future release. In some cases we might provide patches directly to CMS vendors (so you don't need to wait for our next version).

Reply

[Author]

Posts