Don WebSphere Application Server 8.5.5 JAX-WS, duba sarrafawa biyu na kewaye kafin ka dogara da adireshi a cikin mahallin buƙatar abokin ciniki. Kaddarar IBM a matakin JVM com.ibm.ws.websvcs.transport.enableProxyTunnel tana false ta tsohuwa; adireshin kowane abokin ciniki baya kunna rami. Ƙimar jigilar HTTP na saitin manufa kuma tana wuce ƙimar shirye-shirye, kuma waɗannan suna wuce kaddarorin tsarin JVM.

Don zaɓaɓɓen tashar da take akwai, IBM ta rubuta wannan saitin na kowane abokin ciniki kafin kira:

import javax.xml.ws.BindingProvider;

BindingProvider binding = (BindingProvider) servicePort;
binding.getRequestContext().put("https.proxyHost", "proxy.example");
binding.getRequestContext().put("https.proxyPort", "8080");

Maɓallan HTTPS suna aiki ga ƙarshen wuraren HTTPS; don HTTP yi amfani da maɓallan IBM HTTP da suka dace. Ƙarshen SOAP na jama'a da aka yarda zai iya amfani da adireshin HTTP daga jerin wakilan HTTP kawai bayan manufar da ta dace da sarrafa rami sun yarda kuma ba a saita asusun wakili a waɗannan matakan ba. Tabbatar da wakili yana da kaddarorin HTTP/HTTPS proxyUser da proxyPassword daban, masu zaman kansu daga shaidar sabis na SOAP.

Waɗannan ƙarin abubuwan WebSphere ne. Taswirar BindingProvider a cikin Metro, CXF ko wata aiwatarwa baya sa waɗannan igiyoyin ɗaukar nauyi.

Riƙe hanyoyi daban-daban na lokaci ɗaya akan abubuwan abokin ciniki da aka tsara yadda ya kamata maimakon sake rubuta mahallin tasha da aka raba yayin da ake kira. Wannan yana iyakance adireshin ga ainihin abokin ciniki ba tare da ɗaukar duk sarrafa JVM da ke kewaye a matsayin na gida ba.

Labarai masu alaƙa