{"id":4047,"date":"2023-08-16T17:33:35","date_gmt":"2023-08-16T17:33:35","guid":{"rendered":"https:\/\/quebit.com\/askquebit\/?p=4047"},"modified":"2026-01-20T16:08:32","modified_gmt":"2026-01-20T16:08:32","slug":"canceling-threads-and-disconnecting-users-in-planning-analytics","status":"publish","type":"post","link":"https:\/\/quebit.com\/askquebit\/canceling-threads-and-disconnecting-users-in-planning-analytics\/","title":{"rendered":"How Do I Cancel Threads and Disconnect Users in Planning Analytics?"},"content":{"rendered":"

Canceling Threads and Disconnecting Users in Planning Analytics <\/strong><\/p>\n

If you are new to IBM Planning Analytics or particularly to administrating with Planning Analytics Workspace, then the following information may be of interest. Keep in mind that we\u2019re focusing here on just a few administrative tasks and functions, while there are plenty of others you\u2019ll want to explore.<\/p>\n

Assuming you\u2019re running Planning Analytics Local<\/u>, let\u2019s verify which version of Planning Analytics Workspace<\/strong> you are using (if you are running in the IBM Cloud, most likely the version is current – or close). The reason for doing this is because the look and feel of the workspace may vary depending upon which version you are using. In addition, some newer features may not be available in older versions and, occasionally, some features may be decommissioned in favor of others in later versions of the software (it also helpful to know your version when referring to IBM documentation or submitting a support request to a support team).<\/p>\n

    \n
  1. Launch the PAW website<\/li>\n
  2. Click “About IBM Planning Analytics<\/strong>” (shown below):\"\"<\/li>\n
  3. The exact version (for example\u00a00.89<\/strong>) is shown at the lower-right corner:\"\"<\/li>\n<\/ol>\n

    Upgrading<\/strong><\/p>\n

    It goes without saying that, if you find that you are more than a few versions behind, you should consider upgrading your Planning Analytics Workspace. Why? Because IBM is continually developing the product, adding new features and reported \u201cbug fixes\u201d typically are included with each new version. Don\u2019t be concerned that an upgrade will require your team to be retrained, as typically \u201cmaterial functionalities\u201d will continue to work in the same manner allowing you to learn to use any new features as time permits (in fact, when some new features are introduced to\u00a0Planning Analytics Workspace, you can choose to enable or disable those features in your environment). Tight schedule? Upgrading PAW is not a huge undertaking, if best practices are followed, however, you should plan on performing the upgrade during a system maintenance window because services will need to be stopped (and PAW will be unavailable until restarted).<\/p>\n

    Starting Point<\/strong><\/p>\n

    First, it\u2019s important to understand how Planning Analytics Workspace uses security objects, specifically roles, to provide or limit what a user or \u201cclient\u201d can perform. There are four roles available in\u00a0Planning Analytics Workspace, with the \u201cdefault\u201d role being the\u00a0Analyst<\/strong> role. You can learn more about PAW roles here<\/a>. To perform administrative tasks, you\u2019ll need to be \u201cassigned\u201d the Administrator role. By default, the administrator role is assigned to the first user in your organization’s\u00a0Planning Analytics Workspace\u00a0account, but of course you can have multiple users assigned to the administrator role. Not sure if you are an administrator? Here is a quick way to find out: you access the Administration page from the Administration tile on the Planning Analytics Workspace home page. If you are not an administrator, you will not see the Administration tile on the Planning Analytics Workspace home page.<\/p>\n

    Planning Analytics Admin vs Planning Analytics Workspace Admin<\/strong><\/p>\n

    To be clear, you can run Planning Analytics (PA) without Planning Analytics Workspace (PAW) and therefore there is<\/em> a difference between a user who has admin access in PA versus a user with admin access in PAW (note that a user can have both but might not). You can use\u00a0Planning Analytics\u00a0administration clients to administer your data and models, while a Planning Analytics Workspace administration client can be responsible for managing PAW users and assets, such as a book, view, folder,\u00a0modeling workbench,\u00a0application, or plan). As previously noted, workspace automatically assigns the very first account that logs in<\/em> as the \u201cPAW Admin account\u201d, then the user of that account can assign the PAW admin role to any existing PAW user through the Administration panel (and then clicking on \u201cUsers and Groups\u201d). From there, you check\/select the user and then select the \u201cAdministrator\u201d role from the drop-down list. Multiple users should have PAW Admin privileges, but you should limit and monitor who you grant this access to. The default PAW user role for all users is Analyst<\/strong>.<\/p>\n

    Moving On<\/strong><\/p>\n

    Once you have confirmed that you are a Planning Analytics Workspace Administrator <\/em>(not a PA Administrator), you can move on to trying out some of your \u201cadministrator abilities\u201d, such as monitoring and managing activity. Activity within a Planning Analytics database is typically tracked and measured with \u201cthreads\u201d. A thread<\/em> is\u00a0a request to the Planning Analytics server to do some work; typically, a query such as a user opening a view of data, or it could be a TurboIntegrator process performing some sort of processing, rule calculation refreshes, or even a user logging in, etc. Users active within Planning Analytics Workspace also show as threads.<\/p>\n

    Threads are identified with an ID, Type (user, worker, chore, system) and Name. Thread IDs are (system assigned) unique numeric IDs for each thread. The Thread Name is the actual name of the \u201cuser\u201d who initiated the thread (in some cases it may be a Planning Analytics initiated request such as \u201cPseudo\u201d or other name).<\/p>\n

    Threads will \u201cpass through\u201d various states, such as Idle, Wait, Running, Commit, Rollback and Login. Each state has a different meaning:<\/p>\n