Creating a JAX-WS-enabled WebSphere server
JAX-WS web services can only be targeted to servers that support the JAX-WS runtime environment, such as IBM® WebSphere® Application Server Liberty or WebSphere Application Server V7.0 or later.
Before you begin
- IBM WebSphere Application Server Liberty
- WebSphere Application Server Version 7.0 or later.
About this task
Procedure
- From the File menu, select New > Other > Server > Server > Next.
- Select the appropriate version of WebSphere Application Server as the server type, and click Next.
- On the WebSphere server settings page, select the server profile that is associated with your WebSphere Application Server, and enter a server name.
- Click Finish.
Results
To see the server you have created in the workspace, from the Window menu click Show view > Other > Server > Servers > Ok or open the Java™ EE perspective. By double-clicking the server you can view or modify many of the server's settings.
What to do next
If you are using a secured WebSphere Application Server, there are
a couple of tasks you may need complete in order to use the web services
tools:
- Before using the Web Services Explorer, generating sample JSPs, or deploying an Axis Web service, you must configure the workbench to communicate with a server using Secure Sockets Layer (SSL). Information about this task can be found here: Problems working with a secured server using SSL connections.
- If you want to use the Web services wizard to retrieve an HTTPS WSDL or if you want to use the Web Services Explorer against a secured WebSphere Application Server, you must complete the steps in: Configuring the IBM JRE to talk to a secured WebSphere Application Server
Tip: [WebSphere Application Server traditional] By default the
Minimize application files copied to the server option has been turned on in
the server editor for performance reasons. Generally speaking this means you will not be able to see
the application deployment descriptor files from the WebSphere Application Server administrative console. In the case of web services, both
Publish WSDL files and Provide HTTP endpoint URL information links
will be missing from the console because the WSDL,
ibm-web-bnd.xmi, ibm-web-ext.xmi, and web.xml
will not be in the *.war file copied to the server profile directory. This may
cause problems if the WebSphere Application Server
administrator does not have access to the files residing in the development workspace. To disable
this option, double-click the server in the Servers view, and clear the Minimize
application files copied to the server check box. This will have a small performance
impact on the server but will make all the required files available to the administrator.