Disabling Weblogic's http server port - Using an external web server

Hi,
We are using Weblogic 8.1 as application server and IWS as web server. We have
siteminder web agent configured on the web server for implementing authentication
and authorization.
All our requests first go to the web server which redirects them to the application
server.
Since Weblogic itself has a http listen port, user can still send requests directly
to the application server(which does not have any siteminder configuration on
it). Is it possible to ensure that all http requests made directly to the application
server are not processed so that the user is forced to hit the web server first.
Thanks,
Akash

When you say redirect, do you mean you use an HTTP redirect to send it to your
WLS servers URL? Or do you mean you proxy the requests from the webserver to
the WLS instance? In the former case, you must expose WLS's HTTP server to the
clients in order to redirect them to the address and you will not be able to
stop them from going directly there. In the case of the latter, you can put
your WLS instance behind the firewall so external users can't get to it. If you
also need to protect it from internal users you should probably not use
siteminder as your authentication mechanism. You may be able to configure
siteminder so that it has to authenticate itself to send requests to weblogic
and then protect all weblogic resources with that role requirement.
Sam
[email protected] wrote:
Hi,
We are using Weblogic 8.1 as application server and IWS as web server. We have
siteminder web agent configured on the web server for implementing authentication
and authorization.
All our requests first go to the web server which redirects them to the application
server.
Since Weblogic itself has a http listen port, user can still send requests directly
to the application server(which does not have any siteminder configuration on
it). Is it possible to ensure that all http requests made directly to the application
server are not processed so that the user is forced to hit the web server first.
Thanks,
Akash

Similar Messages

How to keep the current http session after returning from external web site

Hi,
When I use the response.sendRedirect api to redirect the web page to the external payment site, after payment and return back to the current application, I found that the current http session is lost.
How to keep the current http session after returning from external web site?
Thanks

You should make your sidebar1 and sidebar2 fixed positioned. Make your content DIV fluid.
This should help you: http://www.glish.com/css/7.asp

Setting up weblogic as http server

How can I set up weblogic server as a http server with multiple virtual domain names?

This is currently not supported as part of version 5.1. It will be added as
part of our next version, 6.0, which is expected to go in public beta in a
month.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"sagol" <[email protected]> wrote in message
news:39acb108$[email protected]..
How can I set up weblogic server as a http server with multiple virtualdomain names?

The disk drive in my ibook g3 is broken, is it possible to disable the drive so i can use an external superdrive instead?

the disk drive doesn't load up what ever is put into it and i am unable to fix it or replace it
when i plug in a superdrive into the usb port it won't work because the disk drive still takes precedence
is there any way to disable the drive so i can use my superdrive instead?
thanks,
matt

For removal or replacement you can see how to do it with an iFixIt manual. Go to the link nd pick your model then look up optical drive.
http://www.ifixit.com/Device/iBook_G3

Using an external web service and local element declarations

I am attempting to use (call) an external web service from workshop
8.1. It seems that if the web service's schema contains local element
declarations with the same name then workshop will generate incorrect
JCX code because it doesn't scope the generated classes.
I think the following simple example will do a better job explaining
than that last paragraph ;). In the following WSDL, the element
"testLocalDec" is used inside two different element types. In XML
Schema this is not a problem because each one is "scoped" by the
element types its included in. However, the generated JCX (listed
second) simply contains the testLocalDec structure twice which causes
problems in Java.
Is there some workaround for this? Note that making this element
declaration in the WSDL will not work because they are different
structures (with different names).
Also see my next email around using XMLBeans with external services
(since that could be a workaround if I knew how to do it).
thanks,
dave
*** sample WSDL ***
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
     <s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
     <s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn" element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
