Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
PDF SERENA BUSINESS MASHUPS – ORCHESTRATION SCALING AND DESIGN
In both deployment and promotion, the contents of the blueprint or snapshot are read by the Application Engine and used to update the database tables that control the behavior of the application. This document will describe the contents of the blueprint and snapshot files , identify the corresponding schema and data in the Application Engine database and describe how the database is updated during deployment and promotion. THE MASHUP BLUEPRINT FILE
PDF SERENA BUSINESS MASHUPS – ORCHESTRATION SCALING AND DESIGN
In both deployment and promotion, the contents of the blueprint or snapshot are read by the SBM Application Engine and used to update the database tables that control the behavior of the application. This document will describe the contents of the blueprint and snapshot files , identify the corresponding schema and data in the SBM Application Engine database and describe how the database is updated during deployment and promotion. THE BLUEPRINT FILE
PDF SERENA BUSINESS MASHUPS – ORCHESTRATION SCALING AND DESIGN
This section enumerates the tables in the AE database that are affected by deployment and promotion. For each table, the location of the data in the blueprint or snapshot file that modifies it is described. The bulleted points identify the XML file (s) and path(s) where the data is sourced. In some cases this is the parent element that contains the column data. It should be fairly clear from the sub‐element names which database
PDF Untitled
Promotion takes a snapshot and then promotes that snapshot to the production server. 4. If your testing Application Engine Web Server does use the same Mashup Manager as your production environment, perform the following steps: a) take a snapshot of the deployed mashup in the staging environment b) Save the snapshot to a file . c) Copy that file to a network location accessible by your production environment's Mashup Manager.
CMS-XML Snapshot promotion: Parser Fatal Error at file <> Message: Invalid character (Unicode: 0x6)
ERROR -- Parser Fatal Error at file C:/Program Files /Serena/Business Mashups/ Application Engine /adf8903/teamtrack/7b166fba-73be-4fee-a3e1-efd31c1f7481/vardata.xml, line 4041, char 53 Message: Invalid character (Unicode: 0x6)
CMS-XML Snapshot cannot be imported directly into Composer nor via a GET from AE and open - error similar to following occurs: The name 'Glkas2273v9763ComponentPartsByProductb70e9f57d35c57348c2021aae8254160' is invalid because it exceeds 64 characters in length.
Problem is with the endpoints.xml and a REST grid. The snapshot will promote in AR and the blueprint will import fine but you should be able to import from a snapshot or do a Get from AE and import from there too.
CMS-XML Workflow Names longer than 32 characters cause errors in snapshot promotions
Mashup Composer allows Workflow names to be longer than 32 characters. When deployed , the workflow names are truncated by AE (and so are the "Quick Admin" projects that are created). If the first 32 characters are not unique, AE still creates the workflows and projects, but once a snapshot is taken and promoted into an environment, you will get errors because the names in the snapshot are not unique.
CMS-XML Global Snapshot promotion fails after snapshot upgrade if folders are present
ERROR -- Parser Error at file C:/Program Files /Serena/SBM/ Application Engine /mst97625/teamtrack/global-1f5ad918-d5aa-4488-80ff-3c88514c3ffe/instance.xml, line 10, char 10 Message: element 'ParentID' is not allowed for content model '(Name,Owner,ParentID,Type,SysCode,Attributes,Sequence)'
CMS-XML Snapshot promotion failed with parser error if contain calendar or calendar feed report with reference name Custom Form
ERROR -- Parser Error at file E:/EXTuserAppl/serena/SBM/ Application Engine /mst56027/teamtrack/6344862c-0a2a-44f6-a77c-518c4940fb7b/instance.xml, line 2574, char 10 Message: element 'ReferenceName' is not allowed for content model
CMS-XML State Activity Trend reports cause Snapshots to contain bad xml so promote fails - ERROR -- Parser Fatal Error at file ... invalid character 0x2
If you create a State Activity Trend report and then take a snapshot - this cannot be promoted - you get an error similar to below: ERROR -- Parser Fatal Error at file C:/Program Files /Serena/SBM/ Application Engine /mst82934/teamtrack/2bc73501-b2b4-46a9-9672-157876dac15e/instance.xml, line 1363, char 18 Message: invalid character 0x2
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Title: Dimensions CM: Deploying Emergency Fixes (demonstration)
This demonstration shows you how to deploy an emergency fix to a live production environment in Dimensions CM. You will learn how to promote requests to any stage in the Global Stage Lifecycle, promote and deploy in the same operation, and browse deployment areas.
Title: Dimensions CM: Deploying Requests (demonstration)
This demonstration shows you how to deploy requests in Dimensions CM. You will learn how to promote requests to the next stage in the Global Stage Lifecycle, deploy requests by
Title: Dimensions CM: Scheduling Deployment (demonstration)
This demonstration shows you how to schedule a deployment in Dimensions CM. You will learn how to set a deployment sequence, schedule a deployment, and use the Queue tab in the Deployment view

Additional Assistance

  • Submit a Case Online
  • FAQs