Configuration Manager for Focal Point

My team is using Configuration Manager to help us map data from a custom Focal Point workspace into Insight. I love Configuration Manager and they way it easily generates the XDC file for us and assists in the mappings, but in this case it seems to be missing a key piece.

When I generate the XDC file and attempt to map my data from FP modules into Insight tables, the Workspace data is unavailable. Without this, how am I supposed to map the FP Workspace into the RTC project? Since Project is kind of the foundation of Insight, I'm not quite sure how to proceed. The out of the box focalpoint.xdc file has a Projects connection, but I'm not sure how to get one in my generated XDC file. Any help would be great.

Jackie some clarification to understand where you are at.
1- You have defined a new resource group in the xdc file which has as a url format
http://<server>/fp/resources/workspaces/<workspaceid>

2- You were able to define new resources for this resource group
3- The problem you are experiencing is in data manager when you want to create the query for some fact build for example, when you select this newly created resource from the FP xml ODBC data source you get no data back hence you can not design a fact build

Our Focal Point team has several custom workspaces they have developed, and have requested that we report on these in Insight. We have defined a connection to our FP server in Configuration Manager which auto-generated an XDC file for us. We are using this to custom map our Focal Point workspace into Insight, with the URL as mentioned: http://<server>/fp/resources/workspaces/<workspaceid>

We can define resources and map these to create an ETL for our project, and this is working as expected. What we're missing is the definition of the Workspace itself. We were expecting to map the Workspace itself into a Project in Insight - so our workspace named "Requirements Management" would be mapped into the Project table in Insight to help us report on several workspaces at once.

In simpler terms, we would like to define a REST API to query on the workspace name and other attributes, since this was not auto-created as a part of our XDC file.

Our Focal Point team has several custom workspaces they have developed, and have requested that we report on these in Insight. We have defined a connection to our FP server in Configuration Manager which auto-generated an XDC file for us. We are using this to custom map our Focal Point workspace into Insight, with the URL as mentioned: http://<server>/fp/resources/workspaces/<workspaceid>

We can define resources and map these to create an ETL for our project, and this is working as expected. What we're missing is the definition of the Workspace itself. We were expecting to map the Workspace itself into a Project in Insight - so our workspace named "Requirements Management" would be mapped into the Project table in Insight to help us report on several workspaces at once.

In simpler terms, we would like to define a REST API to query on the workspace name and other attributes, since this was not auto-created as a part of our XDC file.

The FP REST service is owned by the FP team not Insight so you would have to put in a request with them to give you a resource with workspace information. The other thing I can suggest for now is for you to take the same approach as we do for RQM (since they also do not have a resource for projects) and map the project to the resource group name its self as it is in the xdc file. So you atl least get to etl a project resource for FP. Therefore your resource group names should be named after the FP work space so the data can be meaningful in the reports and you would need to create a fact build for this. You can look at the RQMProjects ODS fact build, the query issued is against the internal datasource table System.DATASOURCES
SELECT "guid",
"name"
FROM "System"."DATASOURCES"
WHERE "guid"='{$RESOURCEGROUP_ID}',
this will return to you information about the resource group, name can be saved as a project in RIODS.PROJECT. This however does not address the fact hat you would actually need to somehow correlate the workspace name with the incoming data to associate it with the correct project id, you would have to take care of that in the ETL for the FP resources you will be processing. The OOTB ETL works against a specific workspace which already contains a definition of a project, I'm guessing that these workspaces you are working with don't have this concept of a project in terms of resources and hence there is no conflicting story.

Thank you Petroula! We have other RFE's open against the Focal Point team for similar concerns, where their REST API's do not properly expose data for reporting, but thank you so much for the suggestion on how to proceed in the meantime. I will take the RQM approach.

You're correct that our workspaces do not have the same Project definition as the OOTB workspaces, so we shouldn't have any conflicts with using this method. I appreciate the advice!