Change Application Maintenance Mode via Command Line

Patch Set Update: 11.1.2.1.600 offers a welcome utility

If you have ever tried to automate the state of a Hyperion Planning applications’ Application Maintenance Mode, you found it difficult. The only way to accomplish this was to run a SQL Update on the repository table, and for this to take effect, the Planning service had to be restarted.

If you are unfamiliar with the Application Maintenance Mode setting, it is found in Administration/Application/Settings menu. Changing this setting from All Users to Administrators, locks out planners from using the application. It is typically used when changes are made to hierarchies, web forms, system settings, security, and during deploys, to keep users out while changes are being introduced.

Patch Set 11.1.2.1.600, and the corresponding patch release for 11.1.2.2, introduces a new utility that allows administrators to change this setting from a command line. YEAH, it can now be automated without restarting Planning!

Without Further Adieu

MaintenanceMode.cmd (or MaintenanceMode.sh in UNIX) is found in the <EPM_PLANNING_INSTANCE> directory. The following parameters can be passed, separated by commas.

  • /A=app – Application name (required)
  • /U=user – Name of the administrator executing the utility (required)
  • /P=password – The administrator’s password (required)
  • /LL=loginLevel – [ALL_USERS|ADMINISTRATORS|OWNER]

ALL_USERS – All users can log on or continue working with the application.

ADMINISTRATORS – Only other administrators can log on. Other users are forced off and prevented from logging on until the parameter is reset to ALL_USERS.

OWNER – Only the application owner can log on. All other users are prevented from logging on. If they are currently logged on, they are forced off the system until the option is reset to All_USERS or ADMINISTRATORS. Only the application owner can restrict other administrators from using the application.

  • /DEBUG=[true|false] – Specify whether to run the utility in debug mode. The default is false. (optional)
  • /HELP=Y – View the utility syntax online (optional)

Example

MaintenanceMode.cmd /A=app1,/U=admin,/P=password,/LL=ADMINISTRATORS

MaintenanceMode.cmd /A=app1,/U=admin,/P=password,/LL=ALL_USERS

 




Kscope 13 Abstract Submissions Are Open

Kscope13 article submission is open.  I will be spearheading the Planning track at Kscope13.  Last year was my first trip to the conference, and I was amazed at the talent and breadth of speakers.  Jake Turrell did an unbelievable job owning the Planning track last year.  He was involved in the release of Developing Essbase Applications (available in hardback and Kindle versions).

I am going to lean on him for help to try to make this year’s event even better.  The most important part of the conference starts now, and we need your help.  Submit an abstract.  Only a brief description is required at this point.  It takes less than 30 minutes.  We don’t need a full presentation now; that comes later.  If you are nervous about speaking, we will have a number of helpful presentations on what to expect and how to make your presentation the most effective possible.  If you do it once, I promise you will be hooked.

What you will need to submit

  1. Personal bio
  2. Presentation title
  3. Presentation description
  4. Presentation summary no more than 100 words
  5. Benefits of attending your presentation

To submit, go to the Kscope13 Abstract Submission Site.  Creating an account takes only a minute.  Once you are logged in, input your bio and click the “Add Abstract” button.  Use the information above to fill out the form.  Select the related technology, the type of presentation, and you are done!  The Kcope13 Content page has suggestions that will help you get your submission to stand out.

Submissions are open now to October 15th. 




Website Updates Mean Improved Viewer Experience For You

We have introduced a few changes to the site, and hope they add additional value and ease of use.

First, we have upgraded the blog engine to the newest version to eliminate some issues the site is experiencing with newer browsers.  We have received feedback that some of the functions aren’t working as expected, and these changes should fix the issues viewers are having.

Secondly, the navigation bar on the right has been updated.  New articles will be assigned to experience level, which will help those in with different experiences find articles more applicable to them.  Our twitter feed will also be streamed near the bottom.  The plan is to tweet more information; things that don’t necessarily constitute an article, but is valuable information.  If you aren’t following us on twitter, you will find it valuable.  Expect bug announcements, tips, interesting finds in new versions, and the other topics that will be applicable.




Article Now Available in InVision

Josh Forrest and I presented at last year’s Collaborate conference.  Along with that presentation, we wrote a white paper on the implementation of Hyperion Planning.  This paper included process of selecting a vendor, the project goals, requirements gathering, project methodology, and even the lessons learned once the implementation was completed.

The editors of OAUG asked us if they could publish the article in the summer edition, which was released this week.  The article was written closely with Abercrombie & Fitch and represents the process from the business, not from the consulting services, point of view.

The article can be downloaded here at www.oaug.org.  Access to the article requires free registration.




BUG REPORT – Shared Members Security in EPMA

Oracle has confirmed a bug related to the deployment of security with a planning application maintained in EPMA in version 11.1.2.x.  When the Shared Members checkbox is selected in an EPMA deployment of a Planning application, it ignores this option.  Even if the Shared Members box is checked, the user still only gets access to Ohio Region, and not the children, in the example below.   Oracle is currently working on a patch.

What Does Checking Shared Members Do?

By default, any member that is a shared member under a parent with security, it gets excluded.  For example, if the security for Ohio Region is set to @IDESCENDANTS with READ access, the three members below Ohio Region would have no access.
– Ohio Region
– Columbus (Shared)
– Cincinnati (Shared)
– Cleveland (Shared)

The filter that gets pushed to Essbase would look something like this.

@REMOVE(@IDESCENDANTS(“Ohio Region”),@SHARE(@IDESCENDANTS(“Ohio Region”)))

When the shared members are checked, it tells Hyperion that you want to include shared members in the security.  The same example above, with shared members selected, would give users access to all 3 members.  The filter that gets pushed to Essbase would then look like this.

@IDESCENDANTS(“Ohio Region”)

The Workaround

The workaround for this is to deploy the hierarchies from EPMA, and Refresh the database (security only) with Shared Members selected from Hyperion Planning.

When a patch is released, we will release the details.