Find Answers

Filter Search Results

Ask a Question

Example: "Database could not be verified"

Pages [Next]

Results

When duplicating an application, the roleselection UUID will be copied and is not unique

When duplicating an application that has user values defined in a user field by a role, this roleselection UUID will be copied into the new application. This can cause issues during the deployment of this mashup where already deployed mashups will appear to have the values removed from the already deployed user fields.

SBM: How to setup a REST GRID that calls Deployment Automation (DA) methods

To setup a Rest Grid like this, follow these steps: Create a plain text field to hold the Application Id value (for example, DA_App_ UUID ).

Deploy fails with error: Failed to complete the deployment to server "Default BPEL Server"

00000 INFO 2017-08-02 22:23:08,326 mashupmgr.AECallbackManager -- INFO -- Export callback from Application Engine for export UUID 7e655d7c-8702-4d01-b0a2-ff47d2f914ea [http-nio-8443-exec-5]

RLC: How to filter the list of Environments given when adding Deployment Tasks (About Environment Level Configuration Overrides)

NOTE: If you are setting up Deployment Automation, enter a comma separated list of Environment names or Global Environment UUID values. But, remember, UUID values can be long. If you need to enter more than a few, you may need to make the fixed length size longer.

Composer should prevent a user from creating a field called "UUID" (Dbname).

Composer should prevent a user from creating a field called "UUID" (Dbname). It will publish and deploy without warning, but results in an error message in the application engine as soon as you try to submit an item.

Production aux tables dropped and recreated when snapshot has different UUID

This could only happen if the two aux tables are independently created in a mashup. e.g. A mashup is exported by one masher and a new table added and deployed to a new repository whilst another masher similarly

Similar Answers

Promoting a snapshot has invalid field errors that appear as follows. ... Invalid Field, , specified in field ordering for T(1070),W(0),P(71),S(0),T(0),Section(1)...

This is an indication that project specific settings that rely on a specific field are being transferred to the new application engine, but the field does not exist in the table. Often in this case, it is possible to deploy the application to the test environment and even the production environment.

Deploys are timing out, Invoking import callback, result=12

06/29/2009 11:05:26: Invoking import callback: uuid =ec09c2d9-84e3-4be6-a701-6c59b9c8cfc8, endpoint=http://wlm1w810:8085/mashupmgr/services/aeimportcallback71, result=12 06/29/2009 11:05:26: Invoking import callback failed: unknown.

Error on deploy of a new Process App fails after upgrade from TeamTrack

ERROR -- Unable to update Table to next version - trying to add record for ordering. SQL statement: select A03ZO_TSM_SOFTWARE_PLATFORM.TS_ID, A03ZO_TSM_SOFTWARE_PLATFORM.TS_ UUID from A03ZO_TSM_SOFTWARE_PLATFORM where A03ZO_TSM_SOFTWARE_PLATFORM.TS_ID=0 (TTexcIDS_EXC_UPDATE_TABLE_VERSION) Invalid object name 'A03ZO_TSM_SOFTWARE_PLATFORM'.

Role being removed when deploy another Process App (built from template of the original Process App)

r TS_ UUID as

Pages [Next]

Knowledgebase

Find Answers

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Additional Assistance