All topics
53 / 55
Adminadvanced

WLST Scripting for OBIEE/OAS Administration

Explain how the WebLogic Scripting Tool (WLST) is used to automate common OBIEE/OAS administrative tasks that would otherwise require manual console operations.

OBIEE runs inside a WebLogic domain, so WLST — the WebLogic Scripting Tool — is how its administration is automated.

It's like the difference between manually flipping switches on a factory control panel every single shift versus writing a programmable control sequence that reliably performs the exact same startup checklist every time, and that can be reviewed, tested, and improved as a document rather than re-learned from memory by whoever happens to be on shift.

Key Concepts

1
What it replaces. Clicking through Fusion Middleware Control and the WebLogic console, identically, every time.
2
    deploy an RPD or a BAR file
    start and stop managed servers
    change configuration settings
    read component status
    manage users and groups in the embedded LDAP
3
A deployment as a script.
    connect('weblogic', password, 't3://host:7001')
    downloadRepository(...)
    uploadRepository(name='/path/new.rpd', password=rpdPassword)
    restartBIComponent(...)
    disconnect()
4
Jython, so it is ordinary scripting with loops, conditions and error handling around those calls.
5
Why this matters beyond convenience.Repeatability. A deployment done by hand is done slightly differently each time, and the difference is found later. A script does the same thing in every environment.
6
Automation. A pipeline can deploy an RPD after a build, which is the prerequisite for any CI practice around BI.
7
Auditability. The script is the record of what was done, in version control, rather than somebody's memory of which checkboxes they ticked.
8
Two modes. Online, connected to a running server, for operations against a live domain. Offline, against the domain's configuration files, for changes made while the server is stopped.
9
The practical cautions.Credentials. A script needs the WebLogic password and often the RPD password. Embedding them in the file is the obvious mistake; a configuration file with restricted permissions, or a secret store, is the answer.
10
Version differences. WLST commands for the BI components have changed between releases, so a script written for one version may not run on the next. That is worth knowing before an upgrade.
11
What it does not cover. Content — analyses and dashboards — is catalog work, handled by Catalog Manager and its own command-line tools. WLST administers the platform, not what is on it.
12
What the interviewer is probing.1. "What is WLST used for here?" Probing: the purpose. Stalls: "Scripting." Moves up: automating WebLogic and BI domain administration — starting and stopping components, deploying, and changing configuration repeatably.
13
2. "Why script rather than use the console?" Probing: the argument. Stalls: "Speed." *Moves up:* repeatability and auditability — a documented console procedure drifts between environments, a script does not.
14
3. "What would you script first?" Probing: the practical priority. Stalls: "Everything." Moves up: the start and stop sequence and the RPD and catalog deployment, since those are done most often and most error-prone by hand.
15
4. "What is the caution with scripted configuration changes?" Probing: the discipline. Stalls: "None." Moves up: they apply instantly across the domain, so they belong in version control and should be tested in a lower environment first.
Use cases:wlstautomationadministration