Create a hierarchy in ASAM ODS Server

[nrin]

Hello,

I followed the instructions in the white paper "Reorganize Your Data and Hierarchy with NI DIAdem" using a script provided by you. However, when I export a client configuration, I cannot use this hierarchy script in the client I import the configuration. It seems to not recognize the NI ASAM Server.

Can you please help me with this?

[Brad_Turpin]

Hi nrin,

The NI software that can serve up a customer-defined hierarchy with ASAM-ODS function calls is the DataFinder Server Edition 2013 or later.  It is true that for the 2013-2014 year your only option to create the custom hierarchy is with DIAdem 2012.  The VBScript you run in DIAdem creates a hierrarchy definition file which you can then configure the DFSE to use.  You have to export a connection file from the DFSE and then double-click it on each computer that has DIAdem and wants to connect to the ASAM-ODS server the DFSE is serving up.

Which part of this process is causing you trouble?

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[Naoa]

Hello Brad,

I had the same problem when running the script in the client computers. My understanding from your response is that the script "main.vbs" for create the custom hierarchy has to be run in DIAdem 2012. I'm running with 2012 SP1 and is still not working, I could export the DFSE configuration and installed in other computer, however,  the first thing that I notice is that the icons are not the same in the ASAM interface and then when I execute the "main.vbs" and "CreateASAMModelHierarchy.SUC" I got a the attached error.

Thank you in advance for your support.

[nrin]

Hello Brad,

thank you for yor response. My struggle is that after running the DFSE configuration in a client computer with Diadem 2012, I cannot run the script to create a custom hierarchy. It seems to not recognize the connection to the NI Data Finder Server.

And also, I have another problem. When I try to create my custom hierarchy after running the DFSE configuration I cannot use the date properties, as in the default hierarchy. So, for example if I want to retrieve my data by Engine number, then by author and then by year and month, year and month are not visible to use them on the hierarchy. Do you know where this problem is coming from?

Thank you very much in advance

[nrin]

Brad, to clarify: If I create a property "DateTime" with date type and I optimize it on the server then it won't be visible when creating a custom hierarchy. Even date type properties intrinsec to the file are not visible.  

[Brad_Turpin]

Hi nrin,

You need to configure the ASAM-ODS server to be visible in the NAVIGATOR prior to running the script that enables you to define the custom hierarchy.  Can you see your DataFinder-ASAM-ODS server in the NAVIGATOR before you run the script?

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[nrin]

Yes Brad, indeed I configured it to be visible in the navigator before trying to run the hierarchy script. And here is where it seems to not recognize it. However, to make it visible in a client computer I had to install the AOP5 DataPlugin which creates a different view than in the computer where the DataServer is installed.

Thank you

[Brad_Turpin]

Hi nrin,

I still get the feeling we're not communicating.  DIAdem has installed the AOP5 DataPlugin for many years now-- why did you think you needed to install it, and what is the DIAdem version you're using?  When you say the AOP5 DataPlugin gave you a different view than on the server, what software were you comparing it to-- DIAdem on the server, the ASAM-Commander, or what?  You said again that DIAdem doesn't recognize the server (properly?), yet you also said you can see the ASAM-ODS data base in the DIAdem client's NAVIGATOR panel.  What would be different if it were reconized (proeprly)?  What do you mean by it not being recognized (properly)?

The DataFinder on the server still exists, and it is possible for you to connect directly to it by clicking on the "DataFinder" cog icon in the NAVIGATOR.  What you want is to click on the "Data Stores" icon underneath it and choose the ASAM-ODS server that sits on top of the DataFinder.  If you opened the DataFinder instead of the ASAM-ODS server, the tree view really would look different.  The VBScript to help you define a custom ASAM-ODS hierarchy requires that the ASAM-ODS server be opened in the NAVIGATOR, NOT the DataFinder that is underneath the ASAM-ODS server.

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[Brad_Turpin]

Hi nrin,

What time zone are you in?  North/South America?  Europe/Africa?  Asia?  I think it's probably time for either a phone call or an email full of screenshots (brad.turpin@ni.com).

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[Brad_Turpin]

Hi All,

nrin and DIAdem R&D hashed this out via email.  Here's a summary of what they had to do to get this to work with the DFSE 2013 and DIAdem 2012, the short description is NOT to use the handy *.urf file that the DFSE can generate and instead create a Data Store profile manually in DIAdem:

To connect to the NI ASAM-ODS server with AOP5 please follow these steps:
1. Open DIAdem NAVIGATOR.
2. Go to Settings - Data Stores...
3. Add a new data store. Either by using the first toolbar button or via the context menu.
4. Enter a name, select the AOP5 DataPlugin, and click OK.
5. In the following configuration dialog you will have to enter the computer name of the machine where the NI ASAM-ODS server is running.

    (This information is also displayed in the ASAM settings dialog of the DataFinder Manager (DFSE)
6. Click the [...] button in the URL line. In the following dialog select your ASAM-ODS server.
7. Leave the two configuration dialogs with [OK] button clicks and open the new data store in NAVIGATOR.

8. Download the Hierarchy Creator script that was updated on Jan 27, 2014 and run it in DIAdem SCRIPT

Brad Turpin

DIAdem Product Support Engineer

National Instruments