Managing Pods and Accounts

Once you have more than one Pod, most of the housekeeping happens in the Pod picker at the top of the EPM Workbench sidebar. Credentials are managed from the Command Palette.

The Pod picker

Open the picker by clicking the row at the top of the sidebar. Pods are grouped by Domain, so a Domain with three Pods shows all three under one heading. A Pod with no Domain set appears under No Domain, and Library Folders appear under Library (see Library Folders).

Hover a Pod row and three actions appear on the right: Edit Pod, Archive Pod, and Delete Pod. Hover a Domain heading and you get Add Pod to this Domain, which opens the Add Pod editor with the Domain already filled in, and Rename Domain.

At the bottom of the picker are four actions that are always available: Add Pod…, Create New Library Folder, Unarchive Pod…, and Refresh. Use Refresh after you move Pod folders around on disk or bring in changes from version control.

Editing a Pod

Edit Pod opens the same editor as Add Pod…, filled in with the Pod’s current settings. You can change the Label, the Pod Icon, the EPM Pod URL, and the Connection (Service Account, OAuth, or Offline). The application name stays read-only: it comes from the connection, so run Test Connection again if you change the URL. See Install and first Pod for a walkthrough of each field.

Archiving a Pod

Archive Pod hides a Pod from the picker. Nothing on disk is touched: the Pod Folder, every rule in it, and its history all stay exactly where they are. Bring it back with Unarchive Pod… at the bottom of the picker, which lists your archived Pods with their Domain so you can pick one.

Archiving is the right choice for a Pod you rarely touch, such as last year’s test Pod, when you want the picker to stay short without losing anything.

Deleting a Pod

Delete Pod is the destructive one. It permanently deletes the Pod Folder and all of its files from disk, including rules you have not Pushed. A modal confirmation names the exact folder path and spells this out before anything happens. It cannot be undone, and the files do not go to the Recycle Bin or Trash.

Deleting a Pod never touches Oracle. The rules in Calculation Manager are unaffected.

Caution

If the Pod Folder is itself one of the folders open in your VS Code workspace, Delete refuses and tells you to remove it from the workspace first, then delete it from your file manager. Deleting a workspace root out from under VS Code would leave the workspace pointing at nothing.

Domains

A Domain is the grouping level above Pods, and it lines up with your Oracle identity domain: the test and production Pods that share one set of user accounts usually belong in one Domain. On disk, Pods live under their Domain folder inside your EPM Workbench Root. Rename Domain changes the display name only. The heading in the picker updates and every Pod under it follows, but no folders move.

A Domain can also carry a shared credential setup: a Service Account, or the OAuth client registration for that identity domain. When it does, each Pod under the Domain can select Inherit From Domain in its Service Account list instead of being configured one at a time. Re-point the Domain’s account later and every inheriting Pod follows.

Service Accounts

A Service Account is a named EPM username and password that Pods connect with. Run EPM Workbench: Manage Service Accounts from the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) to see them. The list shows how many Pods use each account, or marks it unused, so orphans are easy to spot.

Pick an account and you get two choices:

• Update password, which prompts for the new password and keeps the username.
• Delete, which removes the stored credential. If any Pods still reference the account, the confirmation names them and warns that those Pods will not connect until they are pointed at another account.

EPM Workbench: Add Service Account creates one. It asks for a name (the handle your Pods reference), the EPM username, and the password. You can test the credential against a Pod URL before saving. The password is stored securely by VS Code and is never shown again.

EPM accounts (OAuth)

If you sign in as yourself instead of through a shared account, run EPM Workbench: Manage EPM Accounts from the Command Palette. It lists the identity domains you are currently connected to. Select one and confirm to disconnect it.

Disconnecting removes the stored sign-in for that identity domain. Pods there fall back to their Service Account until you reconnect. See Connect with OAuth for the setup and the sign-in flow.