Configuring a workspace for web services development
Although you can begin web services development immediately upon creating a workspace, you might find it convenient to configure your workspace to optimize your development experience.
About this task
After you set up your workspace, you can begin to develop web services by creating or importing the resources that your web service or web service client will use.
- Setting web services preferences
Before you begin developing web services or clients, you can optimize the workbench for web services development by setting a variety of preferences. - Setting the level of WS-I compliance
The web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, 1.2, 2.0, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), the WS-I Attachments Profile 1.0 (WS-I AP), and the WS-I Basic Security Profile 1.0 (WS-I BSP). You can choose to make your web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols are not WS-I compliant. - 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. - Creating a WebSphere Application Server and Web project
If you plan to create a web service that uses WebSphere Application Server as its server, the required version of WebSphere Application Server must be installed and a server created before you begin creating your web service. - Creating a Liberty server and a project
You can create a Liberty server, and then choose an OSGi project, an Enterprise JavaBeans (EJB) project, or a web project as the target project. - Creating a JMS server
In order to create a web service that uses JMS transports, you need to first create and configure a server that can support JMS. - Configuring the IBM JRE to talk to a secured WebSphere Application Server
Use these steps 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. If you encounter an error similar to Error opening socket: javax.net.ssl.SSLHandshakeException: unknown certifcate this task resolves the issue. This error occurs because WebSphere Application Server uses a security certificate for negotiating secured connections that other JRE-based applications do not normally share. - Problems working with a secured server using SSL connections
How to work around the SSLSocketFactory and SSLHandshakeException error messages when you are trying to communicate to a secured server by using a Secure Sockets Layer (SSL) connection within the workbench.
Parent topic: Developing web service applications

