createWSNServicePoint command

Use the createWSNServicePoint command to create a new WS-Notification service point.

You can create a new WS-Notification service point by using the wsadmin tool as described in this topic, or by using the administrative console as described in 建立新的 6.1 版 WS-Notification 服務點 and 建立新的 7.0 版 WS-Notification 服務點.

如果要執行這個指令,請使用 wsadmin Scripting 用戶端AdminTask 物件

[IBM i][IBM i]wsadmin Scripting 用戶端是從 Qshell 執行. [IBM i]如需相關資訊,請參閱利用 wsadmin Script 配置 Qshell 來執行 WebSphere Script.

服務整合匯流排指令有指令行說明:

  • 如需可用的 WS-Notification 指令清單,以及每個指令的簡要說明,請在 wsadmin 提示下,輸入下列指令:

    print AdminTask.help('WSNotificationCommands')

  • 如需給定指令的概觀說明,請在 wsadmin 提示下,輸入下列指令:

    print AdminTask.help('command_name')

使用指令之後,請利用下列指令,儲存對主要配置所做的變更:

AdminConfig.save()

Purpose

匯流排成員上有 WS-Notification 服務點,意指這個匯流排成員會顯現 WS-Notification Web 服務,並使得這個 WS-Notification 服務之通知分配管理系統、訂閱管理程式和發佈者登錄管理程式的 Web 服務端點,都會顯現在服務點所相關聯的匯流排成員上。WS-Notification 應用程式利用這些端點來與 WS-Notification 服務互動。

This command creates the following resources:
  • It creates a new WS-Notification service point on a WS-Notification service.
  • For a Version 7.0 WS-Notification service point, it causes Web service endpoints for the three roles played by the broker to be exposed on the bus member.
  • For a Version 6.1 WS-Notification service point, it creates the three service integration bus inbound ports that represent the three roles played by the broker, it creates a service integration bus endpoint listener if required, and it connects the new or existing endpoint listener to the service integration bus with which the WS-Notification service is associated.
How you use this command depends upon the topology in which the command is being run. The topology determines the conditional parameters that you provide:
  • bus member type (server or cluster)
  • endpoint listener (create new or use existing) for Version 6.1 WS-Notification service points
If the service type is Version 7.0, do not specify the following optional parameters, which relate to JAX-RPC configuration:
-eplName
-eplURLRoot
-eplWSDLServingURLRoot
If the service type is Version 6.1, do not specify the following optional parameters, which relate to JAX-WS configuration:
-transportURLRoot
-transportSoapVersion
-jaxwsHandlerListNB
-jaxwsHandlerListSM
-jaxwsHandlerListPRM

You can only create service points for Version 7.0 WS-Notification services on WebSphere® Application Server 7.0 版或更新版本 bus members. If the bus member is a cluster, then all servers in the cluster must be WebSphere Application Server 7.0 版或更新版本 application servers.

You can create service points for Version 6.1 WS-Notification services on WebSphere Application Server 6.1 版或更新版本 application servers.

Target object

WSNService

Required parameters

-name

Conditional parameters

Choose either a server or a cluster for the associated bus member:

-server
Name of the server on which the WS-Notification service point is created.
  • If you specify the copyServicePoint parameter, then you need not specify this parameter.
  • If this parameter is used then the node parameter must be specified, and the cluster parameter must not be specified.
-node
Name of the node on which the server is located.
  • If you specify the copyServicePoint parameter, then you need not specify this parameter.
  • If this parameter is used then the server parameter must be specified, and the cluster parameter must not be specified.
-cluster
Name of the cluster on which the WS-Notification service point is created.
  • If you specify the copyServicePoint parameter, then you need not specify this parameter.
  • If this parameter is used then the server and node parameters must not be specified.

For a Version 6.1 WS-Notification service, choose either to configure a new endpoint listener or use an existing one:

-eplName
Name of an endpoint listener.
  • If you specify the copyServicePoint parameter, then you need not specify this parameter.
  • If this endpoint listener has already been defined on the chosen server or cluster, then the eplURLRoot and eplWSDLServingURLRoot parameters should not be specified. Otherwise, the eplURLRoot and eplWSDLServingURLRoot parameters must both be specified.
只指定 6.1 版 WS-Notification 服務的這個參數。
-eplURLRoot
Root of the externally visible endpoint address URL for web services that are accessed through this endpoint listener.
  • If you specify the copyServicePoint parameter, then you need not specify this parameter.
  • If the endpoint listener has already been defined on the chosen server or cluster, then this parameter should not be specified.