*** generated JCX ***
package helloTest;
* @jc:location
http-url="http://localhost:18080/tutorial/HelloWorldService"
* @jc:wsdl file="#HelloWorldServiceWsdl"
* @editor-info:link source="HelloWorldService.wsdl" autogen="true"
public interface HelloWorldServiceControl extends
com.bea.control.ControlExtension, com.bea.control.ServiceControl
public static class testLocalDec
implements java.io.Serializable
public static class sayHelloResponse
implements java.io.Serializable
public java.lang.String sayHelloReturn;
public testLocalDec testLocalDec;
public static class testLocalDec
implements java.io.Serializable
public java.lang.String different;
* @jc:protocol form-post="false" form-get="false"
public sayHelloResponse sayHello (java.lang.String caller,
testLocalDec testLocalDec);
static final long serialVersionUID = 1L;
/** @common:define name="HelloWorldServiceWsdl" value::
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
     <s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
     <s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn"
element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Hi David,
The folks in the workshop newgroup may have a suggestion, if you could
try your post there:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.workshop
Thanks,
Bruce
David Rees wrote:
>
I am attempting to use (call) an external web service from workshop
8.1. It seems that if the web service's schema contains local element
declarations with the same name then workshop will generate incorrect
JCX code because it doesn't scope the generated classes.
I think the following simple example will do a better job explaining
than that last paragraph ;). In the following WSDL, the element
"testLocalDec" is used inside two different element types. In XML
Schema this is not a problem because each one is "scoped" by the
element types its included in. However, the generated JCX (listed
second) simply contains the testLocalDec structure twice which causes
problems in Java.
Is there some workaround for this? Note that making this element
declaration in the WSDL will not work because they are different
structures (with different names).
Also see my next email around using XMLBeans with external services
(since that could be a workaround if I knew how to do it).
thanks,
dave
*** sample WSDL ***
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
<s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn" element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
*** generated JCX ***
package helloTest;
* @jc:location
http-url="http://localhost:18080/tutorial/HelloWorldService"
* @jc:wsdl file="#HelloWorldServiceWsdl"
* @editor-info:link source="HelloWorldService.wsdl" autogen="true"
public interface HelloWorldServiceControl extends
com.bea.control.ControlExtension, com.bea.control.ServiceControl
public static class testLocalDec
implements java.io.Serializable
public static class sayHelloResponse
implements java.io.Serializable
public java.lang.String sayHelloReturn;
public testLocalDec testLocalDec;
public static class testLocalDec
implements java.io.Serializable
public java.lang.String different;
* @jc:protocol form-post="false" form-get="false"
public sayHelloResponse sayHello (java.lang.String caller,
testLocalDec testLocalDec);
static final long serialVersionUID = 1L;
/** @common:define name="HelloWorldServiceWsdl" value::
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
<s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType />
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
<s:element name="testLocalDec" >
<s:complexType >
<s:sequence>
<s:element name="different" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn"
element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

How do I use an external web cam with my Mac Pro on Skype?

I am trying to use my MAC Pro with an external web cam (Logitec C615) on Skype. I want to use the external so that I can pan and video a room full of people. Kind of hard to do with the built in cam.
How do I tell the Mac Pro to use the external for Skype and not the built in?

Go to Skype preferences, click on audio/video, and choose your camera from the drop down menu...

HT5697 How do i configure os x server wiki to use the external web server?

I have a Mac mini Server with OS X 10.10 and Server 4.0 running in a DMZ behind a firewall. The firewall passes a select few ports through to this server, exposing services to the Internet.
I use two domains, one dummy domain only available on my local networks, and one proper domain available globally. Lets call them «example.lan» and «example.com». These domains are not hosted on the Mac mini, btw.
In the external domain, I have «server.example.com» registered on my firewalls official IP address.
In my internal domain, I have «server.example.lan» registered to my Mac mini internal (rfc1918) IP address.
Server 4.0 -> Websites seem to work as expected. I have three servers configured: «Server Website - All IP addresses», port 80 + 443. These serve the local networks. Then there is «server.example.com», port 443, serving the internet.
Now to my question: How to I control which of these websites we Wiki uses?
When I activate the Wiki, it is published on «server.example.lan/wiki», which seems rather pointless. In order for the wiki to be available to the internet, it needs to be published on «server.example.com/wiki», but I see no way of doing this. What am I missing here?
Regards,
Gakke

it does look like you can add virtual domains in the GUI of Server.app on at least some versions, but I don't have an OS X Server 10.8 version handy to check.
I'd encourage spending some time to learn the command line. In general, the payoff for learning the command line will be worth the effort expended. You're running a mail server here and sooner or later the capabilities of the GUI will fail you. This whether due to a configuration omission in the GUI itself, or due to the need to troubleshoot a malfunctioning mail server, a need to automate one or more of the Postfix-related sequences, or some other IT-related task. Entirely FWIW, of course.
Here's a cut-and-paste of the sequence just used to test the command line access to the Postfix configuration, first fetching the current value, appending example.com as the second domain, then displaying the new value, then restarting the Postfix server. Don't enter the dollar signs; just the postconf command and following. Adjust example.com to match your domain...
$ postconf mydestination
mydestination = $myhostname, localhost.$mydomain, localhost
$ sudo postconf -e 'mydestination = $myhostname, localhost.$mydomain, localhost, example.com'
Password: {your admin password here}
$ postconf mydestination
mydestination = $myhostname, localhost.$mydomain, localhost, example.com
$ sudo postfix reload
The Postfix and Postconf commands work irrespective of the OS X Server version; the tools reference the data files as needed.

About logical port used to call Web service

Hi Experts:
I found that logical port can be created either from "LPCONFIG" or "SOAMANAGER"， They can't be found from the other transaction. What's the difference between them? Which one should be used in cases?
Wayne

One is a SAP GUI based transaction and the other is a WebDynpro based transaction. SOAMANAGER controls many more things than just logical port maintenance though and is the central location for runtime web service configuration. It's available with NW 7.0 SP14 or higher. You can still use either transaction after NW 7.0 SP14, but get in the habit of using SOAMANAGER.

Using an external web service and XMLBeans

I have an external document/literal web service that I want to use
(call) from inside workshop. I have listed a small example at the end
of this email.
I am wondering if there is a way to call and receive from the web
service using XMLBeans. In the tutorial examples XMLBeans are only
used by marshaling and unmarshaling the xml structure into a string
which is what is actually passed according to the WSDL. However, in
this case (and I personally think in most cases) the schema is
explicitly described in the WSDL and passed as the message. I might
add the structures for my real service are much more complex and so
the value of XMLBeans is certainly applicable to them.
Clearly I can somehow save off the schema and generate XMLBeans from
it. The next step is much less clear, how do I tell my JCX to use the
beans instead of generating private classes to represent the
structures?
To be honest I am a little surprised that for 8.1 the WSDL->JCX stuff
doesn't just leverage XMLBeans by default instead of generating basic
classes. This would give the power of XMLBeans to all web service
calls.
thanks,
dave
*** Sample WSDL ***
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
<s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn" element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

FYI, there is a XMLBeans newsgroup; w/ good feedback from the
developers:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.xmlbeans
Bruce Stephens wrote:
>
Hi David,
We are on the road, headed in that direction; pedal to the metal, etc.
just not there...yet.
We appreciate and value your input.
Thanks,
Bruce
David Rees wrote:
I have an external document/literal web service that I want to use
(call) from inside workshop. I have listed a small example at the end
of this email.
I am wondering if there is a way to call and receive from the web
service using XMLBeans. In the tutorial examples XMLBeans are only
used by marshaling and unmarshaling the xml structure into a string
which is what is actually passed according to the WSDL. However, in
this case (and I personally think in most cases) the schema is
explicitly described in the WSDL and passed as the message. I might
add the structures for my real service are much more complex and so
the value of XMLBeans is certainly applicable to them.
Clearly I can somehow save off the schema and generate XMLBeans from
it. The next step is much less clear, how do I tell my JCX to use the
beans instead of generating private classes to represent the
structures?
To be honest I am a little surprised that for 8.1 the WSDL->JCX stuff
doesn't just leverage XMLBeans by default instead of generating basic
classes. This would give the power of XMLBeans to all web service
calls.
thanks,
dave
*** Sample WSDL ***
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="urn:tutorial/hello"
targetNamespace="urn:tutorial/hello"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<s:schema targetNamespace="urn:tutorial/hello">
<s:element name="sayHelloResponse" >
<s:complexType>
<s:sequence>
<s:element name="sayHelloReturn" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="sayHello" >
<s:complexType>
<s:sequence>
<s:element name="caller" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="sayHelloRequestMsg">
<wsdl:part name="message" element="tns:sayHello"/>
</wsdl:message>
<wsdl:message name="sayHelloResponseMsg">
<wsdl:part name="sayHelloReturn" element="tns:sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHello" >
<wsdl:input message="tns:sayHelloRequestMsg" />
<wsdl:output message="tns:sayHelloResponseMsg" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldServiceSoapBinding"
type="tns:HelloWorld">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequestMsg">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sayHelloResponseMsg">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="tns:HelloWorldServiceSoapBinding"
name="HelloWorldService">
<wsdlsoap:address
location="http://localhost:18080/tutorial/HelloWorldService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

WebLogic HTTP Server

Hello,
How do i bring up only the HTTP services and not all of the
service provided by weblogic. I want to host a simple servlet
on the weblogic and i want weblogic to run on http services
with minimal footprint. Just like in websphere we have separate
http server and application server ???

Bill,
Yes, you are correct.
Bill Kimura wrote:
Correct me if I'm wrong, but Weblogic
HTTP server runs regardless of whether
I use a dedicated web tier using Apache
along with the appropriate plugin, or
if I just use a hw load balancer and combine
the web and presentation tiers?
The proxy plugin for Apache will just proxy
off the request to Weblogic's http server,
correct?
Thanks,
- Bill--
Developer Relations Engineer
BEA Support

Using External Web Service

Hello All,
I need to get data from External Web Service.
for example from :
http://www.w3schools.com/webservices/ws_use.asp
I need to use it from SERVER side method for example from any Context Node SET_XXX() method.
Thanks In Advance
Eli

Hi Eli,
You can create a proxy using the external web services. Go to transation SE 80->Edit Object on the application tool bar. Select the Enterprise Services tab and select the client proxy and click create.
select URL/HTTP Destination and just follow the menu path. The external web service will be created as a proxy(class) in SAP. you will be able to use this in your coding.
Hope this helps.
Sudha.

External Web Authentication - HTTP Redirect or Proxy?

I've been reading all of the information I can find about the use of authentication of guest users using an external web server, rather than the native portal provided by a WLC. I've looked at the configuration examples and configuiration guides.
My question is this: when the WLC redirects the client to the external web server, is it a true http redirect (i.e. a http redirect sent to the client) or does the WLC act as a proxy (via its virtual address - usually 1.1.1.1), altering the http headers as it does when re-directing requests to its internal web portal ?
This is important as I need to understand if it is the client that has to be able to connect to the external web server, or whether it is the WLC that has to be able to connect to the external web server.
The WLC for the solution I am working on is in a highly secure DMZ area, so it is imprtant to know which devices need to talk to which.

So, to be clear, it is the WLC that needs connectivity to the external server or the client device?
Both devices need to communicate to the external web server. The WLC will need to communicate with the external server since it will be expecting a return of information from that server to process the l3 authentication. The client will need to reach it as the WLC is going to redirect it to that site (reason for pre-auth acl).
Does the client communicate directly with the external web server, or will it direct its http requests to 1.1.1.1, which will then be proxied by the WLC to the external web server?
Again this is both; So the client will lookup/resolve a site and initiate some HTTP traffic, so it starts a TCP SYN for to the real web server it is trying to reach, the WLC will see this request; hijack the IP of the destination server and reply back to the client(pretending to be the "internet" server) The WLC redirects the client to it's virtual IP; whether using internal or external web auth. So the client will arrive at the virtual IP of the WLC; which will then redirect the client to the external web server in your case. When this happens the WLC has also inserted some information in to the redirect URL on the clients behalf so which the external server will use to send the information it collects (assuming you're using one of our standard external bundles). The external server will process the client HTTP GET, so as far as "viewing and using" the external web server; the client will make that request directly to the external web server. The external server, upon submittion of the form on the page, will send the information collected from the client back to the WLC server (which it learned it's IP from the redirect URL). The authentication of the client will take place at the WLC.
So in this scenario you need a love triangle between the Client, WLC, and external server. All will be talking to one another at some point. Your client needs connectivity to the external server; and your WLC needs connectivity to the external server.
David W.

Is it possible to call an external web service using ABAP?

Hi~~
I wonder that is possible to use an external web service in SAPGUI using ABAP without PI ( Process Integraion ).
The external web service means the service that is developed by web-language like ASP.NET.
Thank you.

hi,
i'm trying to study on how to use the oracle bi publisher using another client application aside from oracle. the client application is custom and uses a .Net framework. unfortunately, i am not familiar with how .Net sends requests to oracle bi publisher so i was thinking that may be i can just create oracle pl/sql stored procedures that can send this requests over to bi publisher.
p.s. when you said concurrent manager, i'm not sure if you are referring to oracle apps concurrent manager but if you are, unfortunately i won't be using oracle apps with bi publisher.
thanks
allen

What is the HTTP server [default/built-in] that Weblogic server uses

Is the built-in web server in weblogic Apache or is it some other http server that
BEA owns ?

WebLogic Server is a single java process, that has two listen ports, one SSL
and non-ssl.
These two ports use protocol discrimination to handle multiple protocols on
a single port.
NON-SSL --> http, t3 (proprietary rmi protocol), iiop
SSL --> https, t3s, iiops
So WebLogic comes with a build in Webserver. Or you can use a third party
webserver in front of WLS with plugin to proxy to WLS.
See;
http://edocs.bea.com/wls/docs81/plugins/
Cheers
mbg
"Manoj" <[email protected]> wrote in message
news:3edb0ba5$[email protected]..
>
Is the built-in web server in weblogic Apache or is it some other httpserver that
BEA owns ?

Connection timeout when using iPlanet web-server uses Weblogic 6.1 proxy server to proxy requests to an HTTP server

Hi all,
My configuration is as follows: I have an iPlanet web-server that uses a WebLogic
6.1 (sp1) server to proxy requests to another HTTP server. The HTTP request runs
for 120 seconds. This causes Weblogic to timeout after a while. The error I get
is as follows:
<Aug 25, 2003 3:37:09 PM GMT+00:00> <Warning> <HttpClient> <Couldn't open connection
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:194)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
at weblogic.net.http.HttpClient.New(HttpClient.java:149)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
at com.db.gmr.dcm.DebtIssueServlet.getVectorFromConnection(DebtIssueServle
t.java:285)
at com.db.gmr.dcm.IssuesUSThread.run(IssuesUSThread.java:29)
>
I get the same error when I added the following plug-in configuration parameters
(in obj.conf):
ConnectTimeoutSecs="170" ConnectRetrySecs="170".
What do I need to do to extend this timeout? Any help you can provide will be
greatly appreciated..
Thanks
Manish

Hi all,
My configuration is as follows: I have an iPlanet web-server that uses a WebLogic
6.1 (sp1) server to proxy requests to another HTTP server. The HTTP request runs
for 120 seconds. This causes Weblogic to timeout after a while. The error I get
is as follows:
<Aug 25, 2003 3:37:09 PM GMT+00:00> <Warning> <HttpClient> <Couldn't open connection
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:127)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:194)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
at weblogic.net.http.HttpClient.New(HttpClient.java:149)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
at com.db.gmr.dcm.DebtIssueServlet.getVectorFromConnection(DebtIssueServle
t.java:285)
at com.db.gmr.dcm.IssuesUSThread.run(IssuesUSThread.java:29)
>
I get the same error when I added the following plug-in configuration parameters
(in obj.conf):
ConnectTimeoutSecs="170" ConnectRetrySecs="170".
What do I need to do to extend this timeout? Any help you can provide will be
greatly appreciated..
Thanks
Manish

Disabling Weblogic's http server port - Using an external web server

Similar Messages

Maybe you are looking for