cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

How to publish development to production?

EM_9923519
11-Garnet

How to publish development to production?

I am using thingworx 8.5, I would like to publish the development to production server, however I would like to do it without using Solution Central.

 

I was able to export a package containing all entities using this importing and Exporting in ThingWorx Importing and Exporting Data, Entities, and Extensions

 

What is the next step after having the package?

 

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

I export to "Source Control Entities" on my development server.  I choose the applicable Project or Model Tags, and for the path I use the application name, date, and time, like "/project1_20210712.1307".

 

We have a Dev - QA - Prod environment.  I do the development in Dev and user testing is done in QA.  After exporting in Dev, I manually copy that folder from the Dev server's SystemRepository to the QA server's SystemRepository, open the QA ThingWorx Composer, and import (using Source Control Entities and browsing to the folder I copied into SystemRepository).  Our testing is done on the QA server and when that's good, I copy the folder from the QA server's SystemRepository to the Prod server's SystemRepository, open the Prod ThingWorx Composer, and import.

 

Sometimes I update just a few Things or Mashups during development/testing for a project so I'll export from Dev with a name like "/project1_20210712.1307.incremental" and use the "Start Date" value to only export modified entities after that date, then copy to the QA server and import.

 

If any of the imported Things use passwords, like database connectors, the password has to be updated after import.  Because the export creates readable XML files, any passwords are not included in the exported XML files.  Each of our projects can have multiple database connectors, so I've been using a Thing Template that has all of the query services and the actual database connector uses the template.  I do not include the actual database connector in my Project or Model Tag, just the template.  That way I can update queries in the template and export/import without having to re-enter the database password or change its configuration every time I import.

 

I'm interested in hearing of other ways to move projects from development to production, if others have different ways of doing it.

View solution in original post

5 REPLIES 5

As a developer, a solution can be packaged and published in solution central. As a global admin request for deployment can be placed in the published solution from the solution central portal. For step by step process, you can check this - https://support.ptc.com/help/thingworx/solution_central/en/#page/solution_central%2Fpackage_publish_...

Thanks for prompt response, Is it completely necessary to use Solution Central?

I have packaged  the project with all their dependencies using this 

 

EM_9923519_0-1626104930011.png

Also exported using "Collection of Entities" and "Collection of data" like this

EM_9923519_1-1626105125728.png

EM_9923519_2-1626105183488.png

 

What do I do after this?

Do I only import all this exported results to a new production environment?

I export to "Source Control Entities" on my development server.  I choose the applicable Project or Model Tags, and for the path I use the application name, date, and time, like "/project1_20210712.1307".

 

We have a Dev - QA - Prod environment.  I do the development in Dev and user testing is done in QA.  After exporting in Dev, I manually copy that folder from the Dev server's SystemRepository to the QA server's SystemRepository, open the QA ThingWorx Composer, and import (using Source Control Entities and browsing to the folder I copied into SystemRepository).  Our testing is done on the QA server and when that's good, I copy the folder from the QA server's SystemRepository to the Prod server's SystemRepository, open the Prod ThingWorx Composer, and import.

 

Sometimes I update just a few Things or Mashups during development/testing for a project so I'll export from Dev with a name like "/project1_20210712.1307.incremental" and use the "Start Date" value to only export modified entities after that date, then copy to the QA server and import.

 

If any of the imported Things use passwords, like database connectors, the password has to be updated after import.  Because the export creates readable XML files, any passwords are not included in the exported XML files.  Each of our projects can have multiple database connectors, so I've been using a Thing Template that has all of the query services and the actual database connector uses the template.  I do not include the actual database connector in my Project or Model Tag, just the template.  That way I can update queries in the template and export/import without having to re-enter the database password or change its configuration every time I import.

 

I'm interested in hearing of other ways to move projects from development to production, if others have different ways of doing it.

View solution in original post

Thanks for your answer and detailing how you actually do it! I think it is  a good design.

slangley
23-Emerald I
(To:EM_9923519)

Hi @EM_9923519.

 

If you feel your question has been answered, please mark the appropriate response as the Accepted Solution for the benefit of others with the same question.

 

Regards.

 

--Sharon

Announcements