説明 | The command requires the name parameter to be specified. |
アクション | Reissue the command specifying the name. |
説明 | An attempt was made to define a new bundle repository, but the specified name is already in use. |
アクション | Specify a different name. |
説明 | An attempt was made to define a new bundle repository, but another bundle repository already uses the specified URL. |
アクション | Specify a different URL. |
説明 | An attempt was made to modify the bundle repository, but it does not exist. |
アクション | Create the bundle repository. |
説明 | The specified file is not an OSGi bundle. |
アクション | Check and correct the bundle manifest of the supplied file. |
説明 | The bundle cannot be added to the repository because the bundle already exists in the repository. |
アクション | Check whether the bundle in the repository is the correct one. If the bundle in the repository is not correct, remove that bundle from the repository before you add the correct bundle. |
説明 | The bundle cannot be shown or deleted because no bundle with that name exists. |
アクション | Check and correct the version or symbolic name of the bundle. |
説明 | This exception is unexpected. The cause is not immediately known. |
アクション | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
説明 | This exception is unexpected. The cause is not immediately known. |
アクション | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
説明 | This exception is unexpected. The cause is not immediately known. |
アクション | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
説明 | This exception is unexpected. The cause is not immediately known. |
アクション | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
説明 | This exception is unexpected. The cause is not immediately known. |
アクション | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
説明 | The name parameter is required for the addExternalBundleRepository command. |
アクション | Reissue the command and specify the name of the external bundle repository. |
説明 | The URL parameter is required for the addExternalBundleRepository command. |
アクション | Reissue the command and specify the URL of the external bundle repository. |
説明 | One or more bundles that the application requires are being downloaded. The application cannot be modeled until all downloads are complete. |
アクション | Wait until all the required bundles are downloaded, then try again. |
説明 | This exception is unexpected. The cause is not immediately known. |
アクション | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
説明 | This exception is unexpected. The cause is not immediately known. |
アクション | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
説明 | Either the manifest is not present, or the name or format are not correct. |
アクション | Check that the manifest is present and formatted and named correctly. |
説明 | Nesting of Composite Bundle Archives is not supported. |
アクション | Check that the Composite Bundle Archive depends only on bundles in the CompositeBundle-Content header of the Composite Bundle Archive manifest. |
説明 | A Composite Bundle Archive can be deployed only if all the dependencies can be found in the internal bundle repository. |
アクション | Ensure that the Composite Bundle Archive dependencies listed are either in the Composite Bundle Archive or installed in the internal bundle repository. |
説明 | A CompositeBundle-Content entry must use a format similar to 'bundle.name;version="[1.0.0,1.0.0]"'. |
アクション | Ensure that entries in the CompositeBundle-Content header in the composite bundle manifest file specify an exact version and use the correct format. |
説明 | This message is for informational purposes only. |
アクション | No action is required. |
説明 | You are not currently connected to a framework. |
アクション | Use the connect command to connect to a framework. For a list of available frameworks, use the list() command. |
説明 | You are not currently connected to a framework. |
アクション | Use the connect command to connect to a framework. For a list of available frameworks, use the list() command. |
説明 | The bundle ID that was supplied to the command does not match a bundle in the framework. |
アクション | Retry the command with a valid bundle ID. |
説明 | The service ID that was supplied to the command does not match a service in the registry. |
アクション | Retry the command with a valid service ID. |
説明 | You are not currently connected to a framework. |
アクション | Use the connect command to connect to a framework. For a list of available frameworks, use the list() command. |
説明 | You cannot start the bundle because it is already started. |
アクション | No action is required. |
説明 | This message is for informational purposes only. |
アクション | No action is required. |
説明 | You can not stop the bundle because it is already stopped. |
アクション | No action is required. |
説明 | This message is for informational purposes only. |
アクション | No action is required. |
説明 | You are currently connecting to the framework. |
アクション | No action is required. |
説明 | This message is for informational purposes only. |
アクション | No action is required. |
説明 | A framework with the specified ID could not be found. |
アクション | Check that the framework ID is valid and retry the command. |
説明 | A framework with the specified attributes could not be found. |
アクション | Check that the framework attributes are valid and retry the command. |
説明 | This message is for informational purposes only. |
アクション | No action is required. |
説明 | This message is for informational purposes only. |
アクション | No action is required. |
説明 | The bundle cannot be started. |
アクション | Refer to accompanying error messages for more information about why this bundle cannot start. |
説明 | This message is for informational purposes only. |
アクション | No action is required. |
説明 | The bundle cannot be stopped. |
アクション | Refer to accompanying error messages for more information about why this bundle cannot stop. |
説明 | The package ID that was supplied to the command did not match a package in the framework. |
アクション | Check that the package ID is valid and retry the command. |
説明 | The package location that was supplied to the command did not match a package location in the framework. |
アクション | Check that the package location is valid and retry the command. |
説明 | The package name that was supplied to the command did not match a package in the framework. |
アクション | Check that the package name is valid and retry the command. |
説明 | The service filter supplied is not valid. |
アクション | Check that the service filter is valid and retry the command. |
説明 | You are not currently connected to a framework. |
アクション | Use the connect command to connect to a framework. For a list of available frameworks, use the list() command. |
説明 | A bundle cannot be deleted from the internal bundle repository if a Composite Bundle Archive depends on that bundle. |
アクション | To delete the bundle, first delete the Composite Bundle Archives listed, then delete the bundle. |
説明 | The framework that you were connected to is no longer available. This might be because an application has stopped. |
アクション | Check whether the framework is still available and reconnect if required. |
説明 | The asset supplied is not an enterprise bundle archive (EBA) asset. |
アクション | Make sure the asset supplied is an EBA asset. |
説明 | This exception is unexpected. The cause is not immediately known. |
アクション | This exception is unexpected. The cause is not immediately known. |
説明 | The deployment manifest, DEPLOYMENT.MF, to import does not exist. |
アクション | Check that the path of the deployment manifest is correct. |
説明 | The deployment manifest, DEPLOYMENT.MF, to import does not include all the bundles needed to resolve the enterprise bundle archive (EBA) asset. |
アクション | Check that the new deployment manifest includes all the bundles that are listed in the message. |
説明 | The deployment manifest, DEPLOYMENT.MF, to import includes bundles that are not needed to resolve the enterprise bundle archive (EBA) asset. |
アクション | Check that the new deployment manifest does not include the bundles that are listed in the message. |
説明 | This exception is unexpected. The cause is not immediately known. |
アクション | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
説明 | The deployment manifest, DEPLOYMENT.MF, to import has a requirement that cannot be satisfied. |
アクション | Check that the new deployment manifest is complete and includes the bundles needed to resolve the enterprise bundle archive (EBA) asset. |
説明 | The deployment manifest, DEPLOYMENT.MF, is not compatible with the application manifest, APPLICATION.MF, of the asset. |
アクション | Check the new deployment manifest for the following: 1. The Application-SymbolicName and Application-Version in the DEPLOYMENT.MF file must match the corresponding entries in the APPLICATION.MF file. 2. The bundles listed in the Deployed-Content header in the DEPLOYMENT.MF file must match the bundles listed in the Application-Content header in the APPLICATION.MF file. 3. The bundle version in the Deployed-Content header in the DEPLOYMENT.MF file must be within the version range for the corresponding bundle in the APPLICATION.MF file. 4. The bundles listed in the Deployed-Use-Bundle header in the DEPLOYMENT.MF file must also be listed in the Use-Bundle header in the APPLICATION.MF file. 5. The bundle version in the Deployed-Use-Bundle header in the DEPLOYMENT.MF file must be within the version range for the corresponding bundle in the Use-Bundle header in the APPLICATION.MF file. |
説明 | This command requires the specified parameter. |
アクション | Retry the command and specify the required parameter. |
説明 | You attempted to export a deployment manifest to a directory that does not exist, and the directory structure cannot be created. |
アクション | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
説明 | The directory cannot be created. |
アクション | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
説明 | You imported a deployment manifest to an asset, but the enterprise bundle archive (EBA) asset does not exist. |
アクション | Check that the EBA asset is installed. |
説明 | A Composite Bundle Archive (CBA) can export only packages that the bundles it contains also export. The attributes and directives must also match. |
アクション | Correct the composite manifest, COMPOSITEBUNDLE.MF, so that it exports packages that the bundles that the CBA contains also export. |
説明 | The name of the specified file does not end with either a .jar or a .cba file extension. |
アクション | Check and correct the name of the supplied file. The supplied file must be a valid JAR or Composite Bundle Archive (CBA). |