Make note of the ports that this deployment manager profile uses, because you will need the port number later when you add nodes to this deployment manager.
请注意该部署管理器概要文件使用的端口，因为之后您将需要该端口数，添加其它节点至部署管理器。
If your install's port number is different, or you want to use a different queue manager, you need to specify its port.
如果您的安装端口不同，或想另外用队列管理器，则需重新指定端口。
Changing the default port and securing the Lifecycle Manager uri are two additional levels of security that can be applied.
更改默认端口和保护LifecycleManagerURI是另外两个可以应用的安全性级别。
You now have a connection c1 in the free pool, so the connection Manager will take this connection out of the pool and make it available to the listener port.
现在，空闲池中含有连接c1，这样ConnectionManager将从该池中取出此连接，并将其提供给侦听器端口。
Check the Optim Performance Manager repository server log db2pesrv.log for the following message to identify the right port.
检查Optim PerformanceManager信息库服务器日志db2pesrv . log，寻找以下消息，然后识别正确的端口。
Note: By default, the Deployment Manager runs on port 8879 for SOAP connections.
注意：默认情况下，DeploymentManager运行在端口 8879 上，以获得 SOAP 连接。
They will need the MIB, and you will need the host name, port, and community string for the SNMP Manager.
他们需要这个MIB，而您需要SNMPManager的主机名、端口和社区字符串。
The WebSphere MQ information, such as queue manager name, host, channel, and port should correspond to the queue manager Settings configured earlier.
WebSphereMQ信息(如队列管理器名称、主机、通道和端口)必须与以前配置的队列管理器设置相对应。
The first port (default 60000) is the UDP port on which the Extended Insight controller server (part of the Optim Performance Manager repository server) is running.
第一个端口(默认端口为60000)是运行ExtendedInsight控制器服务器的UD p端口(Extended Insight控制器服务器是Optim PerformanceManager信息库服务器的一部分)。
Port (shows default of queue manager) : 1414.
Port(显示队列管理器的缺省端口)：1414。
These parameters may have to be changed to match your Message Broker installation (Queue Manager name is set to QM1 and Listener port set to 1414).
可能必须更改这些参数，以与您的MessageBroker安装匹配（QueueManagername设置为QM1，Listenerport 设置为 1414）。
It must match the name, hostname, and port used by the MQ queue manager to send messages to the bus.
它必须与队列管理器所使用的名称、主机名和端口相匹配，以将消息发送到总线。
It will need to match the name, hostname, and port used by the queue manager to receive messages from the bus.
它需要与队列管理器所使用的名称、主机名和端口相匹配，以接收来自总线的消息。
The file contains information such as the hostname, port, and name of the target queue manager, as well as more advanced configuration information like the SSL attributes that should be used.
该文件包含的信息有目标队列管理器的主机名、端口和名称，以及更高级的配置信息，如应该使用的SSL属性。
JMS request queue Connection Factory: Used by the listener port to connect to the MQ queue manager that hosts the request MQ queue.
JMS请求队列连接工厂：由侦听器端口用于连接到承载请求mq队列的mq队列管理器。
Set the port to the SOAP port number of the deployment manager (to find this, open the admin console, and look at System Administration => Deployment manager => Ports => SOAP_CONNECTOR_ADDRESS).
将端口 port设置为部署管理器的SOAP 端口号（为了找到这个，打开admin控制台，然后查看SystemAdministration =>Deploymentmanager =>Ports => SOAP_CONNECTOR_ADDRESS）。
Like the PROVIDER_URL value used earlier, if your install is running on a different machine or your queue manager is running on a different port, you will need to modify these Settings in your script.
如同以上的provider_url值，如果您是在不同的机器上安装或您的队列管理器在不同的端口运行，则需要在脚本中修改这些设置。
In the examples shown below, the deployment manager is assumed to be running on the default port on the same host as the session in which the script is being executed.
在下面的示例中，假定部署管理器在与执行脚本的会话相同的主机的缺省端口运行。
The example administrative client connects to the MBean server through the deployment manager SOAP port.
示例管理客户端通过部署管理器SOAP端口连接到MBean服务器。
Set deployment manager hostname and port, set the administrative username and password, and then click next.
设置部署管理器主机名称和端口，设置管理用户名和密码，然后单击next。
Set deployment manager hostname and port and set the administrative username and password, click Next.
设置部署管理器主机名称和端口，设置管理用户名和密码，然后单击Next。
If the listener port is restarted, it will once again ask the connection manager for a connection to the queue manager.
如果重新启动侦听器端口，它会再次请求ConnectionManager，以获得到队列管理器的连接。
Update the Queue manager, Port, and Channel to match the secured server connection defined in WebSphere MQ.
更新队列管理器、端口和通道以与WebSphereMQ中定义的安全服务器连接匹配。
If this is not the case in your environment, then you must supply the -host and -port parameters to enable the admin client to connect to the deployment manager.
如果您的环境中不是这样，则必须提供- host和- port参数，以便管理客户端连接到部署管理器。
The port number on which the target WebSphere MQ queue manager is listening for inbound communication requests.
目标WebSphereMQ队列管理器在其上侦听入站通信请求的端口的端口号。
This command creates a QueueConnectionFactory that accesses the queue manager, SSLQMGR, using the client (network-based) transport on a machine localhost via port 1414 and channel SSL.SVRCONN.
该命令创建了一个QueueConnectionFactory，它通过端口1414和通道ssl . SVRCONN使用机器本地主机上的客户机(基于网络的)传输来访问队列管理器SSLQMGR。
On the deployment manager, the specdelivery port number in the supplier.jar dirctory needs to be updated.
在部署管理器上，需要更新supplier.jar目录中的 specdelivery 端口号。
Port - the port number that the queue manager is listening on.
port——队列管理器侦听的端口号。
The paper proposes the solution according to limitation of current information manager system of port, and the practical methods is also discussed.
本文针对当前码头管理系统存在的问题，提出解决方案，并具体给出了系统的实现方法。
The paper proposes the solution according to limitation of current information manager system of port, and the practical methods is also discussed.
本文针对当前码头管理系统存在的问题，提出解决方案，并具体给出了系统的实现方法。
应用推荐