Deployment with encrypted Maxl files

Question

Hi All,
I'd like to know how encrypted maxl files work if I need to deploy them to different servers. This is, I create the maxl files to automate everytihng and I encrypt them in a test server. After deployment to a different production server, are the public/private keys going to work with no problem? Or I should re-encryp everything with new keys generated in the production server?
Thanks!

Answer 1

You need to create new
For Assistance you can use below Comments
You need to use the MaxL encryption tool to do this. The passwords stored in the MaxL Scripts can be encrypted from Version of Essbase 9.3 or higher.
To Encrypt the Scripts:
a) The following MaxL Shell invocation generates a public-private key pair that you can use to encrypt a MaxL script.
essmsh -gk
b) The following MaxL Shell invocation encrypts the input MaxL script, obscuring user name and password, and changing the file extension to .mxls.
essmsh -E scriptname.mxl PUBLIC-KEY
c) The following MaxL Shell invocation decrypts and executes the MaxL script.
essmsh -D scriptname.mxls PRIVATE-KEY
STEP 1: In the command prompt type:
C:\>essmsh -gk
STEP 2: In the command prompt, execute as below:
C:\>essmsh -E D:\Hyperion\MScript.mxl 29287,1495101497
Generates a Encrypted MaxL script file "MScript.mxls" based on the original MaxL script "MScript.mxl" in the location "D:\Hyperion".
STEP 3: Execute Encrypted MaxL script MScript.mxls
C:\>essmsh -D D:\Hyperion\MScript.mxls 1165863655,1495101497
Essbase MaxL Shell - Release 9.3.1 (ESB9.3.1.0.0B181)
Copyright (c) 2000, 2007, Oracle and/or its affiliates.
All rights reserved.
MAXL> login $key 8432115901043363023058112802217170696731 $key 46195519111827550
39099976036415811280221 on localhost;
Hope this helps