|
|
|
|---|
JBIMR1068 |
Severe |
The application
{0} could not be located in DAS repository. Cause: The application name provided
to the export-application-environment command is not available in repository. Action: Check the
application name by listing Service Assemblies. Resource Key: VERIFIER_APPLICATION_NOT_LOCATED |
JBIMA1069 |
Severe |
There was an error in collecting
the list of application variables used in SA {0} Cause: An error occurred while collecting
a list of application variables to be exported by the command export-application-environment. Action: Look
up and verify the application variables using the list command. Resource Key: VERIFIER_ISSUE_COLLECTING_LIST_OF_APP_VARS |
JBIMA1070 |
Severe |
There
was an error in collecting the list of application configs used in SA
{0}. Cause: An error occurred while collecting a list of application configurations to be
exported by the command export-application-environment. Action: Look up and verify the application configurations using the
list command. Resource Key: VERIFIER_ISSUE_COLLECTING_LIST_OF_APP_CONFIGS |
JBIMA1071 |
Severe |
There was an error in getting the application configuration type {0}. Cause:
An error occurred while getting the type of application configuration used by the
given application {0}. Action: Look up and verify the application configuration using the list command.
Resource Key: VERIFIER_ISSUE_COLLECTING_LIST_OF_APP_CONFIG_TYPE |
JBIMA1072 |
Severe |
There was an error in exporting application environment. Cause: An error occurred while
exporting the application environment. Action: Verify that the given application is deployed. Resource Key: VERIFIER_ERROR_EXPORTING_APP_CONFIG |
JBIMA1073 |
Severe |
There was
an error in retrieving application variable value for component {0}. Cause: The value of
an application variable for the component could not be looked up. Action: Verify
that the component is running. Resource Key: VERIFIER_ISSUE_GETTING_APP_VAR_VALUE |
JBIMA1074 |
Severe |
There was an error in retrieving application configuration
value for component {0}. Cause: The value of an application configuration for the component could
not be looked up. Action: Verify that the component is running. Resource Key: VERIFIER_ISSUE_GETTING_APP_CONFIG_VALUE |
JBIMA1075 |
Severe |
There was
an error in retrieving application variable value of {0}. Cause: The value of an
application variable for the component could not be looked up. Action: Verify that the
component is running. Resource Key: VERIFIER_ISSUE_EXPORTING_APP_VAR_VALUE |
JBIMA1076 |
Severe |
There was an error in retrieving application configuration value of {0}. Cause:
The value of an application configuration for the component could not be looked
up. Action: Verify that the component is running. Resource Key: VERIFIER_ISSUE_EXPORTING_APP_CONFIG_VALUE |
JBIMA1077 |
Severe |
Verification of JavaEEServiceEngine service unit failed. Cause:
The service unit for the Java EE Service Engine (sun-javaee-engine) could not be
verified. Action: Check the server log for additional information, and check the application archive. Resource Key:
VERIFIER_JAVAEE_VERIFICATION_FAILED |
JBIMA6000 |
Severe |
Please provide a valid Service Assembly archive. Cause: The verifier is not able to
read the given Service Assembly archive. Action: Verify that the correct archive is
being passed to the verify command. Resource Key: VERIFIER_INVALID_INPUT |
JBIMA6001 |
Severe |
Archive {0} is
not a Service Assembly archive. Cause: The archive provided to the verifier is not
a Service Assembly. Action: Verify that the correct archive is being passed to
the verify command. Resource Key: VERIFIER_INVALID_SA |
JBIMA6002 |
Info |
The following components are not installed: {0} Cause: The
components in the list are not installed and the Service Assembly may fail
deployment. Action: Install the missing components before attempting to deploy the Service Assembly. Resource Key:
VERIFIER_COMPONENT_INSTALLATION_STATUS_ERROR |
JBIMA6004 |
Warning |
SU artifact {0} is not present Cause: A service unit artifact of the specified
name is missing in the application archive. Action: Verify that the list of service
units in jbi.xml is the same as the list of service units included
in the Service Assembly archive. Resource Key: VERIFIER_SU_ARTIFACT_MISSING |
JBIMA6005 |
JBIMA6004 |
A list of WSDL files in the
SA could not be obtained because the SA was not extracted. Cause: The verifier
could not read the Service Assembly archive to get a list of the
WSDL files used. Action: Verify that the correct archive is being passed to the
verify command. Resource Key: VERIFIER_SA_NOT_EXTRACTED |
JBIMA6006 |
Warning |
Component {0} could not be started for application verification. Cause:
The verifier could not start the specified component for application environment verification Action: Check
the status of the specified component. Resource Key: VERIFIER_COMPONENT_NOT_STARTED |
JBIMA6007 |
Warning |
Component {0} has no lifecycle mbean in
target {1}. Cause: The verifier could not start the specified component in the specified
target for application environment verification. Action: Check the status of the specified component in the
target. Resource Key: VERIFIER_NO_COMPONENT_LIFECYCLE_OBJECT |
JBIMA6008 |
Warning |
Component {0} has many lifecycle mbeans in target {1}. Cause:
The verifier could not start the specified component because there are many lifecycle MBeans. Action:
Check the status of the component in the target. Resource Key: VERIFIER_MANY_COMPONENT_LIFECYCLE_OBJECT |
JBIMA6009 |
Warning |
Component {0} has
no mbean with the following pattern: {1}. Cause: The verifier could not look up
the component configuration extension MBean for the specified component. Action: Check the status of the
component. Resource Key: VERIFIER_NO_COMPONENT_EXTENSION_OBJECT |
JBIMA6010 |
Warning |
Component {0} has many mbeans with the following pattern: {1}. Cause:
There is more than one component configuration MBean for the specified component.
Action: Check the status of the component. Resource Key: VERIFIER_MANY_COMPONENT_EXTENSION_OBJECT |
JBIMA6011 |
Warning |
MBean {0} is not registered in
{1}. Cause: The specified MBean is not available in the specified target. Action:
Check the server log for additional information, and verify that the MBean is
available. Resource Key: VERIFIER_INVALID_MBEAN |
JBIMA6012 |
Warning |
Status of endpoint {0} could not be determined. Cause: The verifier could not
verify the status of the given endpoint. Action: Verify that the application is deployed
and started. Resource Key: VERIFIER_ENDPOINT_STATUS_NOT_DETERMINED |
JBIMA6013 |
Warning |
Component {0} was not shutdown. Cause: The verifier started the component
but could not shut it down. Action: Check server log for additional information, and
shut down component. Resource Key: VERIFIER_COMPONENT_NOT_SHUTDOWN |
JBIMA6014 |
Severe |
Templates could not be created. Cause: The export application environment
command was not able to create template files. Action: Verify that the directory provided
for template creation exists and has write permissions. Resource Key: VERIFIER_TEMPLATE_ZIP_NOT_CREATED |
JBIMA6015 |
Severe |
Template zip file exists
and could not be deleted Cause: The export application environment command was not
able to create template files. Action: Erase any previously created application-name-templates.zip files in the directory
provided for template creation. Resource Key: VERIFIER_TEMPLATE_ZIP_EXISTS |
JBIMA6016 |
Warning |
A valid ear/jar file is not found
in the service unit for sun-javaee-engine. Cause: The given application archive does not contain
a service unit for the Java EE Service Engine (sun-javaee-engine). Action: Check the
Service Assembly archive. Resource Key: VERIFIER_JAVAEE_EAR_FILE_NOT_FOUND |
JBIMA6017 |
Warning |
The application {0} is not deployed in target {1}. Cause: The
export application environment cannot be completed for the specified application because it is not
deployed in the target. Action: Check the application name passed to the export application
environment command. Resource Key: VERIFIER_EXPORT_CONFIG_APP_NOT_DEPLOYED |
