2. Discovery
• Maxl Overview
• Benefits of Maxl
• Maxl Documentation
• Maxl Strategies
• Examples
• Growing On The Basics
• Closing
3. Maxl Overview
• Scripting language
• Included with Essbase
• Automates repetitive tasks
• Executed by calling essmsh
• Scripts not dependent on OS
4. Benefits Of Maxl
• Limited learning curve
• Minimal cost to implement/maintain
• Small footprint
• Executed locally or on server
• Organized documentation
• OS independent
• Readable to all levels of expertise
5. Maxl Documentation
• Located in the EPM Documentation
library at download.oracle.com
• See the Technical Reference in the
Essbase category
• Documentation uses a railroad approach
and is very easy to understand
6. Common Uses
• Duplicate applications & databases
• Change security
• Load data
• Create users
• Create partitions
• Export data
• Build outlines
7. Maxl Strategies
Building scripts effectively and organized, leads to lower cost of ownership
and fewer errors
• Parameterized when applicable
• Use spooling and timestamping
• Develop common structure to all scripts
• Use variables in code header
• Nest common routines
• Error trap scripts
• Comment, comment, comment
8. Parameterize Scripts
Common actions invoked can reuse code and decrease the effort of
changing common practices
Contents of file: export.msh
spool on to export.out;
login $1 $2 on $3;
export database $4.$5 level0 data to server data_file ‘export.txt’
spool off;
exit;
Command line:
essmsh.exe export.msh kyle reddog01 localhost sample basic
9. Spooling and Time Stamping
• Spooling Maxl Results
• Time stamp each execution
• Message level
10. Use Common Code Structure
• Define logical sections of code
• Line break scripts to make the scripts
more readable, both on screen and in
print
• Have all scripts follow consistency
Benefits
• Reduces development time
• Reduces break-fix time
• Reduces the doc requirements
11. Use variables
• Keep variables in one location
• Increases the opportunity to reuse
common scripts
• Improves readability
12. Nest Common Routines
• Nesting code whenever possible
• Reduces development time
• Reduces time required for change
requests
14. Comment Code
It takes seconds to make comments in scripts as to the what and why.
It takes hours to figure out what you were thinking 6 months later!
If comments are clear and informative, it can act as the
documentation
Comments in code can be performed by encapsulating the comments in /**/
/* comment */
15. Build On The Basics
• View the results with a website
• Add email component if failure occurs
• Notify users when processes complete
17. Drive Website From Maxl Logs
• Use error trapping and branching
• Spool errors and status
• ASP, PHP, or .NET can traverse folders for
error logs and status
18. Trigger Notification
• Integrate with error trapping and
branching
• Use shell to execute external mail
application
login $1 $2;
……….
iferror 'dimbuildFailed';
……….
exit;
define label 'dimbuildFailed';
shell …
exit;
20. WWW.IN2HYPERION.COM
• A society of Hyperion experts that dedicate their
time to drive strategic change
• Not linked to or owned by a consulting organization
• A resource of valuable content
• Initiated in March of ‘09
• Attract nearly 150 visitors every day
• 20,000 visitors in 6 months
Become a member of the online community - go to
www.in2hyperion.com and sign up for the newlestter!
