Community in read only mode June 18 & 19
This community will be set in READ ONLY mode for a while on Tuesday June 18 into Wednesday June 19 while we import content and users from our Micro Focus Forums community site. MORE INFORMATION
Honored Contributor.. jeanbean Honored Contributor..
Honored Contributor..
1458 views

Database question

Jump to solution

Is it correct to say that Octane's database architecture is similar to ALM.NET in that there is one admin schema and then one schema per workspace instance? Is there also a shared-space schema? 

0 Likes
1 Solution

Accepted Solutions
idan_bauer1 Honored Contributor.
Honored Contributor.

Re: Database question

Jump to solution

There's some similarity but we took a different path.

We do have a site schema where we hold all of our information regarding what spaces are being handled by Octane.

A shared space / tenant equals a database schema.

A workspace is a logical partition within a schema which allows us to provide much better cross reporting / data sharing within individual workspaces. 

Tell us how we can make Octane better!
6 Replies
idan_bauer1 Honored Contributor.
Honored Contributor.

Re: Database question

Jump to solution

There's some similarity but we took a different path.

We do have a site schema where we hold all of our information regarding what spaces are being handled by Octane.

A shared space / tenant equals a database schema.

A workspace is a logical partition within a schema which allows us to provide much better cross reporting / data sharing within individual workspaces. 

Tell us how we can make Octane better!
Micro Focus Expert
Micro Focus Expert

Re: Database question

Jump to solution

If this question comes from the desire to access the database(s) directly, then we strongly recommend avoiding this! For all your reporting purposes and more please use REST API - while database schema may change, REST API will always be backward compatible so your integration or reporting code will continue working even after major version upgrade.

Honored Contributor.. jeanbean Honored Contributor..
Honored Contributor..

Re: Database question

Jump to solution

Leobor, your points are well taken. Yes, this question was from a seasoned ALM admin who I'm sure has needed to meet all kinds of reporting requests from his App Dev teams over the years. Idan, thanks the description of how things work.

0 Likes
Highlighted
Contributor.. iViLouisT Contributor..
Contributor..

Re: Database question

Jump to solution
Hi Leobor,
 
How would you reccommend handing reporting when data needs to be accessed from more than 1 URI. For example, if we want to find all related defects that are attached to one another by a parent defets status. In this case we need to use the /defects URI and the /relations URI and establish their relationships. In SQL we can join the WORK_ITEM and RELATION table on a common ID but this becomes more difficult to do with a GET request on a URI. Do you have any reccomendations on the best way to handle these types of reporting needs? I have outlined a potential workflow for using the REST API below. Do you see any opportunites for improvements? Also, does Octane have a DB refrence guide like ALM.NET does?
 
 
Step 1: GET request to gather all blocked defects (or all defects and we can validate blocked later).
 
.../api/shared_spaces/3002/workspaces/1003/defects?query=“blocked EQ true” 
 
Step 2: GET request to get all links for “work_items” (has defects, epics, features and user stories) with a filter on both entities being defects, side1 is trace to and side 2 is trace from.
 
.../api/shared_spaces/3002/workspaces/1003/relations?query=“relation_name EQ ^work_item_to_work_item^;side1_type EQ ^defect^;side2_type EQ ^defect^”
 
Step 3: Loop through all of the blocked defects and validate their relationship against non blocked defects.
 
Thanks for your time.
-Louis
Tags (3)
Micro Focus Expert
Micro Focus Expert

Re: Database question

Jump to solution

@iViLouisT you should avoid using relations api, it's too complicated to use and is rearelly actually needed.
In your specific case, instead of issuing two quries, u can use single query to bring all items related to blocked items.

For example like this

.../api/shared_spaces/1001/workspaces/1002/work_items?fields=id&limit=10&offset=0&query="subtype='defect';linked_items1={(blocked=true)}"
 
This query will bring any defect which is lined to any other work_item via the linked_items1 relation / reference field where the linked work_item is blocked.
 
Micro Focus Expert
Micro Focus Expert

Re: Database question

Jump to solution

The recommended way to report off of Octane is via Odata enabled products such as Excel, PowerBI and more. See more at https://admhelp.microfocus.com/octane/en/latest/Online/Content/API/articles_OData_API.htm

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.