CORBAObjectNameSpaceBinding.corbanameUrl.displayName=Corbaname URL
CORBAObjectNameSpaceBinding.displayName=CORBAObjectNameSpaceBinding
CORBAObjectNameSpaceBinding.federatedContext.displayName=Federated context
Cell.cellDiscoveryProtocol.displayName=Cell Discovery Protocol
Cell.discoveryAddressEndpointName.displayName=Discovery Address Endpoint Name
Cell.displayName=Cell
Cell.displayName.empty=
Cell.foreignCells.displayName=Foreign Cells
Cell.multicastDiscoveryAddressEndpointName.displayName=Multicast Discovery Address Endpoint Name
Cell.name.displayName=Name
Cell.nodes.displayName=Nodes
Cell.properties.displayName=Custom Properties
Cell.shortName.displayName=Short Name
EjbNameSpaceBinding.applicationNodeName.displayName=Node
EjbNameSpaceBinding.applicationServerName.displayName=Server
EjbNameSpaceBinding.bindingLocation.description.base=Specify the location of the enterprise bean by providing the node name.
EjbNameSpaceBinding.bindingLocation.description.nd=Specify the location of the enterprise bean.  If the enterprise bean is running in a server cluster, select 'Server Cluster'.  Otherwise, select 'Single Server' and provide the node name.
EjbNameSpaceBinding.bindingLocation.displayName=Enterprise Bean Location
EjbNameSpaceBinding.displayName=EjbNameSpaceBinding
EjbNameSpaceBinding.ejbJndiName.displayName=JNDI name
EjbNameSpaceBinding.serverCluster.displayName=Server cluster
EjbNameSpaceBinding.singleServer.displayName=Single server (Node is required)
EndPoint.displayName=End Point
EndPoint.host.displayName=Host
EndPoint.port.displayName=Port
ExecutionState.UNKNOWN=Unknown
ForeignCellBinding.bootstrap.duplicate.hostname.error=Host name {0} already has entry for port {1}
ForeignCellBinding.bootstrapAddresses.displayName=Bootstrap addresses
ForeignCellBinding.displayName=Foreign Cell Bindings
ForeignCellBinding.endpoint.displayName=Bootstrap addresses
ForeignCellBinding.endpoint.host.displayName=Host
ForeignCellBinding.endpoint.port.displayName=Port
ForeignCellBinding.name.displayName=Foreign cell name
ForeignCellBinding.name.not.valid.error=Foreign cell name must be specified.
ForeignCellBinding.new.step1=Specify foreign cell name
ForeignCellBinding.new.step2=Specify bootstrap addresses
ForeignCellBinding.new.step2.help=Specify the foreign cell name and create bootstrap endpoint bindings.
ForeignCellBinding.new.step2.propName.displayName=Host name
ForeignCellBinding.new.step2.propValue.displayName=Port
ForeignCellBinding.new.step3=Summary
ForeignCellBinding.no.bootstrap.address.error=A bootstrap address must be specified.
ForeignCellBinding.portvalue.not.integer.error=Port value must be a non-negative integer.
ForeignCellBinding.step3.binding=Bootstrap bindings
ForeignCellBinding.step3.create.new=New Foreign Cell Binding
ForeignCellBinding.step3.host=host
ForeignCellBinding.step3.name=Foreign cell name
ForeignCellBinding.step3.port=port
Host.name.displayName=Host Name
HostAlias.displayName=Host Name
HostAlias.port.displayName=Port
IndirectLookupNameSpaceBinding.displayName=IndirectLookupNameSpaceBinding
IndirectLookupNameSpaceBinding.initialContextFactory.displayName=Initial context factory name
IndirectLookupNameSpaceBinding.jndiName.displayName=JNDI name
IndirectLookupNameSpaceBinding.providerURL.displayName=Provider URL
IndirectNameSpaceBinding.other.ctxproperties.displayName=Other Context Properties
Library.classloading.displayName=Class Loading
Library.classpath.displayName=Classpath
Library.displayName=Shared Libraries
Library.isolatedClassloader.displayName=Use an isolated class loader for this shared library
Library.name.displayName=Name
Library.nativepath.displayName=Native Library Path
MimeEntry.displayName=MIME Type
MimeEntry.extensions.displayName=Extensions
NameSpaceBinding.bindingType.displayName=Binding type
NameSpaceBinding.create.new=New Name Space Binding
NameSpaceBinding.displayName=Name Space Bindings
NameSpaceBinding.name.displayName=Binding identifier
NameSpaceBinding.nameInNameSpace.displayName=Name in name space
NameSpaceBinding.new.step1=Specify binding type
NameSpaceBinding.new.step2.corba=Specify basic properties
NameSpaceBinding.new.step2.ejb=Specify basic properties
NameSpaceBinding.new.step2.indirect=Specify basic properties
NameSpaceBinding.new.step2.string=Specify basic properties
NameSpaceBinding.new.step3=Summary
NameSpaceBinding.new.step3.other=Specify additional context properties
NameSpaceBinding.new.step3.other.help=Enter any additional properties to pass to the javax.naming.InitialContext constructor. Click Apply to add a new property. Select a property already in the list, and click the Edit button to edit it. Select a property already in the list, and click the Delete button to remove it.
NameSpaceBinding.new.step3.other.propDescription.displayName=Description
NameSpaceBinding.new.step3.other.propName.displayName=Name
NameSpaceBinding.new.step3.other.propValue.displayName=Value
NameSpaceBinding.othercontext.property.duplicate.error=Other context property name {0} already exists
Node.discoveryProtocol.displayName=Discovery Protocol
Node.displayName=Node
Node.displayName.empty=
Node.name.displayName=Name
Node.not.synchronized=Not synchronized
Node.platform.displayName=Platform Type
Node.properties.displayName=Custom Properties
Node.shortName.displayName=Short Name
Node.status.displayName=Status
Node.synchronized=Synchronized
Node.unmanaged=Not applicable
Node.version.none=No version
Node.version.unknown=Unknown
Node.version.unmanaged=Not applicable
OtherContextProperty.description.displayName=Description
OtherContextProperty.displayName=Other Context Property
OtherContextProperty.name.displayName=Name
OtherContextProperty.value.displayName=Value
Platform.AIX=AIX
Platform.HP=HP-UX
Platform.LINUX=Linux
Platform.OS400=OS/400
Platform.SOLARIS=Solaris
Platform.WINDOWS=Windows
Platform.ZOS=z/OS
Property.description.displayName=Description
Property.displayName=Property
Property.name.displayName=Name
Property.required.displayName=Optional
Property.validationExpression.displayName=Validation Expression
Property.value.displayName=Value
PropertySet.description.displayName=description
PropertySet.displayName=Property Set
PropertySet.properties.TypedProperty.displayName=Typed Properties
PropertySet.properties.displayName=Properties
SIPApplicationRouter.AppOrdering.title=Application Routing Order
SIPApplicationRouter.Name.displayName=SIP Application Router Name
SIPApplicationRouter.applicationName.displayName=Application name
SIPApplicationRouter.applicationOrder.displayName=Application Order
SIPApplicationRouter.applicationOrder.page.description=Specify the application startup order weights, which will in turn define the order in which SIP requests are routed to applications. Note: This page and the application level Startup behavior pages modify the same underlying application startup order values.
SIPApplicationRouter.applicationOrder.startupOrder=Startup order weight
SIPApplicationRouter.applicationOrderFor.displayName=Application order for
SIPApplicationRouter.dar.detail.page.description=Use this page to view or modify the targets associated with the default application router (DAR). You can specify the order in which SIP applications are executed at an initial SIP request for each associated target.
SIPApplicationRouter.dar.rule.mainText=Specify the properties of this Default SIP Application Router rule.
SIPApplicationRouter.dar.rule.moveDown=Move down
SIPApplicationRouter.dar.rule.moveUp=Move up
SIPApplicationRouter.dar.upload.button=Import
SIPApplicationRouter.dar.upload.fileLabel=Full path and name of DAR configuration file
SIPApplicationRouter.dar.upload.groupLabel=DAR Configuration File
SIPApplicationRouter.dar.upload.success=DAR configuration file was imported successfully.
SIPApplicationRouter.dar.upload.text=Specify a DAR configuration file containing appropriate application routing rules. Importing a new rules will replace all existing rules for this target. For instructions on creating a DAR configuration file, refer to the JSR 289 specification.
SIPApplicationRouter.dar.upload.title=Import
SIPApplicationRouter.dar.warning.unknownApplication=Warning: The specified appliaction, {0}, is not installed.
SIPApplicationRouter.darConfigPage.add.button=New...
SIPApplicationRouter.darConfigPage.all.methods.scope=All Methods
SIPApplicationRouter.darConfigPage.application=Application
SIPApplicationRouter.darConfigPage.application.desc=Specifies the name of the application that the application router will route to.
SIPApplicationRouter.darConfigPage.delete.button=Delete
SIPApplicationRouter.darConfigPage.import.button=Import...
SIPApplicationRouter.darConfigPage.mainInstructions=Specify and order the Default SIP Application Router (DAR) rules applied to this target. You can also import the rules from a DAR configuration file. Note: The rules can only be re-ordered within a given method.
SIPApplicationRouter.darConfigPage.method=Method
SIPApplicationRouter.darConfigPage.method.desc=Specifies the name of the SIP method being used in the request.
SIPApplicationRouter.darConfigPage.method.existing=Existing method
SIPApplicationRouter.darConfigPage.method.new=New method
SIPApplicationRouter.darConfigPage.routeModifier=Route Modifier
SIPApplicationRouter.darConfigPage.routeModifier.desc=Specifies the Route Modifier
SIPApplicationRouter.darConfigPage.routingRegion=Routing Region
SIPApplicationRouter.darConfigPage.routingRegion.desc=Specifies the Routing Region
SIPApplicationRouter.darConfigPage.sipUri=SIP URI
SIPApplicationRouter.darConfigPage.sipUri.desc=Specifies the SIP URI that indicates the route as returned by the application router.
SIPApplicationRouter.darConfigPage.stateInfo=State Info
SIPApplicationRouter.darConfigPage.stateInfo.desc=Specifies the State Info, which is for the application router's internal use only.
SIPApplicationRouter.darConfigPage.subscriber=Subscriber identifier
SIPApplicationRouter.darConfigPage.subscriber.desc=Specifies the identity of the subscriber that the DAR returns.
SIPApplicationRouter.darConfigPage.subscriber.existing=Existing subscriber identifier
SIPApplicationRouter.darConfigPage.subscriber.new=New subscriber identifier
SIPApplicationRouter.darConfigPage.title=DAR configuration file
SIPApplicationRouter.darFile.badFileError=The specified file is not a valid DAR configuration file.
SIPApplicationRouter.darFile.importError=An error occurred while importing the DAR configuration file. Please check the logs for details.
SIPApplicationRouter.darFile.parseError=An error occurred while parsing the DAR configuration file. Please check the logs for details.
SIPApplicationRouter.darFilePath.description=Specifies the path to the DAR configuration file.
SIPApplicationRouter.darFilePath.displayName=Full path to DAR configuration file
SIPApplicationRouter.darPathExists.warning=This target has already been configured using the custom property javax.servlet.sip.ar.dar.configuration, defined in the SIP Container settings for {0}. To use the console to configure this target, remove the custom property.
SIPApplicationRouter.description=Use this page to specify the order in which applications run during an initial Session Initiation Protocol (SIP) request. You can use the SIP default application router (DAR) that is provided with the product, or you can specify your own application router, which must comply with the SIP Servlet specification. The default application router allows you to specify either a basic ordering of SIP applications or a properties file based configuration as outlined in the SIP Servlet specification.
SIPApplicationRouter.detail.page.description=Use this page to configure custom SIP appliaction routers. Target servers or clusters that have been associated with this SIP application router are also listed.
SIPApplicationRouter.displayName.lower=SIP application routers
SIPApplicationRouter.editApplicationOrder.displayName=Edit Application Order...
SIPApplicationRouter.fullName.displayName=Full Name
SIPApplicationRouter.moveToApplicationRouter.displayName=Move to Application Router
SIPApplicationRouter.name.description=Specifies a logical name that represents the application router.
SIPApplicationRouter.name.displayName=SIP application router name
SIPApplicationRouter.name.displayName.exists=A SIP application router with this name already exists. Please specify a different SIP application router name.
SIPApplicationRouter.noApplicationInstalled.displayName=No Applications Installed
SIPApplicationRouter.provider.description=Specifies the provider name of the application router. This is defined in the custom application router jar file.
SIPApplicationRouter.provider.displayName=SIP application router provider name
SIPApplicationRouter.selectTarget.displayName=You must select at least one target to perform this action.
SIPApplicationRouter.target.displayName=Target
SIPApplicationRouter.targetDetail.page.description=For this target, specify whether the Default SIP Application Router (DAR) should rely on the basic application startup order or advanced application routing rules (DAR configuration).
SIPApplicationRouter.targets.description=Specifies a server or cluster that is configured to use a SIP application router.
SIPApplicationRouter.targets.displayName=Targets
SIPApplicationRouter.targetsAndOrder.displayName=Targets
SIPApplicationRouter.useApplicationOrdering.description=When selected, the application order from the target is used.
SIPApplicationRouter.useApplicationOrdering.displayName=Manually specify the application order
SIPApplicationRouter.useApplicationStartupWeights.description=When selected, the application startup weights are used as the routing order
SIPApplicationRouter.useApplicationStartupWeights.displayName=Basic application startup order
SIPApplicationRouter.useApplicationStartupWeights.link=Configure application startup order
SIPApplicationRouter.useDarFileLink.description=When this option is selected, the default application router (DAR) configuration file is used to provide application order.
SIPApplicationRouter.useDarFileLink.displayName=Advanced application routing rules (DAR configuration)
SIPApplicationRouter.useDarFileLink.link=Configure routing rules
SIPApplicationRouter.weight.must.be.an.integer=Weight must be an integer.
StringNameSpaceBinding.displayName=StringNameSpaceBinding
StringNameSpaceBinding.stringToBind.displayName=String value
TCPIPProtocolType.MULTICAST=MULTICAST
TCPIPProtocolType.TCP=TCP
TCPIPProtocolType.UDP=UDP
Transport.address.displayName=address
Transport.displayName=Transport
Transport.external.displayName=External
Transport.properties.displayName=Properties
Transport.sslConfig.displayName=SSL
Transport.sslEnabled.displayName=SSL Enabled
TypedProperty.displayName=Typed Property
TypedProperty.type.displayName=Type
VariableSubstitutionEntry.displayName=WebSphere Variables
VariableSubstitutionEntry.symbolicName.displayName=Name
VariableSubstitutionEntry.value.displayName=Value
VirtualHost.aliases.displayName=Host Aliases
VirtualHost.displayName=Virtual Hosts
VirtualHost.mimeTypes.displayName=MIME Types
VirtualHost.name.displayName=Name
about.build.date=Build Date:
about.build.num=Build Number:
about.link.text=Access Help:
about.title=<label for="abouttext"><span class="purplebold">About</span> <span class="graytext"> your WebSphere Application Server</span></label>
add.managed.node.displayName=Add Managed Node
add.managed.windows.node.displayName=Add Managed Windows Node
add.node.connection=Node connection
add.node.connector.displayName=JMX connector type
add.node.displayName=Add Node
add.node.failed=The add node operation failed. Check the server logs for details.
add.node.failed.connector.exception=The add node operation failed because the deployment manager could not connect to the remote server. Check the host name and port values and make sure the server is running.
add.node.failed.wizard.link=Return to the node wizard
add.node.host.displayName=Host
add.node.hung=The console has not received information on the add operation in a timely manner. The state of the operation is indeterminate. Check the add node log for details.
add.node.include.apps=Include applications
add.node.include.buses=Include buses
add.node.initiated=The deployment manager has initiated the federation of the node on host {0} into the cell. This operation may take several minutes to complete. Check the addNode.log file on {0} for details on this operation. You will need to log into the console again after the operation has completed to see the new node in the console.
add.node.local.password.displayName=Application server password
add.node.local.user.displayName=Application server user name
add.node.managed=Managed node
add.node.null.local.password=Application server password is required if an application server name is provided.
add.node.null.local.user.name=Application server user name is a required parameter.
add.node.null.password=Deployment manager password is a required parameter.
add.node.null.starting.port=A starting port number is required if you select to specify a node agent starting port.
add.node.null.user.name=Deployment manager user name is a required parameter.
add.node.options=Options
add.node.password.displayName=Deployment manager password
add.node.port.displayName=JMX connector port
add.node.port.number=Port number
add.node.replicated=Recover an existing node
add.node.rmi.displayName=RMI
add.node.rmi.port.displayName=RMI connector port
add.node.run.as.service=Run node agent as Windows service
add.node.service.confirm=Specify whether to run the node agent as a Windows service.  Click OK to continue with the add node action.  Click cancel to modify add node options.
add.node.service.confirm.password.displayName=Confirm password
add.node.service.mismatch.password=The passwords that you entered do not match.  Re-enter and confirm the password to use on the node agent service.
add.node.service.null.user=You specified a password but not a user ID.  If you provide a password, the user ID must also be set.
add.node.service.password.displayName=Password
add.node.service.user.displayName=User name
add.node.soap.displayName=SOAP
add.node.specify=Specify
add.node.starting.port=Starting port
add.node.status.adding=Adding node
add.node.status.logout=The new node will not be available in the console until you log in again.
add.node.status.logout.link=Logout from the WebSphere Administrative Console
add.node.status.nodes.link=View the available nodes.
add.node.unmanaged=Unmanaged node
add.node.use.default=Use default
add.node.user.displayName=Deployment manager user name
add.replicated.node.title=Recover An Existing Node
button.addnode=Add Node
button.forceremovenode=Force Delete
button.fullresync=Full Resynchronize
button.removenode=Remove Node
button.sync=Synchronize
button.syncall=Synchronize All
current.user.preferences=Current User Preferences
developer.domain.desc=<span class="desctext">Get the latest technical articles, best practices, tutorials and much more in the <a href="http://www.ibm.com/developerworks/websphere/zones/was/" target="_blank">WebSphere Application Server Zone</a>.</span>
developer.domain.link.text=http:// www.ibm.com/ developerworks/ websphere/
developer.domain.title=<span class="bluebold">developerWorks WebSphere</span>
download.plugincfg=View or download the current Web server plug-in configuration file
environment.button.edit=Edit
environment.label.corba=CORBA
environment.label.ejb=EJB
environment.label.indirect=Indirect
environment.label.name=Name
environment.label.scope=Scope
environment.label.string=String
environment.nodePropName.displayName=Name
environment.nodePropValue.displayName=Value
environment.nodeproperties.button.back=Back
environment.nodeproperties.displayName=Node Installation Properties
environment.nodeproperties.link.displayName=Node Installation Properties
environment.propname.not.present=Property name not set.
environment.propvalue.not.present=Property value not set.
error.duplicate.foreigncellbinding.name=Error: The foreign cell binding "{0}" already exists.  
error.duplicate.hostalias.name=<span class="validation-error">Error: A host alias with host name "{0}" and port "{1}" already exists.</span><br>
error.duplicate.namespacebinding.name=The binding identifier "{0}" already exists in this scope.
error.duplicate.namespacebinding.nameInNameSpace=A binding with name in name space "{0}" is already configured in this scope.
error.duplicate.propertyname=A property with name {0} already exists. You must use a unique property name.
error.duplicate.variablename=A variable with name {0} already exists. You must use a unique variable name.
error.duplicate.virtualhost.name=<span class="validation-error">Error: The virtual host "{0}" already exists.</span><br>
error.foreigncellbinding.not.found=Foreign Cell Binding can not be found.
error.hostalias.not.found=Cannot find the host alias.
error.library.not.found=The library was not found.
error.mimeentry.not.found=Cannot find the MIME entry.
error.namespacebinding.not.found=The name space binding was not found.
error.noMimeEntry=<li>Missing MIME type</li>
error.node.not.found=The node was not found.
error.replicators.dont.exist=None of the existing domains have replicators defined.
error.replicators.not.defined=One or more domains have no replicators defined.
error.variable.cannot.create=The variable {0} cannot be created.
error.variable.cannot.delete=The variable {0} cannot be deleted.
error.variable.cannot.edit=The variable {0} cannot be edited.
error.variable.not.found=The variable was not found.
error.virtualhost.not.found=The virtual host was not found.
explore.desc=<span class="desctext">Find <a target="_blank" href="http://www.ibm.com/software/webservers/appserv/">product information on IBM.com</a> about the WebSphere software family.  Information for IBM i is found on the <a target="_blank" href="http://www.ibm.com/systems/i/software/websphere/index.html">WebSphere Application Server for IBM i</a> product Web site.</span>
explore.link.text=http:// www.ibm.com / software / webservers / appserv/
explore.title=<span class="bluebold">WebSphere Application Server on IBM.com</span>
force.delete.error=Node {0} cannot be deleted. Verify that the node configuration resources are not locked. Check the deployment manager error log for additional problem determination information.
force.remove.node.confirm=Click OK to delete this node.  If you do not want to delete the nodes, click Cancel.
force.remove.node.help=<img alt="Warning" align="bottom" src="./images/Warning.gif"> The force delete option removes nodes from the master repository that are not removed properly from the cell.  The Remove Node action is preferred to delete a node from the configuration.  If you continue with this operation, you need to uninstall the node or run the remove node utility using the -force option at that node.
force.remove.node.title=Force delete
foreigncell.legacy.bootstrap.warning=<span class="validation-warn-info">Warning: The foreign cell binding contains the deprecated bootstrap address, host "{0}" and port "{1}". Refer to the help page for how to migrate this attribute to the current release level.</span><br>
global.preferences=Global Preferences
globalBiDiTextDirection.label=Default text direction for all users
globalEnableBiDi.label=Enable bidirectional support for all users
infocenter.desc=<span class="desctext">For documentation, including articles and PDF files, visit the <a href="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=" target="_blank">online information center</a>.
infocenter.link.text=http:// www-3.ibm.com / software / webservers / appserv/
infocenter.title=<span class="bluebold">Documentation</span>
missing.required.values=Missing required values
nav.swg.com.ibm.ws.environment=Environment Services
nav.swg.com.ibm.ws.environment.resources=J2EE Resources
nav.view.foreign.cell.bindings=Foreign cell bindings
nav.view.libraries=Shared libraries
nav.view.name.space.bindings=Name space bindings
nav.view.variable.substitution.entry=WebSphere variables
nav.view.virtual.hosts=Virtual hosts
nav.webSphere.environment.configuration=Environment
node.agent.must.be.active.for.sync=The synchronize operation can not be performed on node {0} because its node agent is not active.
node.already.exists=Node {0} already exists and can not be created.
node.must.be.selected=You must select at least one node to perform this action.
node.sync.failed=Failed to initiate the synchronization request for node {0}. Check the deployment manager's SystemOut.log and the node agent's SystemOut.log for more error information.
null.host.name=Host name is a required parameter.
null.port=Port is a required parameter.
one.node.must.be.selected=You must select one node to perform this action.
plugincfg.generated=The Web server plug-in configuration was updated successfully.
plugincfg.generation.failed=An error occurred while updating the Web server plugin configuration. Check the logs for details.
plugincfg.title=Update global Web server plug-in configuration
remote.instance.not.found=The add node operation failed because the remote instance could not be located. Check the host and port values and make sure that the remote application server instance is running.
remove.node.confirm=Click the OK button to remove the following nodes, or click the Cancel button to return to the prior page.
remove.node.failed=Failed to remove node {0}. Check the server logs for details.
remove.node.failure=The remove node operation failed for node {0}. The underlying error is as follows: {1}
remove.node.help=Removing a node will cause the node to be immediately removed from the master configuration repository.
remove.node.hung=The console has not received information on the remove operation in a timely manner. The state of the operation is indeterminate. Check the remove node log for details.
remove.node.initiated=The deployment manager is removing {0} from the cell. This operation may take several minutes to complete. You will need to log into the console again after the operation has completed to see the node removed from the list of available nodes in the console.
remove.node.node.agent.not.active=The node agent on node {0} is not active. The node can not be removed.
remove.node.only.select.one.node=The remove node operation can only be performed on one node at a time.
remove.node.operation.failed=The remove node operation did not complete successfully. Check the remove node and server logs for details.
remove.node.status.logout=The node will be listed in the console until you log in again.
remove.node.status.removing=Removing node
remove.node.title=Remove Node
sync.request.checkstatus=Refresh the page to see the current synchronization status.
sync.request.submitted=Successfully initiated synchronization of the repository on node {0} with the deployment manager's repository.
this.node.already.synchronized=The node {0} is already synchronized.
this.node.can.not.be.removed=The remove operation is not valid for the deployment manager node {0}.
this.node.can.not.be.stopped=The stop operation is not valid for the deployment manager node {0}.
this.node.can.not.be.synchronized=The synchronize operation is not valid for the deployment manager node {0}.
unmanaged.node.invalid.stop.operation=The stop operation is not valid for unmanaged node {0}.
unmanaged.node.invalid.sync.operation=Synchronization operations are not valid for unmanaged node {0}.
update.plugincfg=Update global Web server plug-in configuration
virtual.host.must.be.selected=You must select at least one virtual host to perform this action.
warning.foreigncelbinding.name.change=Changing the settings for this foreign cell binding may affect applications which are currently bound to run on it.  You must manually review the foreign cell binding used by each application to ensure that they are correct.
warning.virtualhost.name.change=Changing the settings for this virtual host may affect applications which are currently bound to run on it.  You must manually review the virtual host mappings for each application to ensure that they are correct.


