You need to have WSO2 EI tooling installed to create a new inbound endpoint or to import an existing inbound endpoint via tooling. For instructions on installing WSO2 EI tooling, see Installing WSO2 EI Enterprise Integrator Tooling.
Follow the steps below to create a proxy service.
- In Eclipse, click the Developer Studio menu and then click Open Dashboard. This opens the Developer Studio Dashboard.
- Click Proxy Service on the Developer Studio Dashboard.
- Select Create a New Proxy Service and click Next.
- Type a unique name for the proxy service and specify the proxy type (see below).
- Do one of the following:
- To save the proxy service in an existing ESB Config project in your workspace, click Browse and select that project.
- To save the proxy service in a new ESB Config project, click Create new ESB Project and create the new project.
- If you specified a proxy type that requires that you enter the target endpoint (the endpoint that represents the actual service), do one of the following:
- If you know the URL of the endpoint, select Enter URL and type it in the text box.
- If you want to use an endpoint you've already defined in this workspace, select Predefined Endpoint and select it from the list.
- If you want to use an endpoint in the registry, select Pick from Registry, and then either type the endpoint's registry key or click Browse, click Registry, and navigate to the endpoint in the registry.
- Fill in the advanced configuration based on the proxy service type you specified:
- Transformer Proxy: Transforms all the incoming requests using XSLT and then forwards them to a given target endpoint. Specify the target endpoint as described in the previous step, and then specify the location of the XSLT you want to use to transform requests, either by typing the path or by clicking Browse and navigating to the XSLT, which can be a file in the workspace or registry or can be a local entry. If you also want to transform the responses from the backend service, click Transform Responses.
- Log Forward Proxy: Logs all the incoming requests and forwards them to a given endpoint. It can also log responses from the backend service before routing them to the client. Specify the log level for requests and responses, where Simple logs
To, From, WSAction, SOAPAction, ReplyTo, MessageID, and any properties, and Full logs all attributes of the message plus the SOAP envelope information.
- Pass Through Proxy: Forwards messages to the endpoint without performing any processing on them. This proxy service is useful as a catch-all, so that messages that do not meet the criteria to be handled by other proxy services are simply forwarded to the endpoint. When you select this proxy service type, you just specify the target endpoint as described in the previous step.
- WSDL Based Proxy: A proxy service that is created from the remotely hosted WSDL of an existing web service. The endpoint information is extracted from the WSDL. In the URI field, enter the URL and URN of the WSDL. The URL defines the host address of the network resource (can be omitted if resources are not network homed), and the URN defines the resource name in local namespaces. For example, if the URL is
and the URN is
/pub/ADSL/, you would enter
for the URI. To ensure that the URI is valid, click Test URI. You then enter the service name and port of the WSDL. Lastly, if you want to publish this WSDL, click Publish Same Service Contract.
- Secure Proxy: Uses WS-Security to process incoming requests and forward them to an unsecured backend service. Specify the target endpoint as described in the previous step, and then specify the key of the security policy or click Browse and select it from the registry.
- Custom Proxy: A custom proxy service in which you customize all the sequences, endpoints, transports, and other QoS settings by adding them to the mediation workflow after the proxy service is created.
- Click Finish. The proxy service is created in the src/main/synapse-config/proxy-service folder under the ESB Config Project you specified, and the proxy service appears in the editor. Click its icon in the editor to view its properties.
Follow these steps to import an existing proxy service from an XML file (such as a Synapse configuration file) into an ESB Config project.