Publishes a deployment package file to the specified server.
Modifiers
Remarks
Publishing a deployment package replaces all previously published solution artifacts: the operation creates artifacts that are not already stored on the server instance, updates existing artifacts that have a different version on the server instance, deletes existing artifacts that the current package does not contain, and leaves unchanged the artifacts that have the same version in both the currently published package and the server instance.
This means that the deployment package that you are publishing needs to contain all the solution artifacts that your workflow solution requires. A deployment package cannot be published piecemeal.
If your deployment package contains an updated version of a reference table schema file, you need to include a Microsoft Office Excel workbook with a worksheet that is named after and whose data structure matches the updated schema - otherwise the compiler throws a Missing reference table data for X error message, and aborts the operation.
If the company has push notification enabled, the publish command will send a
synchronization request to each of the company's mobile users.
Sample
mebt publish -s https://rockyjupiter.mobilengine.com -u petar.hoyt@gmail.com -p verySecretPassword -c 102 OMG!.dpkg c:\RockyJupiter soReferenceData.xlsx mobilengine srv 33.3 (Release) v33.3.178.33401 Executing publish (upload a dpkg to the server): Service url: https://rockyjupiter.mobilengine.com User: petar.hoyt@gmail.com Create reference table 'myFirstTable' Create reference table 'mySecondTable' Reset integration settings Import form myWebform Import form myMobileForm Import rfs myScript Import reference tables Processing table 'myFirstTable' Processing table 'mySecondTable' Rows added: 8, deleted: 0, modified: 0, empty: 0. Done.