Inspect Package

Before importing an application, you can inspect and evaluate its contents.

  • Use this feature to catch missing items before any changes are applied.
  • Package inspection does not catch all possible errors, such as user rights or disk space issues.
  • An actual deployment is simulated. Error messages read as if you have imported the package.
  • No changes are made to either the application or the target server.

Pre-deployment Application Package Testing

As it is not possible to undo an application import, it is a best practice to inspect your application packages before deployment.

  • Before importing an application, click the Inspect Package button in the Application Designer.
  • Select the application package to inspect. (The system expects the file to have a .ZIP file extension.)
  • The application is inspected and a report appears, which displays the following items.
    • Objects with missing dependencies. Each missing reference or dependency is listed
    • Custom data types that cannot be imported because they already exist
    • Data stores that will not be published because the database schema on the target system does not match and will not be updated automatically
    • Objects that are to be created
    • Objects that are to be updated
    • Package corruption (invalid XML)

Inspecting Processes That Use Web Services

  • Data types that are normally created from a WSDL during application import cannot be created by the package inspection process.
  • Missing data type dependencies of the Call Web Service smart service are listed as problems during package inspection. This does not occur when:
    • The data types are already present on the target system. — or —
    • The data types are included in your application package.
  • It is a best practice to include data type dependencies of the Call Web Service smart service as data objects in your application package.
17.1

On This Page

FEEDBACK