A message ID consists of 10 alphanumeric characters that uniquely identify the message. The message ID is composed of:
ID | Description |
---|---|
GBRPC0001I | Starting {0} on cluster {1} ... |
GBRPC0002E | No member in cluster! |
GBRPC0003I | Stopping {0} on cluster {1} ... |
GBRPC0004E | Application MBean is not running on server! |
GBRPC0005I | Invoking synchronization for node {0} ... |
GBRPC0006I | Checking for existence of node {0} |
GBRPC0007E | Node not found for name {0} |
GBRPC0008I | Checking for existence of cluster {0} |
GBRPC0009W | The cluster {0} already exists |
GBRPC0010I | Creating the ServerCluster {0} |
GBRPC0011I | Creating server {0} on node {1} |
GBRPC0012E | ClusterMgr MBean not found for cell {0} |
GBRPC0013I | Synchronization done. |
GBRPC0014I | Checking to see if server {0} is already running on node {1} |
GBRPC0015W | Server {0} already running on node {1} |
GBRPC0016I | Checking to see if server {0} is already exists on node {1} |
GBRPC0017I | Checking for the existence of a NodeSync MBean on node {0} |
GBRPC0018E | NodeSync MBean not found for name {0} |
GBRPC0019I | Creating a server {0} ..... |
GBRPC0020I | Updating virtual host configuration ... |
GBRPC0021I | Create HostAlias for {0} [Host: * port: {1} ] |
GBRPC0022I | Starting server {0} |
GBRPC0023I | Invoking start for cluster {0} |
GBRPC0024E | Error during start, may be already started! |
GBRPC0024I | Stopping {0} ... |
GBRPC0025I | Removing {0} ... |
GBRPC0026W | {0} not found on node {1} |
GBRPC0027E | The key {0} is not correctly set in your properties file |
GBRPC0028I | The cluster is up and running! |
GBRPC0029E | The key {0} is not present in the specified properties file |
GBRPC0030W | The cluster member {0} already exists |
GBRPC0031E | The specified cluster name ({0}) does not exist |
GBRPS0001E | The environment variable JAVA_HOME is not set. You must set this environment variable before running the script. |
GBRPS0002I | Creating a dedicated profile under {0}. |
GBRPS0003I | The profile under {0} is being deleted. |
GBRPS0004I | Cell name: {0} |
GBRPS0005I | Node name: {0} |
GBRPS0006I | Server name: {0} |
GBRPS0007I | This is expected to take a while. |
GBRPS0008I | Restarting the server to finalize the configuration. |
GBRPS0009I | The server is started. |
GBRPS0010I | The server has stopped. |
GBRPS0011E | Application Manager was not found for cell {0} node {1} and server {2}. |
GBRPS0012I | Activation was successful for {0}. |
GBRPS0013I | Deploying {0}. |
GBRPS0014I | Undeploying {0}. |
GBRPS0015I | Updating {0}. |
GBRPS0016W | Failed to stop {0}. |
GBRPS0017I | {0} was successfully installed. |
GBRPS0018I | Removing {0}. |
GBRPS0019I | Creating {0}. |
GBRPS0020W | {0} was not found. |
GBRPS0021I | Enabling Java2 security. |
GBRPS0022E | The error {1} occurred while activating {0}. |
GBRPS0023E | An error occurred while saving the configuration {0}. |
GBRPS0024E | {0} is an unknown application. |
GBRPS0025E | A profile {0} already exists under {1}. A new product offering installation has been detected. You can recreate the sample server by running the Ant script recreateserver in the WODM_HOME/shared/bin directory. Recreating the sample server deletes the existing profile and recreates a new profile. If you do not want to delete the existing profile, you can update the ''profile.name'' property in <InstallDir>/shared/samplesServer/was/build.properties, restarting the server and creating a new profile with the updated name. |
GBRPS0026E | The property was.home is not set in the file <Installation_Dir>/shared/samplesServer/was/build.properties. |
GBRPS0027E | You must have write access on {0} to proceed. Depending on your operating system, you might be able to run the command in elevated mode to access the directory and the directory contents. |
GBRPS0028E | Checking {0} has failed with the message {1}. |
GBRPS0029I | {0} is completed. |
GBRPS0030E | A profile {0} already exists under {1}. Remove the existing profile or use a different profile name. |
GBRPS0031E | Decision Server Rules is not installed on {0}. Unable to create a stand-alone profile for Decision Server Rules. |
GBRPS0032E | Decision Server is not installed under {0}. Unable to create a standalone profile for Decision Server. |
GBRPS0033E | Decision Center is not installed in {0}. Unable to create a stand-alone profile for Decision Center. |
GBRPS0034E | You are upgrading, you have to destroy your profile and re-launch. |
GBRPS0035E | Your profile under {0} still contains logs but has been removed from WAS. Please clean completely the directory an re-launch. |
GBRPT0001I | Adding users to monitor administrative group |
GBRPT0002W | User already mapped to monitor administrative group! |
GBRPT0003W | {0} authorization group does not exist! |
GBRPT0004W | No authorisation group for {0} |
GBRPT0005I | Remove user {0} from role {1} in authorization group {2} |
GBRPT0006I | Creating {0} on node {1} |
GBRPT0007I | {0} created |
GBRPT0008W | JDBC Provider already exits! |
GBRPT0009I | Creating datasource with JDBCProvider {0} |
GBRPT0010I | Deleting {0} ... |
GBRPT0011W | {0} does not exist! |
GBRPT0012W | {0} already exists! |
GBRPT0013I | Installing {0} ... |
GBRPT0014I | Uninstalling {0} ... |
GBRPT0015W | Unable to start Decison applications, may be already started |
GBRPT0016W | XU already deployed, doing nothing XU related |
GBRPT0017I | Install resource adapter on the node: {0} |
GBRPT0018I | Create a J2CConnectionFactory named {0} |
GBRPT0019I | Start application {0} on server {1} ... |
GBRPT0020I | Stop application {0} on server {1} ... |
GBRPT0021W | Unable to stop Decison applications, may be already stopped |
GBRPT0022W | The application {0} is not installed |
GBRPT0023I | Uninstalling {0} ... |
GBRPT0024W | Unable to start {0}, may be already started |
GBRPT0025W | Unable to stop {0}, may be already stopped |
GBRPT0026I | Loading properties file name {0} |
GBRPT0027E | Unsupported database {0} |
GBRPT0028I | Jython scripts are in {0} |