Personalizations in M3 – Manager

A few days ago I wrote about Personlizations in M3. What I forgot to mention is the Personalization Manager in M3. It’s an admin tool for managing personlizations for users and groups and for different servers installations. This is the tool to user for moving personlizations around, for example from a test environment to a production environment.

10 thoughts on “Personalizations in M3 – Manager

  1. yamakake

    This is great info! ๐Ÿ™‚ Would you be able to advise where the default location is for the scripts and personalizations is in LSO10? I got into the tool, but it asked for the folder containing the personalizations, which I didn’t know.

    1. karinpb Post author

      You need to find the File Folder for M3 UI Adapter in the grid. The default name for the root folder is mne_data and then you check the folders in there. One is Customizations and I think Scripts is just Scripts. The folder name was entered as part of the installation of M3 UI Adapter. Becuase I’m assuming you are on a later version of Smart Office with the M3 UI Adapter in the Grid and not MNE on WebSphere.

      The property is visible from the Grid Management pages. The name of the property is File Root Path and in my environment (10.0.5) the navigation path to here is: Configuration Manager – Applications – Application M3 UI Adapter – Application Properties.

      You need to know your way around in the Grid management pages to be able to find it.

      If the setting is blank the files will be stored in the WEB-INF folder in the WAR-file.

      1. Anders Lundh

        I’ve tested the “Personalization Manager” but I’m not sure if I missunderstand you or not….
        You said it could be used for “moving personalizations around”.
        I’ve therefore created a script in my own user, deployed it to LSO and tested it.
        Then I moved it to another user with the “Personalization Manager” and when he started his LSO he had the script in LSO. ๐Ÿ™‚
        However when deleting the scrip from him in the “Personalization Manager” it does not disaper from his user, so next time he starts LSO he still has the script on his M3 screen.
        NB!! It disaper from the “Personalization Manager” but not from his LSO.
        Since the delete function exist in the “Personalization Manager” I tought I also could “take away scripts” from user without having to log into to each and evry user.

  2. karinpb Post author

    Hi Anders,
    Thank you for bringing this to my attention. I would expect the tool to be able to delete as well. What version were you using? Did you get any errors in the log?

    It is always best to report any issue to extreme support.

    1. Anders Lundh

      Hi Karin
      Sorry for missing what version I’m using.
      I’m on LSO version 10.0.5 and M3 BE 14.1.2. No errors found in the log file.
      Before reporting anything to extreme support I wanted to check if you or anybody else have had the same experience with the Personalization Manager, but of course I’ll report if an error.

      1. karinpb Post author

        Just make sure that you have refreshed the cache on the MUA server. You can do that via an admin command (Check the Net extension manager under Administration tools) or by restarting MUA. Personalizations are also cached on the client but I’m assuming he logged off but pehaps you did not clear the server cache?

  3. Anders Lundh

    Hi again Karin
    I’d forgotten to clear the MNE-server. Thanks for the tips. ๐Ÿ™‚
    After doing that it works perfect to copy & delete personalizations between users/roles from the Personalization Manager. Rellay great tool for deploying scripts, etc.

  4. Heiko

    Hi Karin,
    I got a question how to manage localization (=language support) in personalizations. We have a perfect solution for mashups, but what about i.e. conditional styles where descriptions are added to a status code etc. ?

    1. karinpb Post author

      There is no built in language support in personalizations. Please ask the customer to report it as a requirenment via Extreme support. The workaround would be to use different roles and connect different conditional styles.

Comments are closed.