HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

Template access restrictions for users and architects
Template access restrictions for users and architects.Issue
Template viewing and use for non-administrators (architects and users) may have been configured
by an Administrator so that Architects and Users only view and use templates that each have
assigned access to. If restricted, in general:
Possible cause
• An administrator in infrastructure orchestration self service portal may view and use only their
own templates
• An architect in infrastructure orchestration designer and infrastructure orchestration self service
portal may view and use only their own templates
• A user in infrastructure orchestration self service portal may view and use published templates
that they have access to or that have been assigned to them
Contact the administrator for resolution. In ..\Program Files\HP\Matrix infrastructure
orchestration\conf\hpio.properties, the administrator can choose to either restrict a
Action
CMS's templates: template.access.restricted=true or open up a CMS's templates:
template.access.restricted=false. If restricted, assign or unassign individual users to
templates by going to the infrastructure orchestration console, click Templates and then click Modify
Users.
Fatal error occurred while initializing designer
Designer error dialog message:
A fatal error occurred while initializing the Designer.
Issue
Please make sure the HP Matrix infrastructure orchestration service is
running and try again.
Occurs when launching infrastructure orchestration designer from the infrastructure orchestration
console (using the Template tab Edit buttons).
Possible cause
Launch infrastructure orchestration designer using a browser at https://<cms>:51443/hpio/designer
and open the desired template.
Action
Some template XML hand-editing errors are not caught when importing to infrastructure
orchestration designer
Some template XML hand-editing errors, for example, Duplicate Logical Server Group boot order,
are not caught during infrastructure orchestration designer's Import of a template from XML.
Issue
The template was exported from infrastructure orchestration designer to XML, then the XML was
hand-edited with duplicate <Ordinal /> values, and finally the XML was imported back into
infrastructure orchestration designer.
Cause
Do not edit XML templates outside of infrastructure orchestration designer. Editing XML templates
outside of infrastructure orchestration designer is unsupported and undocumented. The XML schema
Action
is not part of the public interface specification; HP may change the XML schema without notice.
Users who modify XML templates, or who create their own XML templates, do so at their own risk.
Use of an invalid template may cause provisioning failures. HP may require the user to reproduce
an issue using an unmodified, IO-generated template before offering support.
Importing a template XML file that was created in a later release of IO into a previous
release and backward compatibility
Importing a template XML file that was created in a later release of IO into a previous release of
IO displays the error: “The template is invalid and could not be read by the
Issue
202 Troubleshooting