Skip to main content
J
jasperlg1-Visitor
1-Visitor
March 5, 2019
Solved

Operator Advisor: Best practices to deploy to a new server

  • March 5, 2019
  • 1 reply
  • 4260 views

Hi, 

 

We are implementing the Operator Advisor with an actual client, using the OA as an accelerator of our project. We still have some questions around deployment, which are not very clear to me in the guide.

 

What is the recommended way of doing a OA deployment? I mean we will have allot of additional tables and AP's added to the current data model. What are the best practices on how to update the database when we go from one environment to another? Should we write a service that updates the entire databasemodel?

 

Thanks for the help on this, 

 

Jasper

Best answer by vranganathan

This create table service intent is to just update that specific table not the entire database. By default _AP will have only UID column and no data. Typically no other property predefined. The expectation is data model will be finalized before going to the production first time. That may not be the case always.

 

Our intent is NOT to rebuild another database tool. We want to provide what is needed the most to support model driven approach. If you are making these changes(if you are adding first time to _AP I don't see an issue) after the first release, our recommendation is to use SQL to update the given tables. 

 

I hope this helps. 

1 reply

V
vranganathan12-Amethyst
12-Amethyst
March 5, 2019

I am not sure whether your question is around whether to port the schema or data? If schema and data, then you can simply import the database (I would recommend you to create a separate database for OA). If  you are creating the Schema, there are couple of options, Running CreateTables and/or with the help of scripts.

 

If you can brief more on your specific intent, we can provide additional details.

    J
    jasperlg1-VisitorAuthor
    1-Visitor
    March 5, 2019

    @vranganathan,

     

    Thanks for your reply. I should explain our situation a bit more I believe. With a transfer from environment I meant a transfer from a dev environment to a test environment to a production environment, so I want to recreate the tables that I created (and delete the ones I deleted) in my production environment. I've tested the CreateTables function, it doesn't add the _AP properties if the _AP table already existed from before in the database. What kind of scripts are suggested as a best practice to update the database model? Scripts that compare my DataShapes with the tables in the database? Or scripts that just try to push all DataShapes into the database? 

     

    Kind regards,

     

    Jasper

    V
    vranganathan12-AmethystAnswer
    12-Amethyst
    March 27, 2019

    This create table service intent is to just update that specific table not the entire database. By default _AP will have only UID column and no data. Typically no other property predefined. The expectation is data model will be finalized before going to the production first time. That may not be the case always.

     

    Our intent is NOT to rebuild another database tool. We want to provide what is needed the most to support model driven approach. If you are making these changes(if you are adding first time to _AP I don't see an issue) after the first release, our recommendation is to use SQL to update the given tables. 

     

    I hope this helps. 

      Terms & ConditionsCookie settingsAccessibility statement