Firstly, thank you for the awesome product, and free! I'm trying to prove it's value to justify a cloud subscription to get the extra views and the webforms for data entry, however, I first need to get the core data into the OS version.
I started populating via Protege, then got the latest version of the launch pad. I'm now trying to export what's currently in the repo to xls, modify the xls tabs with the help of the business/tech, and then i want to merge that back in.
This is how far I've got:
Exporting
- I've install the launch pad v5 dup
Published the protege repo to essential viewer
(all good)
I then click "view library" >> "support" >> "Launchpad Plus Loaders"
Click the "Launchpad as Excel" button
And it then downloads an XML file (note this named "l4_launchpad_export" - not v5...)
- If i double click it and select launch with excel, all is good. I can see the apps etc. i started to enter into protege - IDs are this format "KB_058980_Class4" I assume not an issue if i leave as is, and it doesn;t matter if new rows use the launchpad format?
When I save, it states am i sure, i'll loose some features saving as XML 2003 spreadsheet
Q1 - What format should I save as? as is (XML) or xls or something else?
I used this guide - https://enterprise-architecture.org/ess ... ity.php#os
- Step 1a - I created a prod target pointing to my protege 'server' (I'm using a multi user set up) test connection works for both repo and viewer
Step 1b - I created a 'Development' env pointing to another viewer instance in tomcat (for dev and test)
Step 2 - Created a Data source with this name "Launchpad v5 XML"
Q2 Does this have to be the same as the filename i downloaded above in exporting?
Step 3 - This is where the guide starts to diverge from the tool, when I click 'new' in manage imports, i don't get a window pop up called 'Create Import Activity' i get a sub menu with two options 1) Empty Import Activity 2) From Import Template
Q3 what should I select?
I select #2 - it does nothing...
I select #1 and i get the "Create Import Activity"
Name = "Import pre-populated launchpad file"
Excel
No desc
source = the one created above
I upload the spreadsheet I modified above (the XML file)
- I get an error - needs to be excel file
I try Automated XML import type in the drop down
try the upload again
- I get the same error
I save the xml as xls in excel
repeat the above with excel type and this xls file (no error on upload this time)
click log imports
click OK
all good
Step 4 - select row, click Open
- I don't have a preview spreadsheet button, no biggy
Step 5 - I upload the v5 import spec
- Note 'physical proc to app' sheet is not ticked by default, so i click it (to include everything)
I select "Development" and click test import
In the test import popup, i select "Run Import"
I get two warnings about "Deployment Status" and "Physical Proc to App" not being in the xls (I assume due to v4 export?)
ALL buttons are greyed out so I can't do anything other than close this window, where as I was hoping to download the import script, or publish to test viewer to make sure all was well before importing into production. (I also tried a refresh first, no different)
If I create a production dup, and then inspect the dup (zip) contents, and open the python script I can see the new entries in the code, so it appears to import ok.
I made a SQL server backup, and then I imported into the production instance (the protege server), it appears fine, but not ideal skipping the local test env I hoped it would push to (viewer, or a new repo to download if required)
Q4 - Am I doing something wrong?
I had some strange behaviour after running the direct to server import where SQL server would consume a whole core for a long amount of time preventing the protege client from working. I had to reboot the sql and protege server. When it came back up it did something similar after connecting the client. After it disconnecting and reconnecting again, it settled down and I can comfirm the import worked with the new data.
Thoughts on the questions and the SQL behaviour?
Thanks
John