I have publish one webservice on server let say on abc.com server. now more than 10 client subscribe for this webservice.
Now I want to shift same web service to server xyz.com and want to close server abc.com.
So without updating client how can i make this move successful so my client Web Service do not need to update anything from their side.
You likely can't. Most users will have client side configuration that will need to be changed to point to the new url.
If you control the dns entries, you could decommission server abc.com and point it's old dns entry to the same server as xyz.com.
Related
According to this thread, the endpoint is the URL where your service can be accessed by a client application.
But, it sounds to me like a kind of server. In that case, an endpoint will be always an URL? what is the difference between an endpoint and a server?
An endpoint is a URL which allows you to access a (web) service running on a server. A server(program) may actually host multiple such services exposing them through different endpoint.
e.g. To access twitter search API, https://api.twitter.com/1.1/search/tweets.json is the endpoint. But the same server also has another endpoint https://api.twitter.com/oauth/authenticate for authentication. Both the endpoints are hosted on the same server which runs on a machine with domain name twiter.com
server is something who host your side/data or run multiple services, like php, mysql, etc
end point is where something points like we say end point of phpmyadmin, and might be its a end point of some api.
api.example.com/getusers
We have a strange problem with our ADFS setup but I can't understand why it's happening.
ADFS is used to connect to Sharepoint that is hosted by a cloud provider. Their domain is called cloudsp.eu. Our internal domain is called "hobnobs.internal.eu"
We have a Web proxy with a public DNS record of "login.cloudsp.eu". The WAP has a published Web Application configured as with External and Internal URLs as https://login.cloudsp.eu.
The internal ADFS Federation service name is login.cloudsp.eu
It also has a hosts entry file for login.cloudsp.eu that points to our internal ADFS server so that it can resolve the name
Our internal DNS then also has an empty DNS zone called login.cloudsp.eu configured to resolve to the internal ADFS server so that clients on the internal network do not resolve to the WAP.
Now, this all works well. Internal clients get SSO without having to go via the WAP and external clients hit the WAP and are then redirected to the ADFS of the cloud provider where they have to authenticate with their Sharepoint credentials.
The problem is this :-
An internal clients connects and authenticates via SSO to ADFS.
They then disconnect and connect directly to Internet.
When they start their browser again they immediately get the ADFS login of the INTERNAL ADFS server (which, in theory, they should never see).
What seems to be happening is that they hit the WAP which forwards the requests to the internal ADFS server which presents the login screen of our internal ADFS server
This only occurs in this specific scenario (i.e. having already connected via SSO) and clearing the browser's cache fixes the issue. So, I'm assuming that ADFS stores some sort of cookie or other token somewhere and the browser is re-using that when it tries to authenticate?
FYI - KMSI and PersistentSSO are both disabled.
What may be happening is that ADFS has a cookie that remembers the HRD choice and bypasses this check for following attempts.
This cookie by default is active for 30 days. You can turn it off or extend the time.
e.g. Set-AdfsWebConfig -HRDCookieLifetime 90
Suppose that I have an account on a server with an address http://www.xxx.xxx/~account.
Because of some restriction on the server xxx.xxx, I set up a new AWS server with my own domain http://my.domain.xxx.
However, it looks like the new domain doesn't sufficiently represent my identity, so I was wondering if I could assign the address http://www.xxx.xxx/~account to the AWS server.
Is this possible? If so, how can I do that?
Set the A record of your www.xxx.xxx to the IP of the EC2 server hosting your website and set up a Virtual Host in your web server configuration to handle requests for that domain name.
I am using Service Bus 11gR1
I have created a proxy service
I can view it's WSDL if I point my browser to:
https://wlsdev.mydomain.com/osb/RJMTest/XXIC_ErrorQueryAsync_Proxy?wsdl
When I look at the returned WSDL I can see the binding element lists the actual host rather than the load balancer:
</WL5G3N0:binding>
<WL5G3N0:service name="query_ptBindingQSService">
<WL5G3N0:port binding="WL5G3N2:query_ptBinding" name="query_ptBindingQSPort">
<WL5G3N3:address location="http://internalserver.com:8010/osb/RJMTest/XXIC_ErrorQueryAsync_Proxy"/>
</WL5G3N0:port>
</WL5G3N0:service>
My question is what setting in OSB do I need to change to alter what the SOAP wsdl is using to generate the WSDL?
(In SOA there was a ServerURL setting)
You will have to update the cluster http frontend host to the load balancer address. This will need to be done on WebLogic Admin console
Login to http://{host}:{port}/console
Clicked on Lock and Edit button
Select Cluster
Click on HTTP
Configure Front End Host address to the pool name of load balancer
Configure http and https port where managed servers listen to
Click Save.
You will need to restart the managed servers.
I have built a website and a WCF service. The website calls the WCF service (an application underneath the website) to get data. This connection is made using netTcpBinding (it _should be netNamedPipes but for some reason this refuses to work (only) on the deployment server, so I'm using TCP/IP).
In IIS (7.5) I have used IP Address and Domain Restrictions to deny all unspecified clients to the WCF service. I can see the change reflected in my web.config and I am unable to browse to the WCF service (403.6 Forbidden screen appears).
The problem is that the website is able to connect to the WCF service and get data even when I specify NO IP address is allowed i.e. no matter what I change, the website can still call the WCF service.
Why can the website access the WCF service?
Did you make those same IP restrictions on your website? Since your website is the one calling the WCF service, making those same IP restrictions there would make sense also.