CORBAObjectNameSpaceBinding.corbanameUrl.description=Specifies a CORBA name URL string that identifies where the object is bound in a CosNaming server.
CORBAObjectNameSpaceBinding.description=Use this page to configure a name binding of a CORBA home that has already been configured on a server within the cell.
CORBAObjectNameSpaceBinding.federatedContext.description=Specifies that the target is a CosNaming context (if checked) or a leaf node object (if not checked).
Cell.cellDiscoveryProtocol.description=Specifies the protocol that the cell follows to retrieve information from a network.
Cell.description=Use this page to set the discovery protocol for an existing cell. A cell is a configuration concept, a way for an administrator to logically associate nodes according to whatever criteria make sense in the  administrator's organizational environment.
Cell.discoveryAddressEndpointName.description=Specifies the name of the end point that contains the discovery address.
Cell.foreignCells.description=The domain holds a collection of foreign domain objects that can be used to access a different domain.
Cell.multicastDiscoveryAddressEndpointName.description=Specifies the name of the end point that contains the multicast discovery address.
Cell.name.description=Specifies the name of the existing cell.
Cell.nodes.description=Use this page to define nodes in this cell
Cell.properties.description=Specifies arbitrary configuration properties that apply to this cell.
Cell.shortName.description=Specifies the short name of the cell. This name can contain one to eight uppercase alphanumeric characters, but it cannot start with a numeral. This field only applies to the z/OS(R) platform.
EjbNameSpaceBinding.applicationServerName.description=Specifies the name of the cluster or non-clustered server in which the enterprise bean is configured.
EjbNameSpaceBinding.bindingLocation.description=Specifies the location of the enterprise bean.
EjbNameSpaceBinding.description=Use this page to configure a name binding of an enterprise bean home that has already been configured on a server within the cell.
EjbNameSpaceBinding.ejbJndiName.description=Specifies the enterprise bean JNDI name (the name in the bean bindings, not the java:comp name).
EndPoint.description=Specifies a communication endpoint used by services or runtime components running within a process.
EndPoint.host.description=Specifies the IP address, the full domain name system (DNS) host name with a domain name suffix, or the short DNS host name that a web client uses to request a web application resource. Web application resources include servlets, JSP, or HTML pages. Host names on the ports can be resolvable names or IP addresses. The server will bind the port to the specific host name or IP address given. That port is accessible through the IP address that resolves from the given host name or IP address. The IP address can be in IPv4 format on all platforms, or in IPv6 format on operating systems on which the server supports IPv6.
EndPoint.port.description=Specifies the port configured for the application server to accept web client requests. You must specify a port value in conjunction with the host name. Valid port values are between 0 and 65535. A port value of 0 causes the system to pick an ephemeral port. Port numbers on the application server can be reused only when the host names resolve to unique IP addresses (such as for multiple network address cards) and there is not a port with the same port number and a wildcard '*' host name.
ForeignCellBinding.bootstrap.address.required=At least one bootstrap address is required.
ForeignCellBinding.bootstrapAddresses.description=Use this page to specify the addresses to use to bootstrap to a foreign cell. Multiple bootstrap addresses can leverage the failover support provided by clusters. Multiple bootstrap addresses must resolve to members of the same cluster.
ForeignCellBinding.create.new=Wizard to configure new foreign cell bindings
ForeignCellBinding.create.new.description=Use this wizard to configure one or more foreign cell bindings. Configure a foreign cell binding for each cell that is accessed by applications in the local cell.
ForeignCellBinding.description=Use this page to manage bindings that resolve to the cell root naming context in a foreign cell. Applications in a local cell can look up objects in a foreign cell through a foreign cell binding.
ForeignCellBinding.endpoint.description=Use this page to specify a bootstrap address for a foreign cell.
ForeignCellBinding.endpoint.host.description=Specifies a host for the bootstrap address. Specify an IP address or DNS host name.
ForeignCellBinding.endpoint.port.description=Specifies a port number for the bootstrap address.
ForeignCellBinding.name.description=Specifies the name of the other (foreign) cell. The foreign cell and the local cell must have different names.
ForeignCellBinding.new.step2.propName.description=Specifies a server or cluster in the foreign cell that is used for bootstrapping. Specify an IP address or DNS host name.
ForeignCellBinding.new.step2.propValue.description=Specifies the bootstrap port number for the deployment manager of the host server or cluster.
Host.name.description=Specifies the host name of the node being configured.
HostAlias.description=Use this page to edit or create a domain name system (DNS) alias by which the virtual host is known. An alias is the combination of DNS host name and a unique port number. A web client uses the alias to form the URL request of a web application resource.  Application resources include servlets, JSP files, or HTML pages. For example, the default_host alias is the myhost.newyork.com:9080 portion of http://myhost.newyork.com:9080/servlet/snoop or the myhost.newyork.com:9043 portion of a secure https://myhost.newyork.com:9043/servlet/snoop URL.
HostAlias.hostname.description=Specifies the IP address, the full domain name system (DNS) host name with domain name suffix, the short DNS host name, or an asterisk (*). An asterisk permits any of the other three values as well as the current value of a Dynamic Host Configuration Protocol (DHCP) address in a web client request for a web application resource. Web application resources include servlets, JSP files, or HTML pages.
HostAlias.port.description=Specifies the port where the virtual host accepts web client requests. Specify a unique port value in conjunction with the host name to avoid conflicts with other virtual hosts. The port number default is port 80, which is the default web server port. Assign another value to use the internal HTTP transport capability of the application server, or to use another port that you might have assigned as the web server port. For example, create a new virtual host and assign port 9085 to serve application resources over the internal HTTP transport of the application server using port 9085.
IndirectLookupNameSpaceBinding.description=Use this page to configure a name binding of an object which can be looked up using JNDI.
IndirectLookupNameSpaceBinding.initialContextFactory.description=Specifies the class name of the initial context factory used to obtain a JNDI initial context. If the field is left blank, the initial context factory com.ibm.websphere.naming.WsnInitialContextFactory is used to obtain the initial JNDI context.
IndirectLookupNameSpaceBinding.jndiName.description=Specifies the name used to look up the target object from the initial context.
IndirectLookupNameSpaceBinding.providerURL.description=Specifies the provider URL string needed to obtain a JNDI initial context.
IndirectNameSpaceBinding.other.ctxproperties.description=Specifies a list of name-value pairs (property settings) for the indirect lookup name binding. The property settings are passed to the javax.naming.InitialContext constructor used to obtain the initial JNDI context required for the indirect lookup. The property settings apply to nodes at version 6.1 or later.
Library.classpath.description=Specifies a class path that contains the JAR files for this library. Press Enter to separate class path entries. Entries must not contain path separator characters (such as ';' or ':').  Class paths can contain variable (symbolic) names that can be substituted using a variable map.
Library.description=Use this page to define a container-wide shared library that can be used by deployed applications.
Library.description.description=Specifies an optional description for this shared library.
Library.isolatedClassloader.description=Specifies whether an isolated class loader should be used for this shared library.
Library.name.description=Specifies the name of the shared library.
Library.nativepath.description=Specifies an optional path to any native libraries (DLL or SO files) required by this shared library.
Library.scope.description=Specifies the scope of the shared library.  This value indicates the configuration location for the configuration file.
MimeEntry.description=Use this page to map a MIME type to one or more file extensions.
MimeEntry.extensions.description=Specifies file extensions that map to the MIME type.
MimeEntry.type.description=Specifies a MIME type that maps the associated file name extensions.
NameSpaceBinding.bindingType.description=Specifies the type of binding. Options are String, EJB, CORBA, and Indirect.
NameSpaceBinding.create.new.description=Use this wizard to configure a new name space binding.
NameSpaceBinding.description=Use this page to configure a name binding of a constant string value, an enterprise bean, a CORBA CosNaming Naming Context or CORBA leaf node object, or an object that can be looked up by using JNDI.
NameSpaceBinding.name.description=Specifies a name that uniquely identifies this configured binding.
NameSpaceBinding.nameInNameSpace.description=Specifies a name for this binding in the name space. It is a simple or compound name relative to the portion of the name space where this binding is configured.
NameSpaceBinding.nameInNameSpaceScoped.displayName=Name in name space relative to lookup name prefix '{0}'
NameSpaceBinding.namingContext.description=Specifies the scope of the configured binding. It is the configuration location for the namebindings.xml file.
NameSpaceBinding.new.step3.other.propDescription.description=Specifies an annotation for the property setting. Applies to nodes at version 6.1 or later.
NameSpaceBinding.new.step3.other.propName.description=Specifies a unique name (or key) for the property. Applies to nodes at version 6.1 or later.
NameSpaceBinding.new.step3.other.propValue.description=Specifies the value that is paired with the property name. Applies to nodes at version 6.1 or later.
Node.description=Use this page to manage nodes in the application server environment. A node corresponds to a physical computer system with a distinct IP host address. The following table lists the managed and unmanaged nodes in this cell. The first node is the deployment manager. Add new nodes to the cell and to this list by clicking Add Node.
Node.discoveryProtocol.description=Specifies the protocol that the node follows to retrieve information from a network.
Node.managed.description=Use this page to view or change the configuration for a managed node. A managed node is a node with an application server and a node agent that belongs to a cell.
Node.name.description=Specifies a logical name for the  node. The name must be unique within the cell.
Node.platform.description=Specifies the operating system of the platform that this unmanaged node represents.
Node.properties.description=Use this page to specify arbitrary configuration properties for the node, and a string value for each property.
Node.shortName.description=Specifies the short name of the node. This name can contain one to eight uppercase alphanumeric characters, but it cannot start with a numeral. This field only applies to the z/OS(R) platform.
Node.unmanaged.description=Use this page to view or change the configuration for an unmanaged node. An unmanaged node is a node defined in the cell topology that does not have a node agent running to manage the process. Unmanaged nodes are typically used to manage web servers.
OtherContextProperty.collection.description=Use this page to specify context properties for the indirect lookup name binding.  The properties may be standard JNDI properties or properties specific to the initial context factory being used to obtain the initial JNDI context.  The set of properties should not include a provider URL or initial context factory class name.  The property settings are used only by nodes at version 6.1 or later.
OtherContextProperty.description.description=Specifies the other context property description.
OtherContextProperty.detail.description=Use this page to edit a context property for the indirect lookup name binding.  The property may be a standard JNDI property or a property specific to the initial context factory being used to obtain the initial JNDI context.  The property should not be a provider URL or an initial context factory class name.
OtherContextProperty.name.description=Specifies the other context property name.
OtherContextProperty.value.description=Specifies the other context property value.
Property.description=Use this page to specify an arbitrary name and value pair. The value that is specified for the name and value pair is a string that can set internal system configuration properties.
Property.description.description=Specifies a description of the name and value pair. The description should help to differentiate this pair for other defined pairs.
Property.name.description=Specifies the name of the property.
Property.required.description=Specifies an optional attribute that determines whether this property must have a value.
Property.validationExpression.description=Specifies a value that the administrative console and some host tools use to validate the contents of the value of this property.
Property.value.description=Specifies the value that is paired with the specified name.
PropertySet.description=Use this page to define additional properties for some specialized purpose.
PropertySet.description.description=Some runtime components accept additional properties that can be used for further customization.  See documentation for the runtime component to determine if special properties can be used.
PropertySet.properties.description=Some runtime components accept additional properties that can be used for further customization.  See documentation for that runtime component to determine if special purpose properties can be used.
StringNameSpaceBinding.description=Use this page to configure a name binding of a constant string value.
StringNameSpaceBinding.stringToBind.description=Specifies the string to be bound into the name space.
Transport.address.description=Specifies the address for the transport.
Transport.description=Use this page to configure server processes that support various transports for IPC. Web client processes connect to the server using one of the supported transports.
Transport.external.description=Specifies whether this transport is for internal or external use.
Transport.properties.description=Specifies special configuration properties for the transport. Each type of transport can contain custom properties specified by the transport provider. See the documentation for each transport type to determine if there are special transport property names and what the possible values are for each special property.
Transport.sslConfig.description=Specifies the Secure Socket Layer (SSL) settings type for connections between the WebSphere(R) plug-in and application server. The options include one or more SSL settings defined in the Security Center; for example, DefaultSSLSettings, ORBSSLSettings, or LDAPSSLSettings.
Transport.sslEnabled.description=Specifies whether to protect connections between the web server plug-in and the application server with Secure Socket Layer (SSL). The default is not to use SSL.
TypedProperty.description=Specifies a custom property value.  Check the runtime component documentation to determine if additional custom properties are available for a specific component.
TypedProperty.type.description=Specifies the fully qualified Java type for this property, such as java.lang.Integer or java.lang.Byte.
VariableSubstitutionEntry.description=Use this page to define substitution variables. Variables specify a level of indirection for some system-defined values, such as file system root directories. Variables have a scope level, which is either server, node, cluster, or cell.  Values at one scope level can differ from values at other levels. When a variable has conflicting scope values, the more granular scope value overrides values at greater scope levels. Therefore, server variables override node variables, which override cluster variables, which override cell variables.
VariableSubstitutionEntry.description.description=Specifies an optional description for your administrative records.
VariableSubstitutionEntry.symbolicName.description=Specifies the symbolic name that represents a physical path or URL root.
VariableSubstitutionEntry.value.description=Specifies the absolute path that the symbolic name represents.
VirtualHost.aliases.description=Use this page to edit, create, or delete a domain name system (DNS) alias by which the virtual host is known.
VirtualHost.description=Use this page to create a virtual host with a unique set of web access ports. Such a configuration lets a single host machine resemble multiple host machines. Each virtual host has a logical name and a list of one or more domain name system (DNS) aliases by which it is known.
VirtualHost.mimeTypes.description=Use this page to edit, create, or delete entries in the collection of MIME type extension mappings defined for the virtual host. If MIME entries are not specified at the web module level, these MIME entries apply.
VirtualHost.name.description=Specifies a logical name used for configuring web applications to a particular host name. The default virtual host is suitable for most simple configurations.
add.node.connection.description=Specifies required properties for connecting to the application server being federated.
add.node.connector.description=Specifies the type of JMX connector used to perform the operation
add.node.create.description=Use this page to add either a managed or an unmanaged node.
add.node.description=Use this page to identify a stand-alone application server process that is running. Start the application server, if necessary, or add the node from the command line by running the addNode command from the bin directory of the stopped application server profile.
add.node.host.description=Specifies the network name of the node to be added to the cell. This value can be an IP address, a domain name server (DNS) name that resolves to an IP address, or the word, localhost, if the application server is running on the same machine as the deployment manager. The application server process must be running at the IP address identified by the host field.
add.node.include.apps.description=Specifies whether to copy the applications installed on the remote instance into the cell. Applications with the same name as applications that currently exist in the cell are not copied.
add.node.include.buses.description=Specifies whether to copy the service integration bus configuration of the remote node into the cell.  If the cell already contains a bus with the same name as any bus at the remote node, the add node command fails.
add.node.local.password.description=Specifies the password for the application server user ID entered previously.
add.node.local.user.description=Specifies the user ID and password for the application server. If security is enabled at the node you are adding, enter a valid user ID and password to enable the deployment manager to communicate with the remote application server process. If security is not enabled at the application server, no entry is required.
add.node.managed.description=Specifies the creation of a managed node. A managed node contains an application server process that runs within the deployment manager cell. The managed node is associated with a node agent process that maintains the configuration for the node and controls its operation. Choosing this option results in running the add node utility to federate an existing stand-alone application server.
add.node.options.description=Specifies whether to copy stand-alone applications and buses into the federated node. 
add.node.password.description=Specifies the password for the deployment manager user ID entered previously.
add.node.port.description=Specifies the port number of the JMX connector on the application server process to be added to the cell. The default SOAP connector port is 8880.
add.node.replicated.description=Specifies to replace a damaged node in the cell. First, create a new profile to replace the damaged node and give it the same profile and node names. Then use this option to replace the damaged node in the cell with the new node.
add.node.replicated.page.description=Use this page to recover an existing node that is no longer functioning. First, create a new profile to replace the damaged node and give it the same profile and node names. Then, use this option to replace the damaged node in the cell with the new node. This page is the equivalent of adding the node from the command line by running the addNode command with the -asExistingNode option from the bin directory of the stopped application server profile.
add.node.rmi.port.description=Specifies the port number of the RMI connector on the instance to be added to the cell. By default, this is port 9809.
add.node.run.as.service.description=Specifies that the node agent is to run as a Windows(R) service.
add.node.service.confirm.password.description=Specifies a confirmation password for the user ID.
add.node.service.description=Use this page to let Windows(R) Services run the node agent. The service can start or stop the node agent, as well as provide startup and recovery actions.
add.node.service.password.description=Specifies the password for the local operating system user ID to be used to run the node agent service.
add.node.service.user.description=Specifies a local operating system user ID and password to run the node agent service. If you do not enter a user ID, the service runs by using the local system account. If you provide a user ID, it must have the 'Log on as a service' Windows(R) logon correct.
add.node.starting.port.description=Specifies whether to use the default ports or to start with a specified port number for the node agent process. Additional node agent ports are numbered sequentially after the starting port number.
add.node.unmanaged.description=Specifies the creation of an unmanaged node. An unmanaged node represents a node in the topology that does not have an application server process or a node agent process. Unmanaged nodes are for other server processes, such as web servers that exist on their own node in the topology.
add.node.user.description=Specifies the user ID and password for the deployment manager. The user ID and password are required since security is enabled for the deployment manager. Enter a valid user ID and password to enable the remote application server process to communicate with the deployment manager.
environment.label.description=Description
environment.nodeproperties.description=Use this page to view read-only installation properties for this node. These properties provide information about the capabilities of the node that are collected during product installation, such as the operating system name, architecture and version, or WebSphere(R) Application Server product levels that are installed on the node.
globalBiDiTextDirection.description=Specifies how bidirectional text is displayed and entered for all users.
globalEnableBiDi.description=Specifies whether bidirectional support is enabled in the administrative console for all users.
plugincfg.description=Click OK to update, or click Overwrite to generate a new plug-in configuration file.
plugincfg.help=Use this page to create or update a global plug-in configuration file for a cell. The settings in this configuration file are based on the topology of the cell. The web server plug-in configuration file controls whether an application server or the web server handles user requests. You must regenerate this global plug-in configuration file whenever you change the configuration settings for an application server, cluster, web container transport, or virtual host alias that is contained in the cell. You must also regenerate this file whenever you add a new application server, cluster, web container transport, or virtual host alias to the cell. The global plugin-cfg.xml file is placed in the %was_profile_home%/config/cells directory. This configuration file includes the URIs for all of the applications that are deployed in this cell. If your web server is located on a remote machine, you must manually move this plug-in configuration file to that machine.
