It appears that when an application is published, the [app]/doc/blueprint.xml file contains data for every application in the workspace, including database connection URLs and login's. It is as if, the publishing looks at the repository collection.xml and fleshes it out to the [app]/doc/blueprint.xml.
1. Can these extraneous database data items affect the connection for the application of interest if the URLs are valid and available?
2. Is this blueprint.xml generation by design?
3. If so, just curious, why?
Thank you,
Mike
1. Can these extraneous database data items affect the connection for the application of interest if the URLs are valid and available?
2. Is this blueprint.xml generation by design?
3. If so, just curious, why?
Thank you,
Mike
RE: blueprint.xml "instance" element
Yes, the Blueprint.xml file is copied across when you publish a project (application). The bluepirint.xml file is copied across from the Design Studio to the runtime platform. If there are other projects (applications) then those details are copied as well.
1. The URL and database connection details copied across will be those that were used during development in the Design Studio. This is the Design/Development specification for the applications.
The blueprint.xml db/url details will NOT be used in the Published application, as the details should be overriden by those specified in the Publication Environments details. However, if they have not been changed then they would be the same.
Each Publication Environment is expected to define the DB connection and URL details, and those are placed into the morphyc.xml file at runtime. It is expected that these details would differ from the design/development details in the bluepint.xml.
2. The blueprint.xml is the project(application) specification in the Design studio. This is an important file as it defines various interactions of the project(application). It also defines much of the organisation and graphical layout of the project(application) in the Design Studio.
3. Strictly, all the project(application) details should not be copied across at publication. It is only necessary to copy the details of the single blueprint instance (project) and the generic details.
The other blueprint instance details could be manually removed if essential, but obviously care would need to be taken.