Proxy Demo
Hi
I'm trying to build a proxy demo for a customer.
if I understand the architecture I need to install on the proxy server:
Messenger: Imap Proxy + Messenger
Web server
Communication Express
But do I need Access manager or Directory server on proxy?
Thanks
<snip>
to the internet is not good. It can't tell if the
message is addressed to a real user or not.Recipe
for a DOS attack. There are many other reasons not
to
expose this device to the internet.
Trend (and the other scanner folks) build great
scanners, but they are not experienced in building
great SMTP servers. We don't do scanners, but we
do
build a great MTA.
Uhmmm, I have to test. It seems better but add more
dificulty.Yes, it's slightly more difficult, but it's a lot better, especially if you have more than just a few users on your system.
I run a small system. I reject at connection time, all messages addressed to anybody other than my actual users. That's on the order of 90% of what comes my way. Imagine how much additional cpu,memory and disk I'd need to process all that, and send back DSN for each bad address. Imagine how many users outside my system would be unhappy getting blowback from messages with forged "from" addresses.
It's very important to only accept messages for users that you actually service. It's not just 'good practice', it's truly important, now.
Trend accepts anything you offer it. You need to insulate it from having to do that.
>
>>
IMAP: I try MMP and it works.
Communication express: This is my question.
MMP only act as proxy for mail or calendar to?Our UWC, also known as "communication express" runs
on a web server. It would normally sit behind a
standard web proxy, set up as a "reverse proxy",
and
communicate to the MEM on that same box. I realize
this is starting to get complex, but, until we get
the next version out, it's going to be complex.
I don't understand this part.
I have to install an standard web proxy and MEM? So
the final picture is a server with:
MMP (Imap)
MEM (web mail proxy typical 8080 port)
Apache proxy (port 80 redirect to internal UWC ??)It truly depends on what you're setting up.
If you want to use UWC, AND you have more than one store backend, then you need
the web server container with UWC installed on it.
MEM
You already need MMP for imap.
I think you need the MTA.
You may or may not have all this on one box. Big systems have it on many boxes.
None of us that regularly contribute to this forum are truly expert in architecting large systems. It might help us to help you if you gave us some idea of the scale of what you're trying to do.
>
'm so confused about that...
Do you now when 2006qX have to be released?I can't tell, exactly. It's due out sometime after the first of the year, subject to delays. It's in beta, now.
>
>>
>>>
How I will install MMP?You have already installed MMP, if you proxy IMAP.
My mistake, I was talking about MEMYes, as I said abov e, you'll likely need MEM.
>
>
>>
Thanks
Similar Messages
-
IDoc to IDOC , Proxy to Proxy demo scenarios
Hi!
Can some one recommend some practical sdn-blogs/documentation for the demo XI scenarios such as:
IDoc_to_IDoc, Proxy_to_Proxy, etc.
I have a SAP ECC 6.0 ABAP system (IDES system with two business clients) and SAP PI.
Thank you very much!
regards
HolgerHi
for proxi- to-proxi scenario's refer these links
http://help.sap.com/saphelp_nw04s/helpdata/en/67/2edd3f597af206e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/f8/8ae03fc2269615e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/5d/2add3f597af206e10000000a1550b0/frameset.htm
and also refer these
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30ed7284-22e5-2910-0b85-bb39428e5ab3
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00de46da-8b8b-2a10-a1a0-c328b2034b5e
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/809a4f1a-f8cb-2a10-42bf-cf2338590d8b
hope this helps
regards,
surya -
Learning Java proxies - landscape question
Hi guys,
I could use a little help to learn Java Proxies, I'm just starting to get familiar with Java, I'm coming from the ABAP side.
First and foremost what do I need from the system point view?
We have an XI box and using file/FTP/IDoc adapters and also ABAP Proxies, I wrote some Java (mapping)functions, I am familiar with these.
But for a Java proxy, I would need a separate Java server(?) to run the application on, is this correct?
Can I use my own PC for this? (for learning purposes), I have NWDS installed on my PC.
What are the steps to write a small simple Java Proxy.
I would very much appreciate some help, guys, how do I start?
Thanks a lot,
ViktorHi Viktor,
You can work from your own machine. Becuase in Java Proxy scenarios, you are deploying EAR files in the XI server, and thru XI , you are executing the method written in the Java Application.
Just check these links-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
/people/prasad.ulagappan2/blog/2005/06/27/asynchronous-inbound-java-proxy
/people/rashmi.ramalingam2/blog/2005/06/25/an-illustration-of-java-server-proxy
Demo ~
https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/110ff05d-0501-0010-a19d-958247c9f798#jdi [original link is broken]
Hope this helps,
Regards,
Moorthy -
EREC: Replace Resume parsing demo by a functional XI proxy
Hello,
I'm trying to set the standard SAP solution Resume Parsing. I have reviwed the notes 1122135 (EHP3), 1276543 and 1516634 (EHP4). And I don't have clear how to replace the demo proxy by a functional proxy. Where this customization has to be done?
The only information I have is the service interfaz name.
Entity Type Service interface
Technical Name in Enterprise Service Repository (ESR) ResumeParseQueryResponse_Out
TNamespace in ESR http://sap.com/xi/ERECRUIT/Global
Software Component Version in ESR ERECRUIT 603
Category Outbound
Mode Synchronous
Related Service Resume Parsing
should I publish this post in XI section?
Thanks.Hello Javier,
Please have a look at:
http://help.sap.com/saphelp_nw70/helpdata/en/0f/80243b4a66ae0ce10000000a11402f/frameset.htm
Regards
Nicole -
Hello,
I'm trying to deploy the rich client component runtime demo(see this) on "Sun GlassFish Enterprise Server v2.1.1". This is a clean install, i havn't deployed anything else. When i drop rcf-dvt-demo.war and surf to http://localhost:8080/rcf-dvt-demo/ i get http status 503. I have tried to google but with no luck..
My logs says:
[#|2010-04-10T20:00:17.972+0200|SEVERE|sun-appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=17;_ThreadName=Timer-9;/C:/Sun/SDK/domains/domain1/autodeploy/rcf-dvt-demo.war;_RequestID=bacf3ad7-227b-4135-a059-145209b455fe;|"DPL8004: file open failure; file = /C:/Sun/SDK/domains/domain1/autodeploy/rcf-dvt-demo.war"|#]
[#|2010-04-10T20:00:17.988+0200|INFO|sun-appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=17;_ThreadName=Timer-9;|[AutoDeploy] The copy operation for C:\Sun\SDK\domains\domain1\autodeploy\rcf-dvt-demo.war into the auto-deploy directory may still be in progress or the file may be corrupt; will retry periodically until at least Sat Apr 10 20:00:47 CEST 2010|#]
[#|2010-04-10T20:00:19.972+0200|SEVERE|sun-appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=17;_ThreadName=Timer-9;/C:/Sun/SDK/domains/domain1/autodeploy/rcf-dvt-demo.war;_RequestID=bacf3ad7-227b-4135-a059-145209b455fe;|"DPL8004: file open failure; file = /C:/Sun/SDK/domains/domain1/autodeploy/rcf-dvt-demo.war"|#]
[#|2010-04-10T20:00:21.972+0200|INFO|sun-appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=17;_ThreadName=Timer-9;|[AutoDeploy] Selecting file C:\Sun\SDK\domains\domain1\autodeploy\rcf-dvt-demo.war for autodeployment.|#]
[#|2010-04-10T20:00:48.925+0200|SEVERE|sun-appserver2.1|org.apache.jasper.servlet.JspServlet|_ThreadID=18;_ThreadName=httpSSLWorkerThread-8080-1;_RequestID=88635a24-548b-47de-a8a6-c0b35438ee8e;|PWC6117: File "C:\Sun\SDK\domains\domain1\docroot\rcf-dvt-demo\faces\index.jspx" not found|#]
[#|2010-04-10T20:00:52.706+0200|WARNING|sun-appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=17;_ThreadName=Timer-9;_RequestID=bacf3ad7-227b-4135-a059-145209b455fe;|Error in annotation processing: java.lang.NoClassDefFoundError: weblogic/servlet/http/AbstractAsyncServlet|#]
[#|2010-04-10T20:00:53.253+0200|INFO|sun-appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=17;_ThreadName=Timer-9;|deployed with moduleid = rcf-dvt-demo|#]
[#|2010-04-10T20:00:54.534+0200|INFO|sun-appserver2.1|javax.enterprise.resource.webcontainer.jsf.config|_ThreadID=17;_ThreadName=Timer-9;/rcf-dvt-demo;|Initializing Mojarra (1.2_13-b01-FCS) for context '/rcf-dvt-demo'|#]
[#|2010-04-10T20:00:54.800+0200|SEVERE|sun-appserver2.1|javax.enterprise.system.container.web|_ThreadID=17;_ThreadName=Timer-9;_RequestID=bacf3ad7-227b-4135-a059-145209b455fe;|WebModule[/rcf-dvt-demo]PWC1275: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener
com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! This parser does not support specification "null" version "null"
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:215)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:196)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4655)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5364)
at com.sun.enterprise.web.WebModule.start(WebModule.java:345)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:986)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:970)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:704)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1649)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1254)
at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:182)
at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:278)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1005)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:992)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:231)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:966)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:280)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:298)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:584)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:390)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:373)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:477)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:170)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:583)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployJavaEEArchive(AutoDeployer.java:564)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:495)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:270)
at com.sun.enterprise.deployment.autodeploy.AutoDeployControllerImpl$AutoDeployTask.run(AutoDeployControllerImpl.java:374)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
at javax.xml.parsers.DocumentBuilderFactory.setSchema(DocumentBuilderFactory.java:561)
at com.sun.faces.config.ConfigManager$ParseTask.getBuilderForSchema(ConfigManager.java:522)
at com.sun.faces.config.ConfigManager$ParseTask.getDocument(ConfigManager.java:455)
at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:416)
at com.sun.faces.config.ConfigManager$ParseTask.call(ConfigManager.java:373)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
|#]
[#|2010-04-10T20:00:54.925+0200|SEVERE|sun-appserver2.1|org.apache.catalina.core.StandardContext|_ThreadID=17;_ThreadName=Timer-9;_RequestID=bacf3ad7-227b-4135-a059-145209b455fe;|PWC1306: Startup of context /rcf-dvt-demo failed due to previous errors|#]
[#|2010-04-10T20:00:55.675+0200|WARNING|sun-appserver2.1|javax.enterprise.system.stream.err|_ThreadID=19;_ThreadName=pool-7-thread-4;_RequestID=2bc4c823-f1c0-45e5-969b-f3f22885822d;|
XML-22000: (Fatal Error) Error while parsing XSL file (null).
|#]
[#|2010-04-10T20:00:55.691+0200|WARNING|sun-appserver2.1|javax.enterprise.system.stream.err|_ThreadID=20;_ThreadName=pool-7-thread-1;_RequestID=cfc7e4d3-aeab-474f-8df9-2f1b6d83cc4a;|
XML-22000: (Fatal Error) Error while parsing XSL file (null).
|#]
[#|2010-04-10T20:00:55.691+0200|WARNING|sun-appserver2.1|javax.enterprise.system.stream.err|_ThreadID=21;_ThreadName=pool-7-thread-2;_RequestID=496239eb-bb33-45c9-acc7-220f68657421;|
XML-22000: (Fatal Error) Error while parsing XSL file (null).
|#]
[#|2010-04-10T20:00:55.691+0200|WARNING|sun-appserver2.1|javax.enterprise.system.stream.err|_ThreadID=22;_ThreadName=pool-7-thread-3;_RequestID=9e58c64e-e9ef-445f-b1b3-d51e7278b14f;|
XML-22000: (Fatal Error) Error while parsing XSL file (null).
|#]
[#|2010-04-10T20:00:55.691+0200|WARNING|sun-appserver2.1|javax.enterprise.system.stream.err|_ThreadID=23;_ThreadName=pool-7-thread-5;_RequestID=be2009eb-605f-4137-9fe6-99a7142bcc67;|
XML-22000: (Fatal Error) Error while parsing XSL file (null).
|#]
[#|2010-04-10T20:00:55.753+0200|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=Timer-9;|
classLoader = WebappClassLoader
delegate: true
repositories:
/WEB-INF/classes/
----------> Parent Classloader:
EJBClassLoader :
urlSet = []
doneCalled = false
Parent -> java.net.URLClassLoader@1370b82
|#]
[#|2010-04-10T20:00:55.769+0200|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=Timer-9;|
SharedSecrets.getJavaNetAccess()=java.net.URLClassLoader$7@ac6572|#]
[#|2010-04-10T20:00:55.800+0200|INFO|sun-appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=17;_ThreadName=Timer-9;|[AutoDeploy] Successfully autodeployed : C:\Sun\SDK\domains\domain1\autodeploy\rcf-dvt-demo.war.|#]The demo you loaded is for Weblogic server, not for glassfish. You can't just deploy the demo and run it.
I'm not even sure it has been done jet, but may be someone has successfully done it.
Have you searched (google) for a solution?
Timo -
Java Proxy Runtime: failure to locate proxy bean on inbound call
Hello gurus of the SDN,
I have been trying to get an inbound Java Proxy scenario to work in XI 3.0 but have not been able to get the JPR to recognize my generated and deployed java code. My scenario is set up to call the java proxies generated from a message interface based on the MATMAS Idoc. I successfully deployed the generated java proxies on the same host box as is running the XI instance. The objects are named as follows
Message interface on XI = Inbound_MATMAS04
Generated proxy bean = Inbound_MATMAS04_PortTypeBean
Implementing class = InboundMATMAS04_PortTypeImpl
Implementing method = inboundMATMAS04
I used the JPR transport servlet to register the interface and implementing class but am not sure if I did this correctly. I used the following entry in my web browser:
http://nadcp786:50000/ProxyServer/register?
ns=urn:xiTrainingLabs:groupXX:SAP&
interface=InboundMATMAS04&
bean=InboundMATMAS04_PortTypeImpl&
method=inboundMATMAS04
I also tried using the localejb/ prefix for the bean name in the above step since the code is co-located. When I trigger the scenario, the Idoc info is passed into XI and the Java Proxy Runtime is called, but I get the following error response back in the SOAP header:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Finally, appended at the end of this post is the audit log of the messaging system showing that the JPR is called but without being able to locate the bean. I think I am missing a configuration step somewhere, but cant figure out what it is!! Can anyone help me?
Many thanks in advance.
Regards,
Nick Simon
Time Stamp Status Description
2004-10-25 19:47:32 Success The message was successfully received by the messaging system. Profile: XI URL: http://nadcp786.bcsdc.lexington.ibm.com:50000/MessagingSystem/receive/JPR/XI
2004-10-25 19:47:32 Success Using connection JPR. Trying to put the message into the receive queue.
2004-10-25 19:47:32 Success The message was successfully retrieved from the receive queue.
2004-10-25 19:47:32 Success The message status set to DLNG.
2004-10-25 19:47:32 Success Java proxy runtime (JPR) accepted the message
2004-10-25 19:47:34 Error JPR could not process the message. Reason: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl
2004-10-25 19:47:34 Error Delivery of the message to the application using connection JPR failed, due to: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl.
2004-10-25 19:47:34 Error The message status set to FAIL.
2004-10-25 19:47:34 Error Asynchronous error detected: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl. Trying to report it.
2004-10-25 19:47:34 Error Asynchronous error reported.
Message was edited by: Nicholas SimonHi
How do you determine the JNDI naming of the a EJB?
I have following entry in JNDI directory in the root
Object Name FlightQueryIn
Class Name javax.naming.Reference
Context Name
Object Value Reference Class Name:
Type: clientAppName
Content: sap.com/JavaProxyEAR
Type: interfaceType
Content: remote
Type: home
Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4
Type: ejb-link
Content: FlightSeatAvailabilityQueryIn_PortTypeBean
Type: jndi-name
Content: FlightQueryIn
Type: remote
Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4
I tried to register the bean with JPR using:
http://ctsapxid01:50100/ProxyServer/register?ns=http://sap.com/xi/XI/Demo/Airline&interface=FlightSeatAvailabilityQuery_In&bean=FlightQueryIn&method=flightSeatAvailabilityQueryIn
I followed the following blog
http://wiki.sdn.sap.com/wiki/display/Java/JavaProxyChangesinPI7.1fromPI7.0
Thanks,
Chris -
Problem in creating a java proxy for PHP web service
This is a problem in generating a java proxy for a PHP webservice.
I have a PHP service running on Wamp Server and also a PHP client which is able to call the service.
The WSDL for the PHP web service is also generated .
I am trying to create a java proxy using the jdev (10.1.3.0.3) from the wsdl file.
The wsdl generated by the php program is
<?xml version="1.0" encoding="ISO-8859-1" ?>
<definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:tns="urn:hellowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:hellowsdl">
<types>
<xsd:schema targetNamespace="urn:hellowsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="urn:hellowsdl#hello" style="rpc" />
<input>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>After making following changes to the wsdl program, I tried to generate java proxy.
<definitions name="hellowsdl"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:si="http://soapinterop.org/xsd" xmlns:tns="http://localhost/mywork/hellowsdl.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost/mywork/myphpwsdl.wsdll">
<types>
<xsd:schema targetNamespace="http://localhost/mywork/hellowsdl.wsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="" style="rpc" />
<input>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>This is how the java stub file looks like:
public class HellowsdlBinding_Stub
extends oracle.j2ee.ws.client.StubBase
implements demo.mypackage.HellowsdlPortType {
* public constructor
public HellowsdlBinding_Stub(HandlerChain handlerChain) {
super(handlerChain);
_setProperty(ENDPOINT_ADDRESS_PROPERTY, "http://localhost/mywork/hellowsdl.php");
setSoapVersion(SOAPVersion.SOAP_11);
setServiceName( new QName("http://localhost/mywork/hellowsdl","hellowsdl"));
setPortName( new QName("http://localhost/mywork/hellowsdl","hellowsdlPort"));
* implementation of hello
public java.lang.String hello(java.lang.String name)
throws java.rmi.RemoteException {
StreamingSenderState _state = null;
try {
_state = _start(_handlerChain);
if (_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS) != null) {
_state.getMessageContext().getMessage().setProperty("DimeEncode",_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS));
InternalSOAPMessage _request = _state.getRequest();
_request.setOperationCode(hello_OPCODE);
_state.getMessageContext().setProperty("oracle.j2ee.ws.mgmt.interceptor.operation-qname",new QName("","hello"));
demo.mypackage.runtime.HellowsdlBinding_hello_ReqS _myHellowsdlBinding_hello_ReqS = new demo.mypackage.runtime.HellowsdlBinding_hello_ReqS();
_myHellowsdlBinding_hello_ReqS.setName(name);
SOAPBlockInfo _bodyBlock = new SOAPBlockInfo(ns1_hello_hello_QNAME);
_bodyBlock.setValue(_myHellowsdlBinding_hello_ReqS);
_bodyBlock.setSerializer(myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer);
_request.setBody(_bodyBlock);
_state.getMessageContext().setProperty("http.soap.action", "http://localhost/mywork/hellowsdl");
_send((String) _getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
demo.mypackage.runtime.HellowsdlBinding_hello_RespS _myHellowsdlBinding_hello_RespS = null;
Object _responseObj = _state.getResponse().getBody().getValue();
if (_responseObj instanceof SOAPDeserializationState) {
_myHellowsdlBinding_hello_RespS =
(demo.mypackage.runtime.HellowsdlBinding_hello_RespS)((SOAPDeserializationState)_responseObj).getInstance();
} else {
_myHellowsdlBinding_hello_RespS =
(demo.mypackage.runtime.HellowsdlBinding_hello_RespS)_responseObj;
return _myHellowsdlBinding_hello_RespS.get_return();
} catch (RemoteException e) {
// let this one through unchanged
throw e;
} catch (JAXRPCException e) {
throw new RemoteException(e.getMessage(), e);
} catch (Exception e) {
if (e instanceof RuntimeException) {
throw (RuntimeException)e;
} else {
throw new RemoteException(e.getMessage(), e);
* this method deserializes the request/response structure in the body
protected void _readFirstBodyElement(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
int opcode = state.getRequest().getOperationCode();
switch (opcode) {
case hello_OPCODE:
_deserialize_hello(bodyReader, deserializationContext, state);
break;
default:
throw new SenderException("sender.response.unrecognizedOperation", Integer.toString(opcode));
* This method deserializes the body of the hello operation.
private void _deserialize_hello(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
try {
Object myHellowsdlBinding_hello_RespSObj =
myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer.deserialize(ns1_hello_helloResponse_QNAME,
bodyReader, deserializationContext);
SOAPBlockInfo bodyBlock = new SOAPBlockInfo(ns1_hello_helloResponse_QNAME);
bodyBlock.setValue(myHellowsdlBinding_hello_RespSObj);
state.getResponse().setBody(bodyBlock);
} catch (DeserializationException e) {
if (e.getSoapFaultSubCodeType() == JAXRPCExceptionBase.FAULT_CODE_NONE && e.getSoapFaultCodeType() != JAXRPCExceptionBase.FAULT_CODE_DATA_ENCODING_UNKNOWN) {
e.setSoapFaultSubCodeType(JAXRPCExceptionBase.FAULT_CODE_BAD_ARGUMENTS);
throw e;
public String _getEncodingStyle() {
return SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding();
public void _setEncodingStyle(String encodingStyle) {
throw new UnsupportedOperationException("cannot set encoding style");
public ClientTransport getClientTransport() {
return super._getTransport();
* This method returns an array containing (prefix, nsURI) pairs.
protected String[] _getNamespaceDeclarations() {
return myNamespace_declarations;
* This method returns an array containing the names of the headers we understand.
public QName[] _getUnderstoodHeaders() {
return understoodHeaderNames;
* This method handles the case of an empty SOAP body.
protected void _handleEmptyBody(XMLReader reader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
public void _initialize(InternalTypeMappingRegistry registry) throws Exception {
super._initialize(registry);
myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_ReqS.class, ns1_hello_TYPE_QNAME);
myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_RespS.class, ns1_helloResponse_TYPE_QNAME);
private static final QName _portName = new QName("http://localhost/mywork/hellowsdl", "hellowsdlPort");
private static final int hello_OPCODE = 0;
private static final QName ns1_hello_hello_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private static final QName ns1_hello_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private CombinedSerializer myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer;
private static final QName ns1_hello_helloResponse_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private static final QName ns1_helloResponse_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private CombinedSerializer myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer;
private static final String[] myNamespace_declarations =
new String[] {
"ns0", "http://localhost/mywork/hellowsdl"
private static final QName[] understoodHeaderNames = new QName[] { };
}The errors that are produced are-
java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found; nested exception is:
HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found
Kindly help to resolve this.
Thanks.This is a problem in generating a java proxy for a PHP webservice.
I have a PHP service running on Wamp Server and also a PHP client which is able to call the service.
The WSDL for the PHP web service is also generated .
I am trying to create a java proxy using the jdev (10.1.3.0.3) from the wsdl file.
The wsdl generated by the php program is
<?xml version="1.0" encoding="ISO-8859-1" ?>
<definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:tns="urn:hellowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:hellowsdl">
<types>
<xsd:schema targetNamespace="urn:hellowsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="urn:hellowsdl#hello" style="rpc" />
<input>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>After making following changes to the wsdl program, I tried to generate java proxy.
<definitions name="hellowsdl"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:si="http://soapinterop.org/xsd" xmlns:tns="http://localhost/mywork/hellowsdl.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost/mywork/myphpwsdl.wsdll">
<types>
<xsd:schema targetNamespace="http://localhost/mywork/hellowsdl.wsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="" style="rpc" />
<input>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>This is how the java stub file looks like:
public class HellowsdlBinding_Stub
extends oracle.j2ee.ws.client.StubBase
implements demo.mypackage.HellowsdlPortType {
* public constructor
public HellowsdlBinding_Stub(HandlerChain handlerChain) {
super(handlerChain);
_setProperty(ENDPOINT_ADDRESS_PROPERTY, "http://localhost/mywork/hellowsdl.php");
setSoapVersion(SOAPVersion.SOAP_11);
setServiceName( new QName("http://localhost/mywork/hellowsdl","hellowsdl"));
setPortName( new QName("http://localhost/mywork/hellowsdl","hellowsdlPort"));
* implementation of hello
public java.lang.String hello(java.lang.String name)
throws java.rmi.RemoteException {
StreamingSenderState _state = null;
try {
_state = _start(_handlerChain);
if (_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS) != null) {
_state.getMessageContext().getMessage().setProperty("DimeEncode",_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS));
InternalSOAPMessage _request = _state.getRequest();
_request.setOperationCode(hello_OPCODE);
_state.getMessageContext().setProperty("oracle.j2ee.ws.mgmt.interceptor.operation-qname",new QName("","hello"));
demo.mypackage.runtime.HellowsdlBinding_hello_ReqS _myHellowsdlBinding_hello_ReqS = new demo.mypackage.runtime.HellowsdlBinding_hello_ReqS();
_myHellowsdlBinding_hello_ReqS.setName(name);
SOAPBlockInfo _bodyBlock = new SOAPBlockInfo(ns1_hello_hello_QNAME);
_bodyBlock.setValue(_myHellowsdlBinding_hello_ReqS);
_bodyBlock.setSerializer(myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer);
_request.setBody(_bodyBlock);
_state.getMessageContext().setProperty("http.soap.action", "http://localhost/mywork/hellowsdl");
_send((String) _getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
demo.mypackage.runtime.HellowsdlBinding_hello_RespS _myHellowsdlBinding_hello_RespS = null;
Object _responseObj = _state.getResponse().getBody().getValue();
if (_responseObj instanceof SOAPDeserializationState) {
_myHellowsdlBinding_hello_RespS =
(demo.mypackage.runtime.HellowsdlBinding_hello_RespS)((SOAPDeserializationState)_responseObj).getInstance();
} else {
_myHellowsdlBinding_hello_RespS =
(demo.mypackage.runtime.HellowsdlBinding_hello_RespS)_responseObj;
return _myHellowsdlBinding_hello_RespS.get_return();
} catch (RemoteException e) {
// let this one through unchanged
throw e;
} catch (JAXRPCException e) {
throw new RemoteException(e.getMessage(), e);
} catch (Exception e) {
if (e instanceof RuntimeException) {
throw (RuntimeException)e;
} else {
throw new RemoteException(e.getMessage(), e);
* this method deserializes the request/response structure in the body
protected void _readFirstBodyElement(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
int opcode = state.getRequest().getOperationCode();
switch (opcode) {
case hello_OPCODE:
_deserialize_hello(bodyReader, deserializationContext, state);
break;
default:
throw new SenderException("sender.response.unrecognizedOperation", Integer.toString(opcode));
* This method deserializes the body of the hello operation.
private void _deserialize_hello(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
try {
Object myHellowsdlBinding_hello_RespSObj =
myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer.deserialize(ns1_hello_helloResponse_QNAME,
bodyReader, deserializationContext);
SOAPBlockInfo bodyBlock = new SOAPBlockInfo(ns1_hello_helloResponse_QNAME);
bodyBlock.setValue(myHellowsdlBinding_hello_RespSObj);
state.getResponse().setBody(bodyBlock);
} catch (DeserializationException e) {
if (e.getSoapFaultSubCodeType() == JAXRPCExceptionBase.FAULT_CODE_NONE && e.getSoapFaultCodeType() != JAXRPCExceptionBase.FAULT_CODE_DATA_ENCODING_UNKNOWN) {
e.setSoapFaultSubCodeType(JAXRPCExceptionBase.FAULT_CODE_BAD_ARGUMENTS);
throw e;
public String _getEncodingStyle() {
return SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding();
public void _setEncodingStyle(String encodingStyle) {
throw new UnsupportedOperationException("cannot set encoding style");
public ClientTransport getClientTransport() {
return super._getTransport();
* This method returns an array containing (prefix, nsURI) pairs.
protected String[] _getNamespaceDeclarations() {
return myNamespace_declarations;
* This method returns an array containing the names of the headers we understand.
public QName[] _getUnderstoodHeaders() {
return understoodHeaderNames;
* This method handles the case of an empty SOAP body.
protected void _handleEmptyBody(XMLReader reader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
public void _initialize(InternalTypeMappingRegistry registry) throws Exception {
super._initialize(registry);
myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_ReqS.class, ns1_hello_TYPE_QNAME);
myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_RespS.class, ns1_helloResponse_TYPE_QNAME);
private static final QName _portName = new QName("http://localhost/mywork/hellowsdl", "hellowsdlPort");
private static final int hello_OPCODE = 0;
private static final QName ns1_hello_hello_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private static final QName ns1_hello_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private CombinedSerializer myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer;
private static final QName ns1_hello_helloResponse_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private static final QName ns1_helloResponse_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private CombinedSerializer myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer;
private static final String[] myNamespace_declarations =
new String[] {
"ns0", "http://localhost/mywork/hellowsdl"
private static final QName[] understoodHeaderNames = new QName[] { };
}The errors that are produced are-
java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found; nested exception is:
HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found
Kindly help to resolve this.
Thanks. -
I am trying to call sharepoint online from powershell. Below is the code. I get
Exception calling "ExecuteQuery" with "0" argument(s): "The remote server returned an error: (407) Proxy Authentication Required."
$loadInfo1 = [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client")
$loadInfo2 = [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client.Runtime")
$webUrl = "ZZZZ"
$username = "XXX"
$password = "YYYY"
$ctx = New-Object Microsoft.SharePoint.Client.ClientContext($webUrl)
$ctx.Credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($username, $password)
$web = $ctx.Web
$lists = $web.Lists
$ctx.Load($lists)
$ctx.ExecuteQuery()
$lists| select -Property Title
Raj-ShptHi,
About how to access SharePoint online site using PowerShell, the blog below would be helpful:
http://social.technet.microsoft.com/wiki/contents/articles/29518.csom-sharepoint-powershell-reference-and-example-codes.aspx
Another two demos for your reference:
http://www.hartsteve.com/2013/06/sharepoint-online-powershell/
http://www.sharepointnutsandbolts.com/2013/12/Using-CSOM-in-PowerShell-scripts-with-Office365.html
Thanks
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected] -
How to use server-side classes in a web service proxy client ?
Greetings,
I'm using WebLogic 10.3 with Workshop 10.3 on Windows. I generate a Web Service client in Workshop. There are two options in the New->Others->Web Service category: ClientGen Web Service Client and Web Service Client. I've chosen the second one as it's a JAX-WS Web Service and I think that the first one (ClientGen Web Service is to be used with JAX-RPC Web Services. The proxy is generated but, since the Web Service is using POJOs as parameters, a new version of these POJOs is also generated. For example, my Web Service has an operation like: public OrderStatus putOrder (Order), where OrderStatus and Order are application scoped POJOs. The proxy generation process generates a _PortType class which is supposed to be used by the calling client. This class defines an operation public OrderStatus putOrder(Order), but the OrderStatus and Order classes aren't the original ones but the generated ones. The issue is that these generated classes aren't completely equivalent to the original ones, for examples all lists become arrays, the constructors are different, etc. This is extrememly annouying. Is there any option to say to the proxy generation process to keep with the server-side classes ?
many thanks in advance for any help.
NicolasThe only solution to this problem seems to be using dynamic proxies. But it doesn't work neither as the following code:
Service service = Service.create(new URL("http://localhost:7001/OrderServiceProject/OrderService?WSDL"),
new QName("http://www.simplex_software.fr/demo/services", "OrderService"));
OrderService orderService = service.getPort(new QName("http://www.simplex_software.fr/demo/services", "OrderServicePort"), OrderService.class);
raises the following exception:
16 déc. 2009 19:55:51 com.sun.xml.internal.ws.model.RuntimeModeler getRequestWrapperClass
INFO: Dynamically creating request wrapper Class fr.simplex_software.demo.services.jaxws.PutOrder
16 déc. 2009 19:55:51 com.sun.xml.internal.ws.model.RuntimeModeler getResponseWrapperClass
INFO: Dynamically creating response wrapper bean Class fr.simplex_software.demo.services.jaxws.PutOrderResponse
16 déc. 2009 19:55:51 com.sun.xml.internal.ws.model.RuntimeModeler getRequestWrapperClass
INFO: Dynamically creating request wrapper Class fr.simplex_software.demo.services.jaxws.GetOrderStatus
16 déc. 2009 19:55:51 com.sun.xml.internal.ws.model.RuntimeModeler getResponseWrapperClass
INFO: Dynamically creating response wrapper bean Class fr.simplex_software.demo.services.jaxws.GetOrderStatusResponse
Exception in thread "main" java.lang.IllegalArgumentException: fr.simplex_software.demo.services.OrderService is not an interface
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:362)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
at com.sun.xml.internal.ws.client.WSServiceDelegate.createEndpointIFBaseProxy(WSServiceDelegate.java:630)
at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:331)
at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:313)
at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:295)
at javax.xml.ws.Service.getPort(Service.java:92)
at fr.simplex_software.demo.client.OrderServiceClient.main(OrderServiceClient.java:23)
As a matter of fact, fr.simplex_software.demo.services.OrderService is not an interface but, nevertheless, it's a SEI and it was generated as it is by the IDE Web Service wizard. Big, big confusion ! Of course, this sample works perfectly with Metro, in NetBeans using Glassfish. -
Java Exception Error while trying to run Webutil demo
I am trying to run a webutil demo but failing due to the following error... the error is as
Oracle JInitiator: Version 1.3.1.9
Using JRE version 1.3.1.9 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\Aruns
Proxy Configuration: Manual Configuration
Proxy: proxy1.emirates.net.ae:8080
Proxy Overrides: <local>
JAR cache enabled
Location: C:\Documents and Settings\Aruns\Oracle Jar Cache
Maximum size: 50 MB
Compression level: 0
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
q: hide console
s: dump system properties
t: dump thread list
x: clear classloader cache
0-5: set trace level to <n>
Loading http://hpc266:8888/forms90/java/f90all_jinit.jar from JAR cache
Loading http://hpc266:8888/forms90/java/webutil.jar from JAR cache
Loading http://hpc266:8888/forms90/java/jacob.jar from JAR cache
connectMode=HTTP, native.
Forms Applet version is : 90270
java.lang.ExceptionInInitializerError: java.security.AccessControlException: access denied (java.util.PropertyPermission java.home read)
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPropertyAccess(Unknown Source)
at java.lang.System.getProperty(Unknown Source)
at oracle.forms.webutil.common.VBeanCommon.<clinit>(VBeanCommon.java:130)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at oracle.forms.handler.UICommon.instantiate(Unknown Source)
at oracle.forms.handler.UICommon.onCreate(Unknown Source)
at oracle.forms.handler.JavaContainer.onCreate(Unknown Source)
at oracle.forms.engine.Runform.onCreateHandler(Unknown Source)
at oracle.forms.engine.Runform.processMessage(Unknown Source)
at oracle.forms.engine.Runform.processSet(Unknown Source)
at oracle.forms.engine.Runform.onMessageReal(Unknown Source)
at oracle.forms.engine.Runform.onMessage(Unknown Source)
at oracle.forms.engine.Runform.sendInitialMessage(Unknown Source)
at oracle.forms.engine.Runform.startRunform(Unknown Source)
at oracle.forms.engine.Main.createRunform(Unknown Source)
at oracle.forms.engine.Main.start(Unknown Source)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Please help me to go forwardWhat is the error message, this looks like normal informational messages
I have signed it sucessfully..Now i am getting the
following in the java console
Oracle JInitiator: Version 1.3.1.9
Using JRE version 1.3.1.9 Java HotSpot(TM) Client VM
User home directory = C:\Documents and
Settings\Aruns
Proxy Configuration: Manual Configuration
Proxy: proxy1.emirates.net.ae:8080
Proxy Overrides: 172.16.*,<local>
JAR cache enabled
Location: C:\Documents and Settings\Aruns\Oracle
racle Jar Cache
Maximum size: 50 MB
Compression level: 0
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
q: hide console
s: dump system properties
t: dump thread list
x: clear classloader cache
0-5: set trace level to <n>
Loading
http://hpc266:8888/forms90/java/f90all_jinit.jar from
JAR cache
Cached copy of
http://hpc266:8888/forms90/java/webutil.jar is out of
date
Cached copy: Jul 4, 2005 8:50:04 AM
Server copy: Jul 4, 2005 8:52:15 AM
Downloading
http://hpc266:8888/forms90/java/webutil.jar to JAR
cache
Cached copy of
http://hpc266:8888/forms90/java/jacob.jar is out of
date
Cached copy: Jul 4, 2005 8:50:16 AM
Server copy: Jul 4, 2005 8:51:59 AM
Downloading http://hpc266:8888/forms90/java/jacob.jar
to JAR cache
connectMode=HTTP, native.
Forms Applet version is : 90270
Can anybody pls help me in this issue -
Error while executing demo scenario ProxyToProxy (for SAP PI 7.1)
I've try to execute demo scenario ProxyToProxy (from Simple Use Cases (SAP NetWeaver PI 7.1) at Getting Started With Service Bus-Based Integration [original link is broken] ). I call transaction SXIPATT1, enter suitable data and click "Send". In result, error message "OBJECT_IS_NO_PROXY Object CLASS_NAME CO_SXIPAT_XI_PATTERN_IF2_OUT is not a proxy object" displayed. Can you help me to resolve this problem?
I get the same exact error.
I went to SPROXY transaction. I can not figure out where to find message interface and how to activate it. Can you please give me steps. Like which menu I should go under to see that option?
Help will be greatly appreciated. I an a newbie and spent too much time could not figure this out myself.
Thanks in advance. -
Exception while running webutil demo
Hi,
I am facing problem with a webutil unit. when I use client_tool_env.getvar function
client_tool_env.getvar('NLS_LANG',:builtins.tool_env)
+(under BUILTIT->NLSLANG (button) of webutil DEMO)+
I get this exception in the Java console and the webutil package stops working. Can you tell me from the console readings what could possibly have gone wrong.
Oracle JInitiator: Version 1.3.1.22
Using JRE version 1.3.1.22-internal Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\Dd
Proxy Configuration: no proxy
JAR cache enabled
Location: C:\Documents and Settings\Dd\Oracle Jar Cache
Maximum size: 50 MB
Compression level: 0
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
q: hide console
s: dump system properties
t: dump thread list
x: clear classloader cache
0-5: set trace level to <n>
Loading http://dd-fd704ff99925:8889/forms/java/frmall_jinit.jar from JAR cache
Loading http://dd-fd704ff99925:8889/forms/java/frmwebutil.jar from JAR cache
Loading http://dd-fd704ff99925:8889/forms/java/jacob.jar from JAR cache
proxyHost=null
proxyPort=0
connectMode=HTTP, native.
Forms Applet version is : 10.1.2.0
2008-Sep-11 13:12:17.859 ERROR>WUC-18 [URLDownload.pullFile()] Invalid URL e:\oracle_developer_suite\forms/jacob.dll
2008-Sep-11 13:12:17.906 ERROR>WUC-18 [URLDownload.pullFile()] Invalid URL e:\oracle_developer_suite\forms/JNIsharedstubs.dll
2008-Sep-11 13:12:17.937 ERROR>WUC-18 [URLDownload.pullFile()] Invalid URL e:\oracle_developer_suite\forms/d2kwut60.dll
2008-Sep-11 13:30:49.468 ERROR>WUL-928 [CApiFunctions.register_function()] Library d2kwut60.dll not accessible, or does not contain function d2kwutil_GetRegKey
2008-Sep-11 13:30:49.593 ERROR>WUL-925 [CApiFunctions.parse_funcHnd()] Object returned from object cache is not of type CFunc
Exception occurred during event dispatching:
java.lang.NoClassDefFoundError: oracle.forms.webutil.cApi.CPtr
at oracle.forms.webutil.cApi.CParamList.toArray(Unknown Source)
at oracle.forms.webutil.cApi.CApiFunctions.invokeCApi(Unknown Source)
at oracle.forms.webutil.cApi.CApiFunctions.getProperty(Unknown Source)
at oracle.forms.handler.UICommon.onGet(Unknown Source)
at oracle.forms.engine.Runform.onGetHandler(Unknown Source)
at oracle.forms.engine.Runform.processMessage(Unknown Source)
at oracle.forms.engine.Runform.processSet(Unknown Source)
at oracle.forms.engine.Runform.onMessageReal(Unknown Source)
at oracle.forms.engine.Runform.onMessage(Unknown Source)
at oracle.forms.engine.Runform.processEventEnd(Unknown Source)
at oracle.ewt.lwAWT.LWComponent.redispatchEvent(Unknown Source)
at oracle.ewt.lwAWT.LWComponent.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)this is an issue with the virtual directory. Check this document.
[Webutil Debugging Document|http://www.google.com/search?hl=en&q=webutil+debugging+alexyscorp&aq=f&oq=] -
I keep running into the same error when trying to use the demo for web service development... im new to SOAP so if anyone could shed some light on it, id be wonderful... thanks in advance!
SQL> CREATE OR REPLACE PACKAGE demo_soap AS
2
3 /* A type to represent a SOAP RPC request */
4 TYPE request IS RECORD (
5 method VARCHAR2(256),
6 namespace VARCHAR2(256),
7 body VARCHAR2(32767));
8
9 /* A type to represent a SOAP RPC response */
10 TYPE response IS RECORD (
11 doc xmltype);
12
13 /*
14 * Create a new SOAP RPC request.
15 */
16 FUNCTION new_request(method IN VARCHAR2,
17 namespace IN VARCHAR2)
18 RETURN request;
19
20 /*
21 * Add a simple parameter to the SOAP RPC request.
22 */
23 PROCEDURE add_parameter(req IN OUT NOCOPY request,
24 name IN VARCHAR2,
25 type IN VARCHAR2,
26 value IN VARCHAR2);
27
28 /*
29 * Make the SOAP RPC call.
30 */
31 FUNCTION invoke(req IN OUT NOCOPY request,
32 url IN VARCHAR2,
33 action IN VARCHAR2) RETURN response;
34
35 /*
36 * Retrieve the sipmle return value of the SOAP RPC call.
37 */
38 FUNCTION get_return_value(resp IN OUT NOCOPY response,
39 name IN VARCHAR2,
40 namespace IN VARCHAR2) RETURN VARCHAR2;
41
42 END;
43 /
Package created.
SQL> ed
Wrote file afiedt.buf
1 CREATE OR REPLACE PACKAGE BODY demo_soap AS
2 FUNCTION new_request(method IN VARCHAR2,
3 namespace IN VARCHAR2)
4 RETURN request AS
5 req request;
6 BEGIN
7 req.method := method;
8 req.namespace := namespace;
9 RETURN req;
10 END;
11 PROCEDURE add_parameter(req IN OUT NOCOPY request,
12 name IN VARCHAR2,
13 type IN VARCHAR2,
14 value IN VARCHAR2) AS
15 BEGIN
16 req.body := req.body ||
17 '<'||name||' xsi:type="'||type||'">'||value||'</'||name||'>';
18 END;
19 PROCEDURE generate_envelope(req IN OUT NOCOPY request,
20 env IN OUT NOCOPY VARCHAR2) AS
21 BEGIN
22 env := '<SOAP-ENV:Envelope
23 xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
24 xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
25 xmlns:xsd="http://www.w3.org/1999/XMLSchema">
26 <SOAP-ENV:Body><'||req.method||' '||req.namespace||'
27 SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">'||
28 req.body||'</'||req.method||'></SOAP-ENV:Body></SOAP-ENV:Envelope>';
29 END;
30 PROCEDURE show_envelope(env IN VARCHAR2) AS
31 i pls_integer;
32 len pls_integer;
33 BEGIN
34 i := 1; len := length(env);
35 WHILE (i <= len) LOOP
36 dbms_output.put_line(substr(env, i, 60));
37 i := i + 60;
38 END LOOP;
39 END;
40 PROCEDURE check_fault(resp IN OUT NOCOPY response) AS
41 fault_node xmltype;
42 fault_code VARCHAR2(256);
43 fault_string VARCHAR2(32767);
44 BEGIN
45 fault_node := resp.doc.extract('/soap:Fault',
46 'xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/');
47 IF (fault_node IS NOT NULL) THEN
48 fault_code := fault_node.extract('/soap:Fault/faultcode/child::text()',
49 'xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/').getstringval();
50 fault_string := fault_node.extract('/soap:Fault/faultstring/child::text()',
51 'xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/').getstringval();
52 raise_application_error(-20000, fault_code || ' - ' || fault_string);
53 END IF;
54 END;
55 FUNCTION invoke(req IN OUT NOCOPY request,
56 url IN VARCHAR2,
57 action IN VARCHAR2) RETURN response AS
58 env VARCHAR2(32767);
59 http_req utl_http.req;
60 http_resp utl_http.resp;
61 resp response;
62 BEGIN
63 generate_envelope(req, env);
64 -- show_envelope(env);
65 http_req := utl_http.begin_request(url, 'POST','HTTP/1.0');
66 utl_http.set_header(http_req, 'Content-Type', 'text/xml');
67 utl_http.set_header(http_req, 'Content-Length', length(env));
68 utl_http.set_header(http_req, 'SOAPAction', action);
69 utl_http.write_text(http_req, env);
70 http_resp := utl_http.get_response(http_req);
71 utl_http.read_text(http_resp, env);
72 utl_http.end_response(http_resp);
73 resp.doc := xmltype.createxml(env);
74 resp.doc := resp.doc.extract('/soap:Envelope/soap:Body/child::node()',
75 'xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"');
76 -- show_envelope(resp.doc.getstringval());
77 check_fault(resp);
78 RETURN resp;
79 END;
80 FUNCTION get_return_value(resp IN OUT NOCOPY response,
81 name IN VARCHAR2,
82 namespace IN VARCHAR2) RETURN VARCHAR2 AS
83 BEGIN
84 RETURN resp.doc.extract('//'||name||'/child::text()',
85 namespace).getstringval();
86 END;
87* END;
88 /
Package body created.
SQL> CREATE OR REPLACE PACKAGE time_service AS
2 FUNCTION get_local_time(zipcode IN VARCHAR2) RETURN VARCHAR2;
3 END;
4 /
Package created.
SQL>
SQL> CREATE OR REPLACE PACKAGE BODY time_service AS
2
3 -- Location of Web service definition
4 -- http://www.alethea.net/webservices/LocalTime.asmx?WSDL
5
6 FUNCTION get_local_time(zipcode IN VARCHAR2) RETURN VARCHAR2 IS
7 req demo_soap.request;
8 resp demo_soap.response;
9 BEGIN
10 req := demo_soap.new_request('LocalTimeByZipCode',
11 'xmlns="http://www.alethea.net/webservices/"');
12 demo_soap.add_parameter(req, 'ZipCode', 'xsd:string', zipcode);
13 resp := demo_soap.invoke(req,
14 'http://www.alethea.net/webservices/LocalTime.asmx',
15 'http://www.alethea.net/webservices/LocalTimeByZipCode');
16 RETURN demo_soap.get_return_value(resp, 'LocalTimeByZipCodeResult',
17 'xmlns="http://www.alethea.net/webservices/"');
18 END;
19
20 BEGIN
21 /*
22 * Since the Web service resides outside of the firewall, we need to set
23 * the proxy in the current session before invoking the service.
24 */
25 utl_http.set_proxy('www-proxy', NULL);
26 utl_http.set_persistent_conn_support(TRUE);
27 END;
28 /
Package body created.
SQL> exec dbms_output.put_line(time_service.get_local_time('94065'));
BEGIN dbms_output.put_line(time_service.get_local_time('94065')); END;
ERROR at line 1:
ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1022
ORA-12545: Connect failed because target host or object does not exist
ORA-06512: at "LOANADMIN.DEMO_SOAP", line 65
ORA-06512: at "LOANADMIN.TIME_SERVICE", line 13
ORA-06512: at line 1I deleted the two lines of coding below:
utl_http.set_proxy('www-proxy', NULL);
utl_http.set_persistent_conn_support(TRUE);
and then I set the utl_http.set_persistent_conn_support() to False to get that error message. Seems like the website in question doesnt have the webservice anymore because the error has to do with the parsing of the WSDL file.... which probrably doesnt exist.
Im just trying to get a working example of using a third party webservice to return a value to be displayed in the database.... know of any good examples? The ones im using seem to be pretty out dated... the barnes and nobles example just times out.... -
We are evaluating the Cluster features of WebLogic and got a eval
license for the Cluster Support.
I am running a default cluster (mycluster) using the default Multicast
address (237.0.0.1) and am seeing
some strange behaviour/errors.
Would appreciate some asistance in this matter.
Our Environment
I created directory in a shared file system to host the cluster.
(h:\kkanth\weblogic)
Created the mycluster directory and other directories as recommended in
the Administrator's guide.
I have two WL Servers (asera190 and asera162) with permanent IP
addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
I'm using a NES proxy on asera190 with the plugin for WL specified in
obj.conf alongwith the other parameters.
I'm able to have both the servers join to cluster mycluster and the WL
Admin Console does display a tree that depicts the cluster as well as
servers in it (server61 and server70). The individual server directories
are being created in h:\kkanth\weblogic\mycluster directory with the
appropriate access.log and weblogic.log files.
When a browser attempts to access a URL such as
http://asera190/weblogic/snoop it does return the proper response, but
all requests are processed by asera162 which is listed first in the
obj.conf. Opening multiple sessions does not cause the requests to be
sent to asera190 which is the second server in the cluster. When
asera162 is shutdown and removed from the cluster, I hoped that
subsequent requests would go to asera190. However , depending on the
origin of the request, different errors were thrown. If I try to access
http://asera190/weblogic/snoop from a browser on asera190, I get an
error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
from asera162 cause "Failure at line 706 of file proxy.cpp".
I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
directory as well as the obj.conf file in the ....\config\ directory of
asera190.
We are running NES 3.5.1 and have setup proxy35.dll appropriately.
weblogic.properties
# THE WEBLOGIC PROPERTIES FILE
# This file, which conforms to the java.util.Properties file
# definition, configures your WebLogic products. You cannot run
# WebLogic Server without setting required configuration properties in
this
# file. Required properties are marked and appear first in the file.
# Details on each entry and important information about configuration
# and security are documented on our website. Please go to:
# http://www.weblogic.com/docs45/admindocs/properties.html
# for full instructions on how to edit this file.
# You do not need to include properties in this file unless you want to
# change the default, embedded property. Some properties on the
# T3AdminProps page are not listed here because the default property
# is being used. You can change the default by adding the property and
# its value to this file.
# You cannot set weblogic.system.home in this file, since the WebLogic
Server
# must know where home is in order to retrieve this file. You can
# change WebLogic home on the command line when you start the
# WebLogic Server.
# CLUSTER USERS: Note that the (shared) per-cluster properties file
should
# contain most all of the properties in this file. The only properties
# that potentially belong in a per-server properties file for a server
# running in a cluster are the registration (startup class) of pinned
# RMI objects, and a few tuning properties that may be different for
# servers in the cluster, depending upon hardware and memory. If you use
# a per-server properties file, please REMOVE all properties except
those
# that are specifically required in the per-server properties file. You
# can find specific notes on clusters by searching through this file for
# "CLUSTER USERS".
# The way this file is organized:
# Core properties (includes REQUIRED and RECOMMENDED)
# Core system properties
# Core security-related properties
# Core security-related properties for SSL
# Core HTTPD administrative properties
# Optional properties
# Administrator properties
# System properties
# System startup files
# System shutdown files
# Security-related properties for Workspaces
# Jolt for WebLogic properties
# WebLogic Enterprise Connectivity properties
# WebLogic File properties
# WebLogic JMS demo properties
# WebLogic RMI demo properties
# WebLogic EJB demo properties
# WebLogic ZAC demo properties
# HTTPD administrative properties
# WebLogic JDBC driver properties
# WebLogic JDBC connection pool management
# WebLogic demo connection pool
# WebLogic HTTP Servlet properties
# Proxy servlet registration
# Classpath servlet registration
# File servlet registration
# ServerSideInclude servlet registration
# PageCompileServlet (used by JHTML)
# JSPServlet (used by JSP)
# ServletServlet registration
# Servlet reload properties
# Servlet ACLs
# WebLogic JHTML properties
# User-written and demo servlet registrations
# CORE PROPERTIES
# You should set these before you start the WebLogic Server the first
time.
# If you need more instructions on individual properties in this
# section, check the same section in the Optional Properties, where
# we've left the long explanations. Or, better yet, go to our
# website and read all about properties, at:
# http://www.weblogic.com/docs45/admindocs/properties.html
# CORE SYSTEM PROPERTIES
# TCP/IP port number at which the WebLogic Server listens for
connections
weblogic.system.listenPort=7001
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs45/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8
characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.password.system=kaykayka
# RECOMMEND Set to 'everyone' if HTTPD is enabled
weblogic.allow.execute.weblogic.servlet=everyone
# Set individual ACLs to restrict access to HTTP-related resources,
# such as the Administration servlets.
# To make your own servlets generally available, follow this
# pattern (provide a weblogic.allow.execute) for your packages and
# set ACLs as appropriate.
# CORE SECURITY-RELATED PROPERTIES FOR SSL
# Read important information about SSL at:
# http://www.weblogic.com/docs45/classdocs/API_secure.html
# Enable SSL
# (default if property not defined is false)
weblogic.security.ssl.enable=true
# SSL listen port
weblogic.system.SSLListenPort=7002
# Servlets for SSL
# Authentication servlet for creating tokens for applets
weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
# Limits number of unclaimed stored tokens
weblogic.security.certificateCacheSize=3
# Capture CA root of client servlet
weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
# Certificates for SSL
# Name of acceptable CA roots
# For client authentication change value to a valid .pem file
#weblogic.security.clientRootCA=SecureServerCA.pem
# Server certificates for SSL
weblogic.security.certificate.server=democert.pem
weblogic.security.key.server=demokey.pem
weblogic.security.certificate.authority=ca.pem
# registration for certificate generator servlet
weblogic.httpd.register.Certificate=utils.certificate
weblogic.allow.execute.weblogic.servlet.Certificate=system
# CORE HTTPD ADMINISTRATIVE PROPERTIES
# True permits the HTTPD to run (default)
# Uncomment this property to disable HTTPD
#weblogic.httpd.enable=false
# If authentication is required, add username/password for each user
# who will be included in an ACL, as in this commented-out example:
#weblogic.password.peter=#8gjsL4*
# OPTIONAL PROPERTIES
# These properties affect the behavior of the WebLogic Server.
# You only need to set these properties if you want
# to change the default setting, which is the property shown.
# ADMINISTRATOR PROPERTIES
# Administrator properties are optional information properties,
# particularly useful for clusters.
#weblogic.administrator.location=3355 California Drive, West Hampshire,
CA 94104
#weblogic.administrator.name=Joe Administrator
#weblogic.administrator.phone=1 415 555 1234
# SYSTEM PROPERTIES
# System properties in this section are set to system defaults
# Performance pack. The shared library must be accessible from your
# PATH (NT) or from your shared library path (UNIX; the name of the
# variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
weblogic.system.nativeIO.enable=true
# Outputs logging information to the console as well as to the log file
weblogic.system.enableConsole=true
# Sets the directory or URL for the WebLogic Admin help pages
# The help pages are shipped in the "docs/adminhelp" directory, in the
# default document root in public_html
weblogic.system.helpPageURL=d:/weblogic/myserver/public_html/docs/adminhelp/
# If you prefer to access the most recent help pages, you can do so
online
# by commenting out the previous property and uncommenting this one:
#weblogic.system.helpPageURL=http://www.weblogic.com/docs45/adminhelp/
# Properties for tuning the server's performance
# Number of WebLogic Server execute threads.
weblogic.system.executeThreadCount=15
# Other optional system properties
# Limits size of weblogic.log (in K) and versions old log
weblogic.system.maxLogFileSize=1024
# Adjust minimum length of password
weblogic.system.minPasswordLen=8
# UNIX only: If running on port 80 on UNIX, enable the setUID program
#weblogic.system.enableSetUID=false
# UNIX only: Unprivileged user to setUID to after starting up
# WebLogic Server on port 80
#weblogic.system.nonPrivUser=nobody
# CLUSTER-SPECIFIC PROPERTIES
# Cluster-specific properties in this section are set to system
defaults.
# CLUSTER USERS: Note that ALL Cluster-specific properties should be set
# in the per-cluster properties file ONLY.
# Time-to-live (number of hops) for the cluster's multicast messages
# (default 1, range 1-255).
#weblogic.cluster.multicastTTL=1
# Sets the load-balancing algorithm to be used between
# replicated services if none is specified. If not specified,
# round-robin is used.
#weblogic.cluster.defaultLoadAlgorithm=round-robin
# SERVER-SPECIFIC CLUSTER PROPERTIES
# Cluster-related properties in this section are set to system defaults.
# CLUSTER USERS: Note that these server-specific cluster-related
properties
# should be set in the per-server properties file ONLY.
# Sets the weight of the individual server for the weight-based
load-balancing.
# Range is 0 - 100.
# Larger numbers increase the amount of traffic routed to this server.
#weblogic.system.weight=100
# SYSTEM STARTUP FILES - Examples
# CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
# objects should be registered in the per-server properties file.
# All other startup classes should be registered in the per-cluster
# properties file.
# For more info on writing and using startup file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs45/classdocs/API_t3.html
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
# This example shows the entry for examples/t3client/StartupQuery.java
#weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
#weblogic.system.startupArgs.doquery=\
# query=select * from emp,\
# db=jdbc:weblogic:pool:demoPool
# Other system startup files for use with VisiBroker
# Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
# You must have installed Visigenic 2.5 for use with
# the WebLogic Server before you uncomment these properties
#weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
#weblogic.system.startupArgs.dovisi=\
# clientName=T3Client Manager,\
# connName=T3Connection Manager
# SYSTEM SHUTDOWN FILES - Examples
# For more info on writing and using shutdown file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs45/classdocs/API_t3.html
# Register a shutdown class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
# Add arguments for the shutdown class
#weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
# This example shows the entry for examples/t3client/ShutdownTest.java
#weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
#weblogic.system.shutdownArgs.ShutdownTest=\
# outfile=c:/temp/shutdown.log
# SECURITY-RELATED PROPERTIES FOR WORKSPACES
# For backward compatibility, the following entries disable Access
# Control on Workspaces
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
# JOLT FOR WEBLOGIC PROPERTIES
# These properties configure a BEA Jolt connection pool for use with
# the simpapp and bankapp examples, and register a servlet for use with
# with the simpapp example. The default server address provided here
# points to a public TUXEDO server that is hosted by BEA for use with
# this example.
# Servlet registration for simpapp example:
#weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServlet
# Pool creation and cleanup
# note this example is set up to work with the public
# demo TUXEDO server available from BEA's website:
#weblogic.system.startupClass.demojoltpoolStart=\
# bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
#weblogic.system.startupArgs.demojoltpoolStart=\
# poolname=demojoltpool,\
# appaddrlist=//beademo1.beasys.com:8000,\
# failoverlist=//beademo1.beasys.com:8000,\
# minpoolsize=1,\
# maxpoolsize=3
#weblogic.system.shutdownClass.demojoltpoolStop=\
# bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
#weblogic.system.shutdownArgs.demojoltpoolStop=\
# poolname=demojoltpool
# WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
# The registrations enable a BEA IIOP connection pool and
# register servlets for use with the simpapp and university examples.
# Configure for your environment and uncomment to use.
# Uncommenting these properties requires WebLogic Enterprise
Connectivity
# and an operating WebLogic Enterprise Server.
# Servlet registration for simpapp servlet example
#weblogic.httpd.register.SimpappServlet=\
# examples.wlec.servlets.simpapp.SimpappServlet
#weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
# Servlet registration for simpapp EJB example
# (You'll need to add the wlec_ejb_simpapp.jar to the
# weblogic.ejb.deploy property in this file.)
#weblogic.httpd.register.ejbSimpappServlet=\
# examples.wlec.ejb.simpapp.ejbSimpappServlet
#weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
# Pool creation and cleanup for the simpapp example
#weblogic.CORBA.connectionPool.simplepool=\
# appaddrlist=//wlehost:2468,\
# failoverlist=//wlehost:2468,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# domainname=simpapp
# Servlet registration for university Servlet example:
#weblogic.httpd.register.UniversityServlet=\
# examples.wlec.servlets.university.UniversityServlet
#weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
# Pool creation and cleanup for the University example:
#weblogic.CORBA.connectionPool.Univpool=\
# appaddrlist=//wlehost:2498,\
# failoverlist=//wlehost:2498,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# apppassword=wlepassword,\
# domainname=university
# WEBLOGIC FILE PROPERTIES
# Maps a volume name to a path, for client file read/write
#weblogic.io.fileSystem.[volumeName]=[fullPathName]
# WEBLOGIC JMS DEMO PROPERTIES
# CLUSTER USERS: Note that ALL JMS deployment should be done in the
# per-cluster properties file ONLY.
# You set up a JDBC connection pool if you want persistent messages
# (including durable subscriptions). To use JMS and EJBs in the same
# transaction, both must use the same JDBC connection pool. Uncomment
# the following property to use the default JDBC connection pool
# 'demo', which is defined in the Demo connection pool section of this
file.
#weblogic.jms.connectionPool=demoPool
# The JMS Webshare example demonstrates how the ClientID for a
# durable subscriber is configured in the connection factory:
#weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
#weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
#weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
#weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
# The JMS trader example shows how to use JMS with an EJB. In addition
# to uncommenting the following properties, you must also set up and
# deploy the EJB example examples.ejb.basic.statefulSession.Trader to
# try out this JMS example:
#weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
#weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
#weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
#weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
# Registers the underlying servlet
#weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
# These properties are used with the ServerReceive JMS example,
# which demonstrates how to establish a JMS message consumer
# in a startup class:
#weblogic.system.startupClass.serverReceive=\
# examples.jms.startup.ServerReceive
#weblogic.system.startupArgs.serverReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# These properties are used with the PoolReceive JMS example,
# which demonstrates how to establish a pool of JMS message consumers
# in a startup class:
#weblogic.system.startupClass.poolReceive=\
# examples.jms.startup.PoolReceive
#weblogic.system.startupArgs.poolReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# WEBLOGIC RMI DEMO PROPERTIES
# CLUSTER USERS: Note that pinned RMI objects should be registered
# in the per-server properties file ONLY. All other RMI startup
# classes should be registered in the per-cluster properties file.
# Remote classes registered at startup after the pattern:
#weblogic.system.startupClass.[virtualName]=[fullPackageName]
# These examples can be compiled to see RMI in action. Uncomment to use:
#weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
#weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
# WEBLOGIC EJB DEMO PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# See WebLogic Demo Connection Pool below for a connection pool
# to use with these examples.
# Deploys EJBeans. Uncomment the appropriate lines below and
# modify DBMS-related info and paths to match your particular
installation:
#weblogic.ejb.deploy=\
# d:/weblogic/myserver/cluster_ejb.jar, \
# d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
# d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
# d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
# d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
# d:/weblogic/myserver/ejb_extensions_isModified.jar, \
# d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
# d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
# d:/weblogic/myserver/ejb_sequence_oracle.jar, \
# d:/weblogic/myserver/ejb_subclass.jar, \
# d:/weblogic/myserver/jolt_ejb_bankapp.jar
# Servlets used by the EJB basic examples beanManaged and
# containerManaged. Uncomment to use:
#weblogic.httpd.register.beanManaged=\
# examples.ejb.basic.beanManaged.Servlet
#weblogic.httpd.register.containerManaged=\
# examples.ejb.basic.containerManaged.Servlet
# Add a list of users (set the password with
weblogic.password.[username]=XXX)
# to set an ACL for this servlet:
#weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
#weblogic.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
#weblogic.password.user1=user1Password
#weblogic.password.user2=user2Password
# WEBLOGIC ZAC DEMO PROPERTIES
# These registrations enable the ZAC Publish Wizard.
weblogic.zac.enable=true
# Set the publish root for a WebLogic Server. Edit and
# uncomment to use
#weblogic.zac.publishRoot=d:/weblogic/zac
# Set an ACL for each package you publish. The [name] is
# the "Package name" you assign in the ZAC Publish Wizard.
# Publish a package, edit this property, and uncomment to use.
#weblogic.allow.read.weblogic.zac.[name]=[user list]
#weblogic.allow.write.weblogic.zac.[name]=system
# HTTPD ADMINISTRATIVE PROPERTIES
# Enables logging of HTTPD info in common log format and
# sets the log file name (default is "access.log" in "myserver")
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
# Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
weblogic.httpd.enableEvents=false
# Enables HTTP sessions
weblogic.httpd.session.enable=true
# Sets an optional cookie name. The default name is "WebLogicSession".
# Prior to version 4.0, the default was "TengahSession". To make
# this backward compatible with cookies generated from previous
# installations, you should set this property to "TengahSession".
# Uncomment this line and set this to any string of your choice,
# or comment out this property to use the default.
#weblogic.httpd.session.cookie.name=WebLogicSession
# MIME types
weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.image/gif=gif
weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.application/pdf=pdf
weblogic.httpd.mimeType.application/zip=zip
weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.application/x-java-archive=jar
weblogic.httpd.mimeType.application/x-java-serialized-object=ser
weblogic.httpd.mimeType.application/octet-stream=exe
# In seconds, the keep-alive for HTTP and HTTPS requests
weblogic.httpd.http.keepAliveSecs=60
weblogic.httpd.https.keepAliveSecs=120
# WEBLOGIC JDBC DRIVER PROPERTIES
# Enables JDBC driver logging and sets the file name for the log
# The weblogic.jdbc.logFile is placed in the per-server
# directory (default is "myserver")
weblogic.jdbc.enableLogFile=false
weblogic.jdbc.logFileName=jdbc.log
# WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# For creating JDBC connection pools. This example shows a connection
# pool called "oraclePool" that allows 3 T3Users "guest," "joe," and
"jill"
# to use 4 JDBC connections (with a potential for up to 10 connections,
# incremented by two at a time, with a delay of 1 second between each
# attempt to connect to the database), to an Oracle database server
called
# "DEMO." If more than 4 connections are opened, after 15 minutes,
unused
# connections are dropped from the pool until only 4 connections remain
open.
# Every 10 minutes, any unused connections in the pool are tested and
# refreshed if they are not viable.
#weblogic.jdbc.connectionPool.oraclePool=\
# url=jdbc:weblogic:oracle,\
# driver=weblogic.jdbc.oci.Driver,\
# loginDelaySecs=1,\
# initialCapacity=4,\
# maxCapacity=10,\
# capacityIncrement=2,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshMinutes=10,\
# testTable=dual,\
# props=user=SCOTT;password=tiger;server=DEMO
# Get more details on each argument for this property in the
# Administrators Guide on setting properties at:
# http://www.weblogic.com/docs45/admindocs/properties.html
# Set up ACLs for this connection pool with the following:
#weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
# guest,joe,jill
#weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
#weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
# This property is an ACL that specifies the users who can
# create dynamic connection poolsTry the following obj.conf file. By the way why are using NES 35 version. If you are using NES 36 you should use proxy36.dll.
Init fn="load-types" mime-types="mime.types"
Init fn="load-modules" funcs="wl-proxy,wl-init" shlib="d:/weblogic/bin/proxy35.dll"
Init fn="wl-init"
Init access="C:/Netscape/SuiteSpot/https-octavia/logs/accessNewELF" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%
\"%Req->headers.referer%\" \"%Req->headers.user-agent%\" %Req->reqpb.method% %Req->reqpb.uri% %Req->reqpb.query% \"%Req->reqpb.protocol%\"" fn="flex-init"
<Object name="tg" ppath="*/weblogic/*">
Service fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001" PathTrim="/weblogic"
</Object>
<Object name="default">
NameTrans fn="pfx2dir" from="/ns-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
NameTrans fn="pfx2dir" from="/mc-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
NameTrans fn="pfx2dir" from="/help" dir="C:/Netscape/SuiteSpot/manual/https/ug"
NameTrans fn="document-root" root="C:/Netscape/SuiteSpot/docs"
PathCheck fn="nt-uri-clean"
PathCheck fn="check-acl" acl="default"
PathCheck fn="find-pathinfo"
PathCheck fn="find-index" index-names="index.html,home.html"
ObjectType fn="type-by-extension"
ObjectType fn="force-type" type="text/plain"
Service method="(GET|HEAD|POST|PUT)" type="text/jsp" fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001"
Service method="(GET|HEAD)" type="magnus-internal/imagemap" fn="imagemap"
Service method="(GET|HEAD)" type="magnus-internal/directory" fn="index-common"
Service method="(GET|HEAD)" type="*~magnus-internal/*" fn="send-file"
AddLog fn="flex-log" name="access"
</Object>
<Object ppath="/usr/suitespot/docs/.perf">
Service fn="service-dump"
</Object>
<Object name="cgi">
ObjectType fn="force-type" type="magnus-internal/cgi"
Service fn="send-cgi"
</Object>
Hope this helps
Krishna Kanth wrote:
> We are evaluating the Cluster features of WebLogic and got a eval
> license for the Cluster Support.
> I am running a default cluster (mycluster) using the default Multicast
> address (237.0.0.1) and am seeing
> some strange behaviour/errors.
> Would appreciate some asistance in this matter.
>
> Our Environment
> ----------------
>
> I created directory in a shared file system to host the cluster.
> (h:\kkanth\weblogic)
> Created the mycluster directory and other directories as recommended in
> the Administrator's guide.
>
> I have two WL Servers (asera190 and asera162) with permanent IP
> addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
> I'm using a NES proxy on asera190 with the plugin for WL specified in
> obj.conf alongwith the other parameters.
>
> I'm able to have both the servers join to cluster mycluster and the WL
> Admin Console does display a tree that depicts the cluster as well as
> servers in it (server61 and server70). The individual server directories
> are being created in h:\kkanth\weblogic\mycluster directory with the
> appropriate access.log and weblogic.log files.
>
> When a browser attempts to access a URL such as
>
> http://asera190/weblogic/snoop it does return the proper response, but
> all requests are processed by asera162 which is listed first in the
> obj.conf. Opening multiple sessions does not cause the requests to be
> sent to asera190 which is the second server in the cluster. When
> asera162 is shutdown and removed from the cluster, I hoped that
> subsequent requests would go to asera190. However , depending on the
> origin of the request, different errors were thrown. If I try to access
> http://asera190/weblogic/snoop from a browser on asera190, I get an
> error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
> from asera162 cause "Failure at line 706 of file proxy.cpp".
>
> I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
> directory as well as the obj.conf file in the ....\config\ directory of
> asera190.
>
> We are running NES 3.5.1 and have setup proxy35.dll appropriately.
>
> weblogic.properties
> *********
> # THE WEBLOGIC PROPERTIES FILE
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # This file, which conforms to the java.util.Properties file
> # definition, configures your WebLogic products. You cannot run
> # WebLogic Server without setting required configuration properties in
> this
> # file. Required properties are marked and appear first in the file.
> #
> # Details on each entry and important information about configuration
> # and security are documented on our website. Please go to:
> #
> # http://www.weblogic.com/docs45/admindocs/properties.html
> #
> # for full instructions on how to edit this file.
> #
> # You do not need to include properties in this file unless you want to
> # change the default, embedded property. Some properties on the
> # T3AdminProps page are not listed here because the default property
> # is being used. You can change the default by adding the property and
> # its value to this file.
> #
> # You cannot set weblogic.system.home in this file, since the WebLogic
> Server
> # must know where home is in order to retrieve this file. You can
> # change WebLogic home on the command line when you start the
> # WebLogic Server.
> #
> # CLUSTER USERS: Note that the (shared) per-cluster properties file
> should
> # contain most all of the properties in this file. The only properties
> # that potentially belong in a per-server properties file for a server
> # running in a cluster are the registration (startup class) of pinned
> # RMI objects, and a few tuning properties that may be different for
> # servers in the cluster, depending upon hardware and memory. If you use
>
> # a per-server properties file, please REMOVE all properties except
> those
> # that are specifically required in the per-server properties file. You
> # can find specific notes on clusters by searching through this file for
>
> # "CLUSTER USERS".
> #
> # -------------------------------------------------
> # The way this file is organized:
> # Core properties (includes REQUIRED and RECOMMENDED)
> # Core system properties
> # Core security-related properties
> # Core security-related properties for SSL
> # Core HTTPD administrative properties
> #
> # Optional properties
> # Administrator properties
> # System properties
> # System startup files
> # System shutdown files
> # Security-related properties for Workspaces
> # Jolt for WebLogic properties
> # WebLogic Enterprise Connectivity properties
> # WebLogic File properties
> # WebLogic JMS demo properties
> # WebLogic RMI demo properties
> # WebLogic EJB demo properties
> # WebLogic ZAC demo properties
> # HTTPD administrative properties
> # WebLogic JDBC driver properties
> # WebLogic JDBC connection pool management
> # WebLogic demo connection pool
> # WebLogic HTTP Servlet properties
> # Proxy servlet registration
> # Classpath servlet registration
> # File servlet registration
> # ServerSideInclude servlet registration
> # PageCompileServlet (used by JHTML)
> # JSPServlet (used by JSP)
> # ServletServlet registration
> # Servlet reload properties
> # Servlet ACLs
> # WebLogic JHTML properties
> # User-written and demo servlet registrations
> # -------------------------------------------------
>
> #################################################################
> # CORE PROPERTIES
> # -------------------------------------------------
> # You should set these before you start the WebLogic Server the first
> time.
> # If you need more instructions on individual properties in this
> # section, check the same section in the Optional Properties, where
> # we've left the long explanations. Or, better yet, go to our
> # website and read all about properties, at:
> # http://www.weblogic.com/docs45/admindocs/properties.html
> #################################################################
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE SYSTEM PROPERTIES
> # -------------------------------------------------
> # TCP/IP port number at which the WebLogic Server listens for
> connections
> weblogic.system.listenPort=7001
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE SECURITY-RELATED PROPERTIES
> # -------------------------------------------------
> # Read important information about security at:
> #
> # http://www.weblogic.com/docs45/admindocs/properties.html
> #
> # REQUIRED: The system password MUST be set in order to start the
> # WebLogic Server. This password is case-sensitive, at least 8
> characters.
> # The username for the privileged user is ALWAYS "system".
> # This username and password also includes httpd access (see
> # HTTPD properties below).
> weblogic.password.system=kaykayka
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # RECOMMEND Set to 'everyone' if HTTPD is enabled
> weblogic.allow.execute.weblogic.servlet=everyone
> # Set individual ACLs to restrict access to HTTP-related resources,
> # such as the Administration servlets.
> # To make your own servlets generally available, follow this
> # pattern (provide a weblogic.allow.execute) for your packages and
> # set ACLs as appropriate.
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE SECURITY-RELATED PROPERTIES FOR SSL
> # ------------------------------------------------
> # Read important information about SSL at:
> #
> # http://www.weblogic.com/docs45/classdocs/API_secure.html
> #
> # Enable SSL
> # (default if property not defined is false)
> weblogic.security.ssl.enable=true
> #
> # SSL listen port
> weblogic.system.SSLListenPort=7002
>
> # Servlets for SSL
> # ------------------------------------------------
> # Authentication servlet for creating tokens for applets
> weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
>
> # Limits number of unclaimed stored tokens
> weblogic.security.certificateCacheSize=3
> # Capture CA root of client servlet
> weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
>
> # Certificates for SSL
> # ------------------------------------------------
> # Name of acceptable CA roots
> # For client authentication change value to a valid .pem file
> #weblogic.security.clientRootCA=SecureServerCA.pem
> #
> # Server certificates for SSL
> # ------------------------------------------------
> weblogic.security.certificate.server=democert.pem
> weblogic.security.key.server=demokey.pem
> weblogic.security.certificate.authority=ca.pem
>
> # registration for certificate generator servlet
> weblogic.httpd.register.Certificate=utils.certificate
> weblogic.allow.execute.weblogic.servlet.Certificate=system
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE HTTPD ADMINISTRATIVE PROPERTIES
> # ------------------------------------------------
> # True permits the HTTPD to run (default)
> # Uncomment this property to disable HTTPD
> #weblogic.httpd.enable=false
> #
> # If authentication is required, add username/password for each user
> # who will be included in an ACL, as in this commented-out example:
> #weblogic.password.peter=#8gjsL4*
>
> #################################################################
> # OPTIONAL PROPERTIES
> # ------------------------------------------------
> # These properties affect the behavior of the WebLogic Server.
> # You only need to set these properties if you want
> # to change the default setting, which is the property shown.
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # ADMINISTRATOR PROPERTIES
> # ------------------------------------------------
> # Administrator properties are optional information properties,
> # particularly useful for clusters.
> #weblogic.administrator.location=3355 California Drive, West Hampshire,
> CA 94104
> #weblogic.administrator.name=Joe Administrator
> #weblogic.administrator.phone=1 415 555 1234
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SYSTEM PROPERTIES
> # ------------------------------------------------
> # System properties in this section are set to system defaults
>
> # Performance pack. The shared library must be accessible from your
> # PATH (NT) or from your shared library path (UNIX; the name of the
> # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
> weblogic.system.nativeIO.enable=true
>
> # Outputs logging information to the console as well as to the log file
> weblogic.system.enableConsole=true
>
> # Sets the directory or URL for the WebLogic Admin help pages
> # The help pages are shipped in the "docs/adminhelp" directory, in the
> # default document root in public_html
> weblogic.system.helpPageURL=d:/weblogic/myserver/public_html/docs/adminhelp/
>
> # If you prefer to access the most recent help pages, you can do so
> online
> # by commenting out the previous property and uncommenting this one:
> #weblogic.system.helpPageURL=http://www.weblogic.com/docs45/adminhelp/
>
> # Properties for tuning the server's performance
> # ------------------------------------------------
> # Number of WebLogic Server execute threads.
> weblogic.system.executeThreadCount=15
>
> # Other optional system properties
> # ------------------------------------------------
> # Limits size of weblogic.log (in K) and versions old log
> weblogic.system.maxLogFileSize=1024
>
> # Adjust minimum length of password
> weblogic.system.minPasswordLen=8
>
> # UNIX only: If running on port 80 on UNIX, enable the setUID program
> #weblogic.system.enableSetUID=false
>
> # UNIX only: Unprivileged user to setUID to after starting up
> # WebLogic Server on port 80
> #weblogic.system.nonPrivUser=nobody
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CLUSTER-SPECIFIC PROPERTIES
> # ------------------------------------------------
> # Cluster-specific properties in this section are set to system
> defaults.
> # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
>
> # in the per-cluster properties file ONLY.
> #
> # Time-to-live (number of hops) for the cluster's multicast messages
> # (default 1, range 1-255).
> #weblogic.cluster.multicastTTL=1
> #
> # Sets the load-balancing algorithm to be used between
> # replicated services if none is specified. If not specified,
> # round-robin is used.
> #weblogic.cluster.defaultLoadAlgorithm=round-robin
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SERVER-SPECIFIC CLUSTER PROPERTIES
> # ------------------------------------------------
> # Cluster-related properties in this section are set to system defaults.
>
> # CLUSTER USERS: Note that these server-specific cluster-related
> properties
> # should be set in the per-server properties file ONLY.
> #
> # Sets the weight of the individual server for the weight-based
> load-balancing.
> # Range is 0 - 100.
> # Larger numbers increase the amount of traffic routed to this server.
> #weblogic.system.weight=100
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SYSTEM STARTUP FILES - Examples
> # ------------------------------------------------
> # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
> # objects should be registered in the per-server properties file.
> # All other startup classes should be registered in the per-cluster
> # properties file.
> #
> # For more info on writing and using startup file, see the
> # Developers Guide "Writing a WebLogic Client application," at
> # http://www.weblogic.com/docs45/classdocs/API_t3.html
> #
> # Register a startup class by giving it a virtual name and
> # supplying its full pathname.
> #weblogic.system.startupClass.[virtual_name]=[full_pathname]
> #
> # Add arguments for the startup class
> #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
> #
> # This example shows the entry for examples/t3client/StartupQuery.java
> #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
> #weblogic.system.startupArgs.doquery=\
> # query=select * from emp,\
> # db=jdbc:weblogic:pool:demoPool
> #
> # Other system startup files for use with VisiBroker
> # ------------------------------------------------
> # Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
> # You must have installed Visigenic 2.5 for use with
> # the WebLogic Server before you uncomment these properties
> #weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
>
> #weblogic.system.startupArgs.dovisi=\
> # clientName=T3Client Manager,\
> # connName=T3Connection Manager
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SYSTEM SHUTDOWN FILES - Examples
> # ------------------------------------------------
> # For more info on writing and using shutdown file, see the
> # Developers Guide "Writing a WebLogic Client application," at
> # http://www.weblogic.com/docs45/classdocs/API_t3.html
> #
> # Register a shutdown class by giving it a virtual name and
> # supplying its full pathname.
> #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
> #
> # Add arguments for the shutdown class
> #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
> #
> # This example shows the entry for examples/t3client/ShutdownTest.java
> #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
>
> #weblogic.system.shutdownArgs.ShutdownTest=\
> # outfile=c:/temp/shutdown.log
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SECURITY-RELATED PROPERTIES FOR WORKSPACES
> # ------------------------------------------------
> # For backward compatibility, the following entries disable Access
> # Control on Workspaces
> weblogic.allow.read.weblogic.workspace=everyone
> weblogic.allow.write.weblogic.workspace=everyone
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # JOLT FOR WEBLOGIC PROPERTIES
> # ------------------------------------------------
> # These properties configure a BEA Jolt connection pool for use with
> # the simpapp and bankapp examples, and register a servlet for use with
> # with the simpapp example. The default server address provided here
> # points to a public TUXEDO server that is hosted by BEA for use with
> # this example.
> #
> # Servlet registration for simpapp example:
> # ------------------------------------------------
> #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServlet
>
> #
> # Pool creation and cleanup
> # note this example is set up to work with the public
> # demo TUXEDO server available from BEA's website:
> # ------------------------------------------------
> #weblogic.system.startupClass.demojoltpoolStart=\
> # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
> #weblogic.system.startupArgs.demojoltpoolStart=\
> # poolname=demojoltpool,\
> # appaddrlist=//beademo1.beasys.com:8000,\
> # failoverlist=//beademo1.beasys.com:8000,\
> # minpoolsize=1,\
> # maxpoolsize=3
> #
> #weblogic.system.shutdownClass.demojoltpoolStop=\
> # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
> #weblogic.system.shutdownArgs.demojoltpoolStop=\
> # poolname=demojoltpool
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
> # ------------------------------------------------
> # The registrations enable a BEA IIOP connection pool and
> # register servlets for use with the simpapp and university examples.
> # Configure for your environment and uncomment to use.
> # Uncommenting these properties requires WebLogic Enterprise
> Connectivity
> # and an operating WebLogic Enterprise Server.
> #
> # Servlet registration for simpapp servlet example
> # ------------------------------------------------
> #weblogic.httpd.register.SimpappServlet=\
> # examples.wlec.servlets.simpapp.SimpappServlet
> #
> #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
> #
> # Servlet registration for simpapp EJB example
> # (You'll need to add the wlec_ejb_simpapp.jar to the
> # weblogic.ejb.deploy property in this file.)
> # --------------------------------------------
> #weblogic.httpd.register.ejbSimpappServlet=\
> # examples.wlec.ejb.simpapp.ejbSimpappServlet
> #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
> #
> # Pool creation and cleanup for the simpapp example
> # -------------------------------------------------
> #weblogic.CORBA.connectionPool.simplepool=\
> # appaddrlist=//wlehost:2468,\
> # failoverlist=//wlehost:2468,\
> # minpoolsize=2,\
> # maxpoolsize=3,\
> # username=wleuser,\
> # userrole=developer,\
> # domainname=simpapp
> #
> # Servlet registration for university Servlet example:
> # ---------------------------------------------------
> #weblogic.httpd.register.UniversityServlet=\
> # examples.wlec.servlets.university.UniversityServlet
> #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
> #
> # Pool creation and cleanup for the University example:
> # ----------------------------------------------------
> #weblogic.CORBA.connectionPool.Univpool=\
> # appaddrlist=//wlehost:2498,\
> # failoverlist=//wlehost:2498,\
> # minpoolsize=2,\
> # maxpoolsize=3,\
> # username=wleuser,\
> # userrole=developer,\
> # apppassword=wlepassword,\
> # domainname=university
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC FILE PROPERTIES
> # ------------------------------------------------
> # Maps a volume name to a path, for client file read/write
> #weblogic.io.fileSystem.[volumeName]=[fullPathName]
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC JMS DEMO PROPERTIES
> # -------------------------------------------------
> # CLUSTER USERS: Note that ALL JMS deployment should be done in the
> # per-cluster properties file ONLY.
> #
> # You set up a JDBC connection pool if you want persistent messages
> # (including durable subscriptions). To use JMS and EJBs in the same
> # transaction, both must use the same JDBC connection pool. Uncomment
> # the following property to use the default JDBC connection pool
> # 'demo', which is defined in the Demo connection pool section of this
> file.
> #
> #weblogic.jms.connectionPool=demoPool
> #
> # The JMS Webshare example demonstrates how the ClientID for a
> # durable subscriber is configured in the connection factory:
> #
> #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
> #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
>
> #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
> #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
> #
> # The JMS trader example shows how to use JMS with an EJB. In addition
> # to uncommenting the following properties, you must also set up and
> # deploy the EJB example examples.ejb.basic.statefulSession.Trader to
> # try out this JMS example:
> #
> #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
> #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
> #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
> #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
> #
> # Registers the underlying servlet
> #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
> #
> # These properties are used with the ServerReceive JMS example,
> # which demonstrates how to establish a JMS message consumer
> # in a startup class:
> #
> #weblogic.system.startupClass.serverReceive=\
> # examples.jms.startup.ServerReceive
> #weblogic.system.startupArgs.serverReceive=\
> # connectionFactory=javax.jms.TopicConnectionFactory,\
> # topic=javax.jms.exampleTopic
> #
> # These properties are used with the PoolReceive JMS example,
> # which demonstrates how to establish a pool of JMS message consumers
> # in a startup class:
> #weblogic.system.startupClass.poolReceive=\
> # examples.jms.startup.PoolReceive
> #weblogic.system.startupArgs.poolReceive=\
> # connectionFactory=javax.jms.TopicConnectionFactory,\
> # topic=javax.jms.exampleTopic
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC RMI DEMO PROPERTIES
> # ------------------------------------------------
> # CLUSTER USERS: Note that pinned RMI objects should be registered
> # in the per-server properties file ONLY. All other RMI startup
> # classes should be registered in the per-cluster properties file.
> #
> # Remote classes registered at startup after the pattern:
> #weblogic.system.startupClass.[virtualName]=[fullPackageName]
> #
> # These examples can be compiled to see RMI in action. Uncomment to use:
>
> #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
>
> #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC EJB DEMO PROPERTIES
> # -------------------------------------------------
> # CLUSTER USERS: Note that ALL EJB deployment should be done in the
> # per-cluster properties file ONLY.
> #
> # See WebLogic Demo Connection Pool below for a connection pool
> # to use with these examples.
> #
> # Deploys EJBeans. Uncomment the appropriate lines below and
> # modify DBMS-related info and paths to match your particular
> installation:
> #weblogic.ejb.deploy=\
> # d:/weblogic/myserver/cluster_ejb.jar, \
> # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
> # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
> # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
> # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
> # d:/weblogic/myserver/ejb_extensions_isModified.jar, \
> # d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
>
> # d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
> # d:/weblogic/myserver/ejb_sequence_oracle.jar, \
> # d:/weblogic/myserver/ejb_subclass.jar, \
> # d:/weblogic/myserver/jolt_ejb_bankapp.jar
> #
> # Servlets used by the EJB basic examples beanManaged and
> # containerManaged. Uncomment to use:
> #weblogic.httpd.register.beanManaged=\
> # examples.ejb.basic.beanManaged.Servlet
> #weblogic.httpd.register.containerManaged=\
> # examples.ejb.basic.containerManaged.Servlet
> #
> # Add a list of users (set the password with
> weblogic.password.[username]=XXX)
> # to set an ACL for this servlet:
> #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
> #weblogic.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
>
> #weblogic.password.user1=user1Password
> #weblogic.password.user2=user2Password
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC ZAC DEMO PROPERTIES
> # -------------------------------------------------
> # These registrations enable the ZAC Publish Wizard.
> #
> weblogic.zac.enable=true
> #
> # Set the publish root for a WebLogic Server. Edit and
> # uncomment to use
> #
> #weblogic.zac.publishRoot=d:/weblogic/zac
> #
> # Set an ACL for each package you publish. The [name] is
> # the "Package name" you assign in the ZAC Publish Wizard.
> # Publish a package, edit this property, and uncomment to use.
> #weblogic.allow.read.weblogic.zac.[name]=[user list]
> #weblogic.allow.write.weblogic.zac.[name]=system
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # HTTPD ADMINISTRATIVE PROPERTIES
> # ------------------------------------------------
> # Enables logging of HTTPD info in common log format and
> # sets the log file name (default is "access.log" in "myserver")
> weblogic.httpd.enableLogFile=true
> weblogic.httpd.logFileName=access.log
>
> # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
> weblogic.httpd.enableEvents=false
>
> # Enables HTTP sessions
> weblogic.httpd.session.enable=true
>
> # Sets an optional cookie name. The default name is "WebLogicSession".
> # Prior to version 4.0, the default was "TengahSession". To make
> # this backward compatible with cookies generated from previous
> # installations, you should set this property to "TengahSession".
> # Uncomment t -
FRM-92101 in wu_test (the webutil demo form)
Error:
FRM-92101 in wu_test (the webutil demo form)
Problem:
I am attempting to run the wu_test form, downloaded with demos for webutil 1.02.
Running wu_test or another form containing webutil functions results in
FRM-92101 in the form's window and the following error in the OC4J console.
"Forms session <1> aborted: unable to communicate with runtime process."
Environment:
Java Client: Tried with both Sun Java Plug-In 1.4.2.04/5 and Jinitiator 1.3.1.17
Application Server: Oracle 9.0.4 iDS (Orion Development OC4J)
Database: Enterprise Edition 10.1.0.2.0
Forms Listener Servlet
Attempted Solutions:
I have scoured OTN & MetaLink & tried everything I could find with no luck. I
apologize for the length of this post, but I want to provide as much information
as possible re: what I've tried and my environment.
For instance, the remedy in Note 252600.1, which can cause these symptoms, did
not help.
This note states:
In webutil.cfg modify
install.syslib.location to an absolute URL, replacing the line:
install.syslib.location=/webutil
To an absolute URL like:
install.syslib.location=http://[host]:[port]/forms90/webutil
(replacing [host] and [port] with your own values) or
install.syslib.location=//../webutil
Other Information:
Other forms (ones that don't contain webutil functions/beans) run fine with the same
env and config used for webutil.
The wu_test form is already set up so first navigation item is not on the
webutil canvas, but on the "demo" canvas.
OC4J Console:
C:\Program Files\Common Files\System\MAPI\1033\nt>C:\Ora10giDS\jdk\bin\java -Xbo
otclasspath/p:C:\Ora10giDS\vbroker4\lib\vbjboot.jar -Doracle.security.jazn.confi
g=C:\Ora10giDS\j2ee\DevSuite\config\jazn.xml -Doracle.home=C:\Ora10giDS -DORACLE
_HOME=C:\Ora10giDS -jar C:\Ora10giDS\j2ee\home\oc4j.jar -userThreads -config C:\
Ora10giDS\j2ee\DevSuite\config\server.xml
04/07/29 15:46:09 Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)
initialized
04/07/29 15:46:19 FormsServlet init():
configFileName: C:\Ora10giDS/forms90/server/formsweb.cfg
testMode: false
04/07/29 15:46:35 ListenerServlet init()
04/07/29 15:46:51 Forms session <1> aborted: unable to communicate with runtime
process.
Orion webserver application.log:
04/07/29 15:46:07 Started
04/07/29 15:46:19 forms90web: jsp: init
04/07/29 15:46:19 forms90web: f90servlet: init
04/07/29 15:46:19 forms90web: FormsServlet init():
configFileName: C:\Ora10giDS/forms90/server/formsweb.cfg
testMode: false
04/07/29 15:46:19 forms90web: 9.0.4.0.0 Started
04/07/29 15:46:35 forms90web: l90servlet: init
04/07/29 15:46:35 forms90web: ListenerServlet init()
04/07/29 15:46:51 forms90web: Forms session <1> aborted: unable to communicate with runtime process.
04/07/29 15:46:51 forms90web: Forms session <1> exception stack trace:
java.io.IOException: FRM-93000: Unexpected internal error.
Details : No HTTP headers received from runform
at oracle.forms.servlet.ListenerServlet.forwardResponseFromRunform(Unknown Source)
at oracle.forms.servlet.ListenerServlet.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:765)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Java Console:
Java(TM) Plug-in: Version 1.4.2_05
Using JRE version 1.4.2_05 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\isellers
Proxy Configuration: No proxy
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
p: reload proxy configuration
q: hide console
r: reload policy configuration
s: dump system properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to <n>
RegisterWebUtil - Loading Webutil Version 1.0.2 Beta
proxyHost=null
proxyPort=0
connectMode=HTTP, native.
Forms Applet version is : 9.0.4.0
oracle.forms.net.ConnectionException: Forms session <1> aborted: unable to communicate with runtime process.
at oracle.forms.net.ConnectionException.createConnectionException(Unknown Source)
at oracle.forms.net.HTTPNStream.getResponse(Unknown Source)
at oracle.forms.net.HTTPNStream.doFlush(Unknown Source)
at oracle.forms.net.HTTPNStream.flush(Unknown Source)
at java.io.DataOutputStream.flush(Unknown Source)
at oracle.forms.net.StreamMessageWriter.run(Unknown Source)
Or JInitiator Console:
Oracle JInitiator: Version 1.3.1.17
Using JRE version 1.3.1.17-internal Java HotSpot(TM) Client VM
User home directory = N:
Proxy Configuration: no proxy
JAR cache enabled
Location: N:\Oracle Jar Cache
Maximum size: 50 MB
Compression level: 0
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
q: hide console
s: dump system properties
t: dump thread list
x: clear classloader cache
0-5: set trace level to <n>
Loading http://localhost:8890/forms90/webutil/webutil.jar from JAR cache
Loading http://localhost:8890/forms90/java/f90all_jinit.jar from JAR cache
Loading http://localhost:8890/forms90/webutil/jacob.jar from JAR cache
RegisterWebUtil - Loading Webutil Version 1.0.2 Beta
proxyHost=null
proxyPort=0
connectMode=HTTP, native.
Forms Applet version is : 9.0.4.0
oracle.forms.net.ConnectionException: Forms session <2> aborted: unable to communicate with runtime process.
at oracle.forms.net.ConnectionException.createConnectionException(Unknown Source)
at oracle.forms.net.HTTPNStream.getResponse(Unknown Source)
at oracle.forms.net.HTTPNStream.doFlush(Unknown Source)
at oracle.forms.net.HTTPNStream.flush(Unknown Source)
at java.io.DataOutputStream.flush(Unknown Source)
at oracle.forms.net.StreamMessageWriter.run(Unknown Source)
Named Config sections from formsweb.cfg
#A named (sample) named configuration section for use with WebUtil & Sun JPI
[webutil]
pageTitle=Oracle Forms Services - WebUtil
webUtilArchive=/forms90/webutil/webutil.jar,/forms90/webutil/jacob.jar
WebUtilLogging=off
WebUtilLoggingDetail=normal
WebUtilErrorMode=Alert
baseHTMLjinitiator=html/bocowebutiljpi.htm
baseHTMLjpi=html/bocowebutiljpi.htm
userid=<replacedforsecurity>/<replacedforsecurity>@<replacedforsecurity>
legacy_lifecycle=false
heartBeat=5
envFile=env/webutil.env
#A named (sample) named configuration section for use with WebUtil & JInitiator
[webutiljinit]
pageTitle=Oracle Forms Services - WebUtil JInit
webUtilArchive=/forms90/webutil/webutil.jar,/forms90/webutil/jacob.jar
WebUtilLogging=off
WebUtilLoggingDetail=normal
WebUtilErrorMode=Alert
baseHTMLjinitiator=html/bocowebutiljini.htm
baseHTMLjpi=html/bocowebutiljini.htm
userid=<replacedforsecurity>/<replacedforsecurity>@<replacedforsecurity>
envFile=env/webutil.env
Webutil.env (with comments removed)
ORACLE_HOME=C:\Ora10giDS
FORMS90_PATH=C:\Ora10giDS\forms90\webutil\forms;C:\Ora10giDS\forms90\webutil\demo;C:\Ora10giDS\apps;
WEBUTIL_CONFIG=C:\Ora10giDS\forms90\webutil\webutil.cfg
CLASSPATH=C:\Ora10giDS\j2ee\OC4J_BI_Forms\applications\forms90app\forms90web\WEB-INF\lib\f90srv.jar;C:\Ora10giDS\jlib\repository.jar;C:\Ora10giDS\jlib\ldapjclnt9.jar;C:\Ora10giDS\jlib\debugger.jar;C:\Ora10giDS\jlib\ewt3.jar;C:\Ora10giDS\jlib\share.jar;C:\Ora10giDS\jlib\utj90.jar;C:\Ora10giDS\jlib\zrclient.jar;C:\Ora10giDS\reports\jlib\rwrun.jar;C:\Ora10giDS\jdk\jre\lib\rt.jar;C:\Ora10giDS\forms90\webutil\lib\webutil.jar;C:\Ora10giDS\forms90\webutil\lib\jacob.jar;
PATH=C:\Ora10giDS\bin;C:\Ora10giDS\jdk\jre\bin\client
FORMS90=C:\Ora10giDS\forms90
Section from Webutil.cfg
#install.syslib.location=/webutil
# Try absolute URL per note 252600.1 - no help
#install.syslib.location=http://it110981.boco.co.boulder.co.us:8890/forms90/webutil
# Or try relative URL like this per note 252600.1 - also no help
install.syslib.location=//../webutil
Line from orion-web.xml
<virtual-directory virtual-path="/webutil" real-path="C:\Ora10giDS/forms90/webutil/lib" />
Any suggestions on how I can get this to work will be appreciated. Thanks. -Ianmost of the time this means that your webutil.pll isn't good attached but it is very dependant on the versions you working on.
Post your versions of forms ias and webutil.
In older version it is sometimes necessary to first subclass the webutil group and then attach the webutil.pll. Other way around didn't work (was in beta version 1.02 I believe)
Maybe you are looking for
-
Can I use my old iMac as a second screen for my new one?
I have an old iMac (about 4-5 years) that I don't use anymore and a new iMac that I just bought a few months ago. Can I us my old iMac as a second display for my new one? Its a slow computer now, but the screen is nice and big so it would be nice to
-
I can not use the Acrobat DC Cloud. How do I get an Acrobat PDF Reader that does not use the Cloud?
The subject pretty much says it all. I can not save sensitive corporate files on your Cloud. Even for non-sensitive PDFs, I do not always have access to the cloud when I need to view or work with a PDF. I need a non-cloud version of Acrobat Reader. W
-
Select List item with closest upcoming date
Hello! I am creating a workflow for SharePoint 2010 using SharePoint Designer 2010. I do not have Visual Studio, and then ONLY tool I have is SharePoint Designer 2010. I have a workflow and need to create a custom variable that is the title field of
-
Bring back the YouTube app that is not in ios6
Bring back the YouTube app that is not in ios6
-
Pixel Bender did not install with CS4 on Win7 64. Downloaded toolkit, message "installer failed to initialize" What should I try next? Thank you, and happy Holidays!