com.sun.enterprise.admin.servermgmt.services.LocalStrings.properties Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of payara-micro Show documentation
Show all versions of payara-micro Show documentation
Micro Distribution of the Payara Project for IBM JDK
#
# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
#
# Copyright (c) 2010-2013 Oracle and/or its affiliates. All rights reserved.
#
# The contents of this file are subject to the terms of either the GNU
# General Public License Version 2 only ("GPL") or the Common Development
# and Distribution License("CDDL") (collectively, the "License"). You
# may not use this file except in compliance with the License. You can
# obtain a copy of the License at
# https://glassfish.dev.java.net/public/CDDL+GPL_1_1.html
# or packager/legal/LICENSE.txt. See the License for the specific
# language governing permissions and limitations under the License.
#
# When distributing the software, include this License Header Notice in each
# file and include the License file at packager/legal/LICENSE.txt.
#
# GPL Classpath Exception:
# Oracle designates this particular file as subject to the "Classpath"
# exception as provided by Oracle in the GPL Version 2 section of the License
# file that accompanied this code.
#
# Modifications:
# If applicable, add the following below the License Header, with the fields
# enclosed by brackets [] replaced by your own identifying information:
# "Portions Copyright [year] [name of copyright owner]"
#
# Contributor(s):
# If you wish your version of this file to be governed by only the CDDL or
# only the GPL Version 2, indicate your decision by adding "[Contributor]
# elects to include this software in this distribution under the [CDDL or GPL
# Version 2] license." If you don't indicate a single choice of license, a
# recipient has the option to distribute your version of this file under
# either the CDDL, the GPL Version 2 or to extend the choice of license to
# its licensees as provided above. However, if you add GPL Version 2 code
# and therefore, elected the GPL Version 2 license, then the option applies
# only if the new code is made subject to such option by the copyright
# holder.
#
internal.error=Internal Error: {0}
validator.invalid_value=Invalid value for {0} : {1}
validator.invalid_type=Invalid type for {0}. Expected {1} or subtype but got {2}
fileValidator.no_read=No read permission: {0}
fileValidator.no_write=No write permission: {0}
fileValidator.not_a_dir={0} is not a directory
portValidator.in_use=Port {0} is in use
domainConfig=domain config
keyFileNotCreated=Error creating keyfile
adminUserComment=# Domain User and Password - Do Not Delete Entry Above
serverPolicyNotCreated=Error creating server.policy
keyStoreNotCreated=Error creating key store {0}
trustStoreNotCreated=Error creating trust store {0}
masterPasswordFileNotCreated=Error creating master password file {0}
timerDbnNotCreated=Error creating timer database dbn file
timerWalNotCreated=Error creating timer database wal file
jbiRegistryTemplateNotCopied=Error copying JBI registry template file
installRoot=install root
cannotDeleteJmsProviderInstance=Error deleting mq broker instance
masterPasswordFileNotRead=Error reading master password file {0}
keyStorePasswordNotChanged=Error changing keystore password for store {0}
s1asKeyPasswordNotChanged=Error changing password for default key with alias s1as for store {0}
passwordAliasPasswordNotChanged=Error changing password for password alias store {0}
passwordAliasKeystoreNotCreated=Could not create password alias keystore {0}
couldNotValidateMasterPassword=Exception validating master password against store {0}
masterPasswordInvalid=Password entered is invalid
derbyEjbTimerDBNotCreated=The embedded EJB Timer Database could not be created, detailed message: {0}
noDerbyLog=The derby log file could not be read. No detailed information available.
nullArg=Null argument was provided.
smfTokenNeeded=Required token [{0}] initialized with invalid value [{1}]. Set the value correctly using ServiceHandler interface.
invalidTO=Invalid value [{0}] specified as timeout. Only non-negative integers are allowed.
serviceNameInvalid=Invalid name [{0}] for the service.
smfLeftoverFiles=There was a previous attempt to create a service with the same name. \
Either choose a different name for the service or delete the service and the corresponding directory [{0}] and retry.
doesNotExist=The object [{0}] could not be found.
serviceTypeNotSet=Service type is not configured correctly.
serviceTemplateNotFound=Service template [{0}] does not exist, something wrong with setting environment like INSTALL_ROOT etc.
notSolaris10=Present Platform, OS: {0} version: {1} is not Solaris 10. This facility is not supported on platforms other than Solaris 10.
noPermissionToCreateManifest=The user [{0}] does not have permission to create the service manifest related files \
and directories at [{1}]. This structure is required per SMF guidelines. Either become super-user to do this \
operation or contact the System Administrator to explicitly get the relevant permissions and try again.
noSmfAuth=The user [{0}] does not seem to have adequate authorizations [solaris.smf.*] on this System to \
create and configure an SMF service. The authorizations available are [{1}].\nSee smf_security(5), rbac(5).\n
missingParamsInFile=The passwordfile that was specified as [{0}] does not contain the property [{1}] in required form. \
Rerun the command after adding [{1}=value] to this file on a separate line.
serviceNameExists=An SMF service with name [{0}] appears to exist as shown by [svcs -a] command, on this machine. Retry creating the service with different name provided for the service.
runtimeStatusToString={0} is {1}
fileNotFound=File {0} not found.
error=error
runtimeStatusToStringStopCluster.alreadyStopped=The clustered instance, {0}, was already stopped.
runtimeStatusToStringStopCluster.success=The clustered instance, {0}, was successfully stopped.
runtimeStatusToStringStopCluster.stoppedToRunning=This should be impossible. The clustered instance, {0}, was stopped and now it is: {1}
runtimeStatusToStringStopCluster.error=The clustered instance, {0}, could not be stopped. It was originally in this state: [{1}] and now it is in this state: [{2}].
runtimeStatusToStringStartCluster.alreadyStarted=The clustered instance, {0}, was already running.
runtimeStatusToStringStartCluster.success=The clustered instance, {0}, was successfully started.
runtimeStatusToStringStartCluster.startedToStopped=This should be impossible. The clustered instance, {0}, was running and now it is: {1}
runtimeStatusToStringStartCluster.error=The clustered instance, {0}, could not be started. It was originally in this state: [{1}] and now it is in this state: [{2}].
CertificateDN=Distinguished Name of the self-signed X.509 Server Certificate is:\n[{0}]
SomeProblemWithKeytool= Domain creation process involves a step that creates primary key and\n self-signed server certificate. This step failed for the reason shown below.\n This could be because JDK provided keytool program could not be found (e.g.\n you are running with JRE) or for some other reason. No need to panic, as you\n can always use JDK-keytool program to do the needful. A temporary JKS-keystore\n will be created. You should replace it with proper keystore before using it for SSL.\n Refer to documentation for details. Actual error is:\n{0}
windows.services.passwordFileNotA=The password file you specified is not a file: {0}
windows.services.passwordFileNotReadable=The password file you specified is not readable: {0}
windows.services.noTargetDir=Can not create a directory for services in the domain: {0}
services.alreadyCreated=\n\nServices have already been created for this server.\nTry deleting the files first \
like so:\n {1} {0}\nor -- use the --force option and they will be deleted for you automatically.\n
windows.services.install.bad=Error while trying to install Payara as a Windows Service. \n\
The return value was: {0}.\nSTDERR: {1}\nSTDOUT: {2}
SMFServiceCreated=The Service was created successfully. Here are the details:\n\
Name of the service:{0}\n\
Type of the service:{1}\n\
Configuration location of the service:{2}\nManifest file location on the system:{3}.\n\
You have created the service but you need to start it yourself. Here are the most typical Solaris commands of interest:\n\
\n\
* /usr/bin/svcs -a | grep {4} // status\n\
* /usr/sbin/svcadm enable {4} // start\n\
* /usr/sbin/svcadm disable {4} // stop\n\
* /usr/sbin/svccfg delete {4} // uninstall
dryrun=\n******** Dry Run ********\nThe service was not really created, but it would have been successful.\n\
Run the command again without the --dry-run option to really run it.
WindowsServiceCreated=The Windows Service was created successfully. It is ready to be started. Here are the details:\n\
ID of the service: {0}\n\
Display Name of the service:{1}\n\
Server Directory: {2}\n\
Configuration file for Windows Services Wrapper: {3}\n\
The service can be controlled using the Windows Services Manager or you can use the\n\
Windows Services Wrapper instead:\n\
Start Command: {4} start\n\
Stop Command: {4} stop\n\
Restart Command: {4} restart\n\
Uninstall Command: {4} uninstall\n\
Install Command: {4} install\n\
Status Command: {4} status\n\
You can also verify that the service is installed (or not) with 'sc query state= all'\n\
windows.services.uninstall.good=Found the Windows Service and successfully uninstalled it.
noSuitableServiceImplementation=Sorry but there is no support yet for your \
Operating System. Currently Linux, Windows and SMF on Solaris are the supported platforms.
bad.server.dirs=Internal Error: Bad Server Dirs Argument.
noAsadminScript=Can not find the location of the administration client script. It is supposed to be here: {0}
xmlfiledump=\nHere is the gnerated config file that would have been used (this is handy for debugging):\n
no_initd=There is no system folder for Services. We were looking for: {0}
no_write_dir=You do not have permission to write to {0}. Please re-run the command with root privileges.
no_rc=Can not determine your Services Configuration. It must be non-standard because this directory: {0} doesn''t exist.\n\
Unfortunately we are unable to create services for this system.
no_rc2=Can not determine your Services Configuration. It must be non-standard because no rc?.d directories were present\n\
in either /etc or /etc/init.d directories. Unfortunately we are unable to create services for this system.
linux.services.uninstall.good=Found the Linux Service and successfully uninstalled it.
LinuxServiceCreated=\
The Service was created successfully. Here are the details:\n\
Name of the service:{0}\n\
Type of the service:{1}\n\
Configuration location of the service:{2}\n\
User account that will run the service: {3}\n\
You have created the service but you need to start it yourself. \
Here are the most typical Linux commands of interest:\n\
\n\
* /etc/init.d/{4} start\n\
* /etc/init.d/{4} stop\n\
* /etc/init.d/{4} restart\n
# Do not translate PATH as it is a reserved operating system variable name
no_updater=Could not find the Ubuntu Services Updater program in your path. The program is named {0}. \n\
Please locate it and add it to your PATH.
cant_delete=Unable to delete this file: {0}. Please delete it manually, or login \
with higher privileges, and run the command again.
too_many_links=Found too many link files that match. To be safe we did NOT delete them. \
Please delete them manually and/or consider \nchanging the name of the service so it \
does not clash. Here are the link file names: \n{0}
ln_error=Error attempting to create a soft link with this command: {0}\nGet this Exception: {1}
no_delete_yet=delete-service is not implemented for this platform yet.
not_installed=The service is not installed.
cant_exec=Can not execute {0}. Try getting your access privileges increased or login as root.
© 2015 - 2024 Weber Informatics LLC | Privacy Policy