只指定 6.1 版 WS-Notification 服務的這個參數。
-eplWSDLServingURLRoot
Root of the externally visible HTTP URL where the WSDL file associated with this endpoint listener is located. In most circumstances this is http://host_name:port_number/SIBWS. For more information, see Creating a new endpoint listener configuration or createSIBWSEndpointListener command.
  • If you specify the copyServicePoint parameter, then you need not specify this parameter.
  • If the endpoint listener has already been defined on the chosen server or cluster, then this parameter should not be specified.
只指定 6.1 版 WS-Notification 服務的這個參數。

For a Version 7.0 WS-Notification service, configure the web service endpoint:

-transportURLRoot
Root of the externally visible endpoint address for the WS-Notification service point, in the following format:
protocol://host_nameport_number/service_location
where protocol is either http or https. For example:
http://myhostname:9080/ctx123/mySvc
You can use this parameter to associate a particular external web address with the WS-Notification service when you publish WSDL to a compressed file through the administrative console. Note that this address might not be the same as the address at which the WS-Notification service is exposed. This address is required when the WS-Notification service is accessed through a proxy.
If you do not specify this parameter, the underlying JAX-WS implementation creates an appropriate URL based on information provided as part of the service point installation process.
If you specify the copyServicePoint parameter, then you need not specify this parameter.
This attribute is the equivalent of the eplURLRoot parameter for service points created on Version 6.1 WS-Notification services. 只指定 7.0 版 WS-Notification 服務的這個參數。
-transportSoapVersion
允許的值如下:1.1(SOAP 1.1,預設值)和 1.2 (SOAP 1.2)。
If you specify the copyServicePoint parameter, then you need not specify this parameter.
只指定 7.0 版 WS-Notification 服務的這個參數。

Copy the configuration from an existing WS-Notification service point definition:

-copyServicePoint
The name of an existing service point configured on the WS-Notification Service from which the other configuration attributes are copied. If you specify this parameter, then you only have to specify the name parameter. All other values are taken from the nominated existing service point.

Optional parameters

-description
-jaxwsHandlerListNB
If you specify the copyServicePoint parameter, then you need not specify this parameter.
只指定 7.0 版 WS-Notification 服務的這個參數。
-jaxwsHandlerListSM
If you specify the copyServicePoint parameter, then you need not specify this parameter.
只指定 7.0 版 WS-Notification 服務的這個參數。
-jaxwsHandlerListPRM
If you specify the copyServicePoint parameter, then you need not specify this parameter.
只指定 7.0 版 WS-Notification 服務的這個參數。

Examples

In the following examples, the WS-Notification service point uses the WS-Notification service newService created in the example from topic "Creating a new WS-Notification service by using the wsadmin tool".

Create a Version 6.1 WS-Notification service point on cluster1 that uses the existing endpoint listener SIBWSHTTPChannel1:

newServicePoint = AdminTask.createWSNServicePoint(newService, 
["-name", "newServicePoint", "-cluster", "cluster1", "-eplName", "SIBWSHTTPChannel1"] )

Create a Version 6.1 WS-Notification service point on server1 on node1 and create a new endpoint listener that uses SOAP over HTTP on channel 1, where the host address of the server is http://myHost:9080:

newServicePoint = AdminTask.createWSNServicePoint(newService, 
["-name", "newServicePoint", "-node", "node1", "-server", "server1", "-eplName", "myNewEPL", 
"-eplURLRoot", "http://myhost:9080/wsn", "-eplWSDLServingURLRoot", "http://myhost:9080/sibws"] )

Create a Version 7.0 WS-Notification service point on server1 on node1 (minimum set of parameters):

newServicePoint = AdminTask.createWSNServicePoint(newService, 
["-name", "newServicePoint", "-node", "node1", "-server", "server1", 
"-transportURLRoot", "http://myhost:9080/myWSN"] ) 

Create a Version 7.0 WS-Notification service point on server1 on node1 (full set of parameters):

newServicePoint = AdminTask.createWSNServicePoint(newService, 
["-name", "newServicePoint", "-node", "node1", "-server", "server1", 
"-transportURLRoot", "http://myhost:9080/myWSN", "-transportSoapVersion", "1.1", 
"-jaxwsHandlerListNB", "nbList", "-jaxwsHandlerListSM", "smList", "-jaxwsHandlerListPRM", "prmList"] )

指出主題類型的圖示 參照主題



時間戳記圖示 前次更新: July 9, 2016 11:13
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rjwsn_cli_wsnservpt_new
檔名:rjwsn_cli_wsnservpt_new.html