Workshop 3.2 and WebLogic Launch Config

WebLogic 9.x Launch Configuration Editor stop working after some time with the error:
<i>!ENTRY org.eclipse.jface 4 2 2006-08-10 15:26:33.946
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.NullPointerException
     at com.bea.wstudio.debugger.WebAppServerLaunchConfigurationTab.setProjectCombo(Unknown Source)
     at com.bea.wstudio.debugger.WebAppServerLaunchConfigurationTab.initializeFrom(Unknown Source)
     at org.eclipse.debug.ui.AbstractLaunchConfigurationTabGroup.initializeFrom(AbstractLaunchConfigurationTabGroup.java:86)
     at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:655)
     at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$6.run(LaunchConfigurationTabGroupViewer.java:548)</i>
Can't create the new launch config and only WS 3.2 reinstallation works but not for long.

Hi Dejan,
You can either use a newsgroup client such as Thuderbird or you can email it to me at [email protected]
cheers
Raj
The next time the issue occurs can you attach the .log file from the .metadata folder.
Also can you attach information on what specific steps which may have caused the crash ?
Thanks
Raj

Similar Messages

How to install Workshop for WebLogic and WebLogic Portal?

Hi All,
I am new to Weblogic Portal. I would like to start learning Oracle Weblogic Portals..
Can anyone please guide me, how to install Workshop for WebLogic and WebLogic Portal?
As per the ""Tutorials – Getting Started with WebLogic Portal"" (http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/tutorials/setup_dev_env.html)
we need to install the Workshop for WebLogic and WebLogic Portal.
Please suggest me where should i get the required environments/IDE?
Thanks,
Harish.

Hi Harish
1. If this is your first time with Weblogic Portal, I would recommend to download the latest Weblogic Portal Software Rel 10.3.2 from this bottom link. Check Accept Radio button, for windows download windows installer. Its about 1 GB file. This software includes Eclipse IDE, Weblogic Server and Weblogic Portal.
http://www.oracle.com/technology/software/products/wlp/index.html
2. During the installation process, make sure at one point you select Custom mode (NOT default Typical mode). In next following screens you will see all bundles checked EXCEPT for Samples. So make sure you check Samples Check box both under Weblogic Server and Weblogic Portal. Then proceed. This will install full Weblogic Workshop (Eclipse IDE), Weblogic Server and Weblogic Portal. This is the good installation package. Also it will install samples for Portal and Server. If you select all default typical mode, it will NOT install samples. You can install samples later on also, but its good at installation time itself you select custom and check Samples also.
3. WLP 10.3.2 uses Eclipse IDE. If you are familiar with Eclipse IDE this should be helpful. Otherwise also, its ok.
4. For learning WLP, in Eclipse IDE, you need to create Portal EAR Project, then Portal Web Project. Inside portal web project create simple jsp hello world portlets and a simple portal.
5. For Deploying and Testing Portal application you need to create Portal Domain using config wizard. You can see this from Start -> Programs -> Oracle Weblogic Portal shortcut -> Weblogic Server -> Tools -> Configuration Wizard.
6. You can start Workshop IDE from Start -> Program Files -> Oracle Weblogic Portal ...-> Eclipse For Weblogic 10.3.2
Here are the links for quick start guide for portal development. Please do refer them.
http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/tutorials/index.html
http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/quickstart/newproject.html
HTH
Ravi Jegga

How to change location for config files in WLS6.0 (like weblogic.home and weblogic.system.home in 5.1)

Hi,
I would like to point weblogic to a directory NOT under c:\bea\... for it's configuration.
I used to do this on WLS 5.1 by setting:
weblogic.home=/weblogic and weblogic.system.home=/projects/wlsconfig
This way my config was NOT coupled to the weblogic install.
I want to do the same thing, and have the config directory located in /projects/domainconfig
for example.
weblogic.system.home etc doesn't seem to do anything. The
only variable that does anything is bea.home, but I need weblogic to find it's
libs etc in /bea, but ONLY the config should be elsewhere.
Any help would be great.
Thanks,
Dion

From SP1 and beyond, you can use
-Dweblogic.RootDirectory=<dirname>
* The property for specifying configuration location:
* The directory name of the domain from which to load the specified
* configuration. The default is ".".
* -Dweblogic.RootDirectory=<dirname>
* The directory must exist.
Dion Almaer wrote:
Hi,
I would like to point weblogic to a directory NOT under c:\bea\... for it's configuration.
I used to do this on WLS 5.1 by setting:
weblogic.home=/weblogic and weblogic.system.home=/projects/wlsconfig
This way my config was NOT coupled to the weblogic install.
I want to do the same thing, and have the config directory located in /projects/domainconfig
for example.
weblogic.system.home etc doesn't seem to do anything. The
only variable that does anything is bea.home, but I need weblogic to find it's
libs etc in /bea, but ONLY the config should be elsewhere.
Any help would be great.
Thanks,
Dion[att1.html]

JDeveloper and Weblogic Server - DOESN't WORK

Hi All,
Yesterday, I was working fine with JDeveloper 11.1.1.6 until I tried to do a deployment (like normally I do) and Weblogic wouldn't start. It was giving me an error, something like 'premature end of file' and security stuff. However, my colleagues told me to rename the folder defaultDomain under C:\Users\Alejandro\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92. So I did. It didn't help.
I restarted the computer, reinstalled JDeveloper in a new middleware nothing. I created a new Windows user and repeated the process. Nothing.
My log when creating the domain is
Log File: C:\Users\Alejandro\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee.adrs\CreateDefaultDomain.log
Label: JDEVADF_11.1.1.6.0_GENERIC_111205.1733.6192.1
Product Home: C:\OracleClean\Middleware\jdeveloper\jdev\
Domain: C:\Users\Alejandro\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain
"C:\OracleClean\Middleware\oracle_common\common\bin\wlst.cmd" "C:\Users\Alejandro\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee.adrs\CreateDefaultDomain.py"
Process started
wlst >
wlst > >CLASSPATH=C:\ORACLE~2\MIDDLE~1\patch_wls1035\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\ORACLE~2\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\ORACLE~2\MIDDLE~1\JDK160~1\lib\tools.jar;>C:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\ORACLE~2\MIDDLE~1\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\lib\web>services.jar;C:\ORACLE~2\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\ORACLE~2\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;C:\ORACLE~2\MIDDLE~1\ORACLE~1/modules/oracle.jrf_11.1.1/jrf->wlstman.jar;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\lib\ADF->SH~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\lib\ADFSCR~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\lib\mdswlst.jar;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\AUDITW~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~>1\common\wlst\RESOUR~1\IGFWLS~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jps-wlst.jar;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jrf->wlst.jar;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAP_~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAUT~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\ossoiap.jar;C:\ORACLE~2\MIDD>LE~1\ORACLE~1\common\wlst\RESOUR~1\OSSOIA~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OVDWLS~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\SSLCON~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\comm>on\wlst\RESOUR~1\wsm-wlst.jar
wlst >
wlst > >PATH=C:\ORACLE~2\MIDDLE~1\patch_wls1035\profiles\default\native;C:\ORACLE~2\MIDDLE~1\patch_jdev1111\profiles\default\native;C:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\bin;C:\ORACLE~2\>MIDDLE~1\modules\ORGAPA~1.1\bin;C:\ORACLE~2\MIDDLE~1\JDK160~1\jre\bin;C:\ORACLE~2\MIDDLE~1\JDK160~1\bin;;C:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
wlst >
wlst > Your environment has been set.
wlst >
wlst > >CLASSPATH=C:\ORACLE~2\MIDDLE~1\patch_wls1035\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\ORACLE~2\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\ORACLE~2\MIDDLE~1\JDK160~1\lib\tools.jar;>C:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\ORACLE~2\MIDDLE~1\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\ORACLE~2\MIDDLE~1\WLSERV~1.3\server\lib\web>services.jar;C:\ORACLE~2\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\ORACLE~2\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;C:\ORACLE~2\MIDDLE~1\ORACLE~1/modules/oracle.jrf_11.1.1/jrf->wlstman.jar;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\lib\ADF->SH~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\lib\ADFSCR~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\lib\mdswlst.jar;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\AUDITW~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~>1\common\wlst\RESOUR~1\IGFWLS~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jps-wlst.jar;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jrf->wlst.jar;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAP_~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAUT~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\ossoiap.jar;C:\ORACLE~2\MIDD>LE~1\ORACLE~1\common\wlst\RESOUR~1\OSSOIA~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OVDWLS~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\SSLCON~1.JAR;C:\ORACLE~2\MIDDLE~1\ORACLE~1\comm>on\wlst\RESOUR~1\wsm-wlst.jar;C:\ORACLE~2\MIDDLE~1\utils\config\10.3\config->launch.jar;C:\ORACLE~2\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbynet.jar;C:\ORACLE~2\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\ORACLE~2\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbytools.jar;;
wlst >
wlst > Initializing WebLogic Scripting Tool (WLST) ...
wlst > I am currently moving to a next computer to see because I cant keep spending time by solving this. Any help? Or should I just reinstall windows? I cant use linux because I need to work under VPN connection and I didn't managed to set it up.

Really don't know much about your problem but whenever i have weired problem like these..... (it has happened twice in last one year) I just renamed that sytem 11.1.1.6.38.61.92 folder
next time i start Jdev, it creates this folder and everything started working fine.... the main problem here is that.... you have to setup your connections, version control and other weblogic specific items again...... from my experience, that has been worked out well.....
-R

Problems with Cocoon 2.03 and Weblogic 6.1 SP3

I am having problems with Cocoon 2.03 and Weblogic 6.1 SP3, when I try to deploy
the cocoon.war.
Cocoon works fine when I unpack the cocoon.war into ...\mydomain\applications
(after I changed cocoon.xconf to use the following transformer factory: org.apache.xalan.processor.TransformerFactoryImpl).
However, when I deploy the cocoon.war through the weblogic console and try to
invoke cocoon (http://localhost:7001/cocoon/) I get the following error:
ERROR (2002-09-26) 11:28.40:859 [sitemap] (/cocoon/) ExecuteThread: '7' for
queue: 'default'/Handler: Error compiling sitemap
java.util.zip.ZipException: The system cannot find the file specified
     at java.util.zip.ZipFile.open(Native Method)
     at java.util.zip.ZipFile.<init>(ZipFile.java:110)
     at java.util.zip.ZipFile.<init>(ZipFile.java:125)
     at weblogic.utils.zip.ZipURLConnection.getInputStream(Handler.java:49)
     at org.apache.cocoon.components.source.URLSource.getInputStream(URLSource.java:151)
     at org.apache.cocoon.components.source.URLSource.getInputSource(URLSource.java:223)
     at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.generateResource(ProgramGeneratorImpl.java:318)
     at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.createResource(ProgramGeneratorImpl.java:282)
     at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.load(ProgramGeneratorImpl.java:196)
     at org.apache.cocoon.sitemap.Handler.run(Handler.java:228)
     at java.lang.Thread.run(Thread.java:484)
I understood that there were problems when the cocoon.war file that did occur
when you unpacked the war, but I believed that these problems did not occur with
WLS6.1 SP3.
Has anyone else encountered this problem and solved it? Any help would be greatly
appreciated.
Thanks in advance.
Paul

This how I got Cocoon 2.04 up and running on WLS 6.1.4
Download the Cocoon source from http://xml.apache.org/cocoon/dist/
Remove all but the following JARs from lib/optional:
commons-jxpath-1.0.jar
jing-20020724.jar
resolver-20020130.jar
servlet_2_2.jar
commons-logging-1.0.jar
jtidy-04aug2000r7-dev.jar
rhino-1.5r3.jar
xt-19991105.jar
Update lib/jars.xml to reflect these changes
Issue build commands:
./build.sh clean (Note: Always clean first!)
./build.sh -Dinclude.webapp.libs=yes -Dexclude.webapp.samples=yes -Dexclude.webapp.documenation=yes
-Dexclude.webapp.javadocs=yes webapp
Copy the following JARs to your WLS instance’s lib directory:
xercesImpl-2.0.0.jar
xml-apis.jar
xalan-2.3.1.jar
xt-19991105.jar
java/lib/tools.jar
Sample of config/SERVER_NAME.setenv
LIB=/path/to/lib
JARS=$LIB/xercesImpl-2.0.0.jar:$LIB/xml-apis.jar:$LIB/xalan-2.3.1.jar:$LIB/xt-19991105.jar:/opt/java1.3/lib/tools.jar
JAVACLASSPATH=$JARS:.:$JAVACLASSPATH
JAVA_HOME=/opt/java1.3
Deploy the resluting cocoon.war and you should have a Cocoon up and running that
can do the XML->HTML Hello World sample. The status page works fine too.
My advice is to launch this stripped configuration first and if needed add more
features later by adding the JARs of your choice to the class path (or add the
to your webapp-build if you are confident that WLS are capable of handling their
manifests).
Good luck
/Peter
"Paul Petley" <[email protected]> wrote:
>
>
I am having problems with Cocoon 2.03 and Weblogic 6.1 SP3, when I try
to deploy
the cocoon.war.
Cocoon works fine when I unpack the cocoon.war into ...\mydomain\applications
(after I changed cocoon.xconf to use the following transformer factory:
org.apache.xalan.processor.TransformerFactoryImpl).
However, when I deploy the cocoon.war through the weblogic console and
try to
invoke cocoon (http://localhost:7001/cocoon/) I get the following error:
ERROR (2002-09-26) 11:28.40:859 [sitemap] (/cocoon/) ExecuteThread:
'7' for
queue: 'default'/Handler: Error compiling sitemap
java.util.zip.ZipException: The system cannot find the file specified
     at java.util.zip.ZipFile.open(Native Method)
     at java.util.zip.ZipFile.<init>(ZipFile.java:110)
     at java.util.zip.ZipFile.<init>(ZipFile.java:125)
     at weblogic.utils.zip.ZipURLConnection.getInputStream(Handler.java:49)
     at org.apache.cocoon.components.source.URLSource.getInputStream(URLSource.java:151)
     at org.apache.cocoon.components.source.URLSource.getInputSource(URLSource.java:223)
     at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.generateResource(ProgramGeneratorImpl.java:318)
     at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.createResource(ProgramGeneratorImpl.java:282)
     at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.load(ProgramGeneratorImpl.java:196)
     at org.apache.cocoon.sitemap.Handler.run(Handler.java:228)
     at java.lang.Thread.run(Thread.java:484)
I understood that there were problems when the cocoon.war file that did
occur
when you unpacked the war, but I believed that these problems did not
occur with
WLS6.1 SP3.
Has anyone else encountered this problem and solved it? Any help would
be greatly
appreciated.
Thanks in advance.
Paul

IIS proxy 5.1 and Weblogic 6.1 does not support sticky session

Dear Sir,
Our system is migrating from Weblogic 5.1 to Weblogic 6.1. After testing on
development environment, it is found that IIS proxy for 5.1 plug-in and Weblogic
6.1 server is perfect match for our case. Since our appliction system hit some
bugs of IIS proxy for 6.1. In development environment, one IIS match with one
Weblogic.
During production launch, another problem found. It seems that IIS proxy 5.1
plug-in with Weblogic 6.1 does not support the sticky load balancing. A sticky
service is one where a client sends its requests to the same instance and those
requests are not redirected to other instances. In production, two IIS match with
two Weblogic. Below is
#WebLogicHost=10.0.3.12
#WebLogicPort=8012
WebLogicCluster=10.0.3.12:8012,10.0.3.13:8012
COnnectionTimeoutSecs=10
ConnectionRetrySecs=2
ErrorPage=https://www.xxxx.com/eBank/sysnotready.htm
CookieName=eBankingWebLogicSession
Anyone have idea on out case?
Thanks,
KAI

My test was with 6.1 SP3.
The way to tell is by analyzing the cookie(JSESSIONID).
Perhaps the behaviour changed post SP1. I can't say for sure.
Eric
"Gary Rudolph" <[email protected]> wrote in message
news:[email protected]...
Is that entirely true concerning you don't need the persistence set to
replicated in the weblogic.xml to gain sticky load balancing?
The reason I ask was that in our situation sticky wouldn't work without
having the persistence set to replicated. This was with NSAPI and WLS 6.1
SP1. The weblogic servers were configured in a weblogic cluster. So..based
on this statement we should not have needed to set the persistence, but in
practice we did for it to work.
Gary
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
I just checked, and you are correct. You just need to have clustering
enabled in 6.1. You do not necessarily need to have persistence set to
replicated.
Of course, you won't get failover, but you will get the sticky load
balancing.
Regards,
Eric
"Ricky Wong" <[email protected]> wrote in message
news:[email protected]...
Why do we need to set session persistence to replicate in order to
perform
sticky load balancing ? There is no such requirement in WebLogic 5.1.
As
far
as I know, the IIS plugin simply interprets the value of the sessioncookie,
which should be embedded with the application server address, then
forward
the request to that particular application server.
We didn't use session replication in our environment because not allsession
variables are serializable.
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
The problem you mentionned in the other newsgroup post has been
fixed
and
will be in SP4. If you are in production or nearing production and
need
a
resolution now, then please open a case with support.
You should not need any other parameters to do the load balancing.
But
to
have the sticky load balancing, you must make sure you have session
persistence set to replicated for the webapp in question.
I'm not sure I am understanding your 3rd question.
In any case, my advice is to either wait for SP4 to bereleased(scheduled
sometime this month) or if you really need to go into production
soon,
contact support to obtain the latest IIS plugin.
Regards,
Eric
"Mike" <[email protected]> wrote in message
news:[email protected]...
Dear Eric,
Thanks very much for you kindly information, but we still have thefollowing issues
regarding the WL IIS proxy:
1. We have already tried the IIS proxy that comes with WL6.1 SP3.However, the
result from that version of IIS proxy is not satisfactory, as weexperienced cases
where the web page is not displayed correctly (as in
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.develo
per.interest.plug-in&item=994&utag=).
If there is any IIS proxy released after WL6.1 SP3, Could you
kindly
give
us
a pointer to the plugin?
2. In WL5.1 case, we are only required to have "WebLogicCluster"
parameter
set
to two weblogic servers in order use the load balancing features.
In
WL6.1, we
do not come across any additional settings required to support
load
balancing.
Is there any such settings required (e.g. in
config.xml,weblogic.xml,
application.xml,
etc?)
3. Does WL IIS proxy problem has anything to do with the version
of
the
IIS server/windows
versions that are using? we have already tried with IIS4 and IIS5
and
have
different
kinds of issues.
Thanks in advance for your kind assistance.
Mike
"Eric Gross" <[email protected]> wrote:
Yes, the session format has changed when using clustering and you
cannot
use
the 5.1 plugin to proxy to 6.1.
What problems did you have using the 6.1 plugin? Maybe you need
the
latest
6.1 plugin.
Regards,
Eric
"KAI" <[email protected]> wrote in message
news:[email protected]...
Dear Sir,
Our system is migrating from Weblogic 5.1 to Weblogic 6.1.
After
testing on
development environment, it is found that IIS proxy for 5.1
plug-in
and
Weblogic
6.1 server is perfect match for our case. Since our appliction
system
hit
some
bugs of IIS proxy for 6.1. In development environment, one IIS
match
with
one
Weblogic.
During production launch, another problem found. It seems
that
IIS
proxy 5.1
plug-in with Weblogic 6.1 does not support the sticky load
balancing.
A
sticky
service is one where a client sends its requests to the same
instance
and
those
requests are not redirected to other instances. In production,
two
IIS
match with
two Weblogic. Below is
#WebLogicHost=10.0.3.12
#WebLogicPort=8012
WebLogicCluster=10.0.3.12:8012,10.0.3.13:8012
COnnectionTimeoutSecs=10
ConnectionRetrySecs=2
ErrorPage=https://www.xxxx.com/eBank/sysnotready.htm
CookieName=eBankingWebLogicSession
Anyone have idea on out case?
Thanks,
KAI

Issue in bringing up CRS on ATG 10.1.1 with MySQL and Weblogic 10.3

Hello,
I am trying to bring up Commerce Reference Store as part of my evaluation using MySQL (bundled with ATG) and WebLogic 10.3.
I followed the ATG Documentation on CRS with WebLogic and MySQL and I could not proceed because of the below error log. I keep getting error in OnlineCreateServerInstanceTask of CIM. I believe it should be some configuration problem, but could not think of any.
As part of the installation, I use C:\jdk1.6.0_25. I verified my weblogic server is up through the admin console. I started MySQL before running the eval batch. Apart from starting MySQL server, I did not make any datasource/database configuration changes for ATG. I have not run any other scripts to configure MySQL too.
Please guide me to resolve the problem.
C:\ATG\ATG10.1.1\CommerceReferenceStore\Store\eval>configureEval.bat
Do you wish to run the CRS evaluation installation? [Y/N]: y
Do you wish to use an existing database for the CRS evaluation? [Y/N]: n
The CRS evaluation install will attempt to create the database. Press [Return] t
o continue or any other key to quit:
Enter mysql database connection details
Enter user name: admin
Enter user password: admin
Enter database name: crsprod
Enter 'root' user password:
Creating database...
Finished database creation
Enter weblogic admin server URL: http://localhost:7001
Enter weblogic admin server username: weblogic
Enter weblogic admin server password: weblogic123
Buildfile: C:\ATG\ATG10.1.1\CommerceReferenceStore\Store\eval\evalbuild.xml
all:
[copy] Copying 1 file to C:\ATG\ATG10.1.1\CommerceReferenceStore\Store\eval
[delete] Deleting: C:\ATG\ATG10.1.1\CommerceReferenceStore\Store\eval\cimOut.
cim.tmp
BUILD SUCCESSFUL
Total time: 0 seconds
Application Server: weblogic
The following installed ATG components are being used to launch:
ATGPlatform version 10.1.1 installed at C:\ATG\ATG10.1.1
Created "C:\ATG\ATG10.1.1\home\CIM\startDynamo.jar" in 15,273ms.
Nucleus running
atg.cim.productconfig.productselector.ProductSelectionContextTask starting...
(Searching for products... done.)
atg.cim.productconfig.productselector.ProductSelectionContextTask finished.
atg.cim.productconfig.appserver.AppServerSelectTask starting...
atg.cim.productconfig.appserver.AppServerSelectTask finished.
atg.cim.productconfig.appserver.AppServerPathTask starting...
atg.cim.productconfig.appserver.AppServerPathTask finished.
atg.cim.productconfig.appserver.DomainPathTask starting...
atg.cim.productconfig.appserver.DomainPathTask finished.
atg.cim.productconfig.appserver.UrlTask starting...
atg.cim.productconfig.appserver.UrlTask finished.
atg.cim.productconfig.appserver.UsernameTask starting...
atg.cim.productconfig.appserver.UsernameTask finished.
atg.cim.productconfig.appserver.PasswordTask starting...
atg.cim.productconfig.appserver.PasswordTask finished.
atg.cim.productconfig.appserver.AppServerSelectionPersistenceTask starting...
atg.cim.productconfig.appserver.AppServerSelectionPersistenceTask finished.
atg.cim.database.CreateSchemaTask starting...
atg.cim.database.CreateSchemaTask finished.
atg.cim.database.ImportDataTask starting...
Combining template tasks...Success
Importing (1 of 1) /CIM/tmp/import/nonswitchingCore-import1.xml:
/CommerceReferenceStore/Store/Storefront/data/pricelists.xml to /atg/commerce/pr
icing/priceLists/PriceLists
/CommerceReferenceStore/Store/Storefront/data/stores.xml to /atg/store/stores/St
oreRepository
/CommerceReferenceStore/Store/Storefront/data/catalog-i18n.xml to /atg/commerce/
catalog/ProductCatalog
/CommerceReferenceStore/Store/Storefront/data/pricelists-i18n.xml to /atg/commer
ce/pricing/priceLists/PriceLists
/CommerceReferenceStore/Store/Storefront/data/sites.xml to /atg/multisite/SiteRe
pository
/CommerceReferenceStore/Store/Storefront/data/sites-i18n.xml to /atg/multisite/S
iteRepository
/CommerceReferenceStore/Store/Storefront/data/promos-i18n.xml to /atg/commerce/c
atalog/ProductCatalog
/CommerceReferenceStore/Store/Storefront/data/seotags-i18n.xml to /atg/seo/SEORe
pository
/CommerceReferenceStore/Store/Storefront/data/wishlists.xml to /atg/commerce/gif
ts/Giftlists
/CommerceReferenceStore/Store/Storefront/data/inventory.xml to /atg/commerce/inv
entory/InventoryRepository
/CommerceReferenceStore/Store/Storefront/data/users.xml to /atg/userprofiling/Pr
ofileAdapterRepository
/CommerceReferenceStore/Store/Storefront/data/orders.xml to /atg/commerce/order/
OrderRepository
/CommerceReferenceStore/Store/Storefront/data/orders-i18n.xml to /atg/commerce/o
rder/OrderRepository
/CommerceReferenceStore/Store/Storefront/data/storetext-i18n.xml to /atg/store/s
tores/StoreRepository
/CommerceReferenceStore/Store/Storefront/data/claimable-i18n.xml to /atg/commerc
e/claimable/ClaimableRepository
... > Success
All Imports Completed Successfully
atg.cim.database.ImportDataTask finished.
atg.cim.worker.common.PropertyFileClearPersistanceTask starting...
atg.cim.worker.common.PropertyFileClearPersistanceTask finished.
atg.cim.productconfig.serverinstance.ServerInstanceNameTask starting...
atg.cim.productconfig.serverinstance.ServerInstanceNameTask finished.
atg.cim.productconfig.serverinstance.PortBindingsSelectTask starting...
atg.cim.productconfig.serverinstance.PortBindingsSelectTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.worker.common.MapPropertyFileCreatorTask starting...
atg.cim.worker.common.MapPropertyFileCreatorTask finished.
atg.cim.productconfig.serverinstance.MakeServerInstanceFromPatternTask starting.
atg.cim.productconfig.serverinstance.MakeServerInstanceFromPatternTask finished.
atg.cim.productconfig.appassembly.EarFileNameTask starting...
atg.cim.productconfig.appassembly.EarFileNameTask finished.
atg.cim.productconfig.deploy.weblogic.OnlineCreateServerInstanceTask starting...
Error Executing Batch File
atg.cim.worker.TaskException: Error deploying to weblogic
atg.cim.worker.TaskException: Error exececuting batch file
at atg.cim.flow.CimFlowCreator.startHeadlessCimFlow(CimFlowCreator.java:
130)
at atg.cim.Launcher.startCimFlow(Launcher.java:278)
at atg.cim.Launcher.main(Launcher.java:99)
Caused by: atg.cim.worker.TaskException: Error deploying to weblogic
at atg.cim.worker.Task.handleException(Task.java:72)
at atg.cim.productconfig.deploy.weblogic.OnlineCreateServerInstanceTask.
execute(OnlineCreateServerInstanceTask.java:159)
at atg.cim.headless.HeadlessExecutorImpl.executeTasks(HeadlessExecutorIm
pl.java:150)
at atg.cim.headless.HeadlessExecutorImpl.populateAndExecuteHeadlessTasks
(HeadlessExecutorImpl.java:140)
at atg.cim.batch.BatchChooserExecutor.populateAndExecuteHeadlessTasks(Ba
tchChooserExecutor.java:169)
at atg.cim.flow.CimFlow.headlessFlow(CimFlow.java:116)
at atg.cim.flow.CimFlowCreator.startHeadlessCimFlow(CimFlowCreator.java:
120)
... 2 more
Caused by: C:\ATG\ATG10.1.1\CIM\plugins\Base\ant\cim-ant.xml:348: The following
error occurred while executing this line:
C:\ATG\ATG10.1.1\CIM\plugins\Base\ant\cim-ant.xml:254: The following error occur
red while executing this line:
C:\ATG\ATG10.1.1\CIM\plugins\Base\ant\cim-ant.xml:214: exec returned: 1
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(Projec
tHelper.java:541)
at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.jav
a:394)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at atg.cim.task.ant.utility.AntExecutionWrapper.executeAntTarget(AntExec
utionWrapper.java:167)
at atg.cim.worker.AntTask.executeAntTarget(AntTask.java:115)
at atg.cim.productconfig.deploy.weblogic.OnlineCreateServerInstanceTask.
execute(OnlineCreateServerInstanceTask.java:155)
... 7 more
Caused by: C:\ATG\ATG10.1.1\CIM\plugins\Base\ant\cim-ant.xml:254: The following
error occurred while executing this line:
C:\ATG\ATG10.1.1\CIM\plugins\Base\ant\cim-ant.xml:214: exec returned: 1
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(Projec
tHelper.java:541)
at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.jav
a:394)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.jav
a:391)
... 20 more
Caused by: C:\ATG\ATG10.1.1\CIM\plugins\Base\ant\cim-ant.xml:214: exec returned:
1
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:636)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:662)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:487)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.jav
a:391)
... 34 more
Nucleus shutting down
Nucleus shutdown complete
Thanks.

This error is resolved after following the logs in C:\ATG\ATG10.1.1\CIM\log\cim.log. The root cause is I used http as protocol instead of t3 while specifying weblogic admin url.
http://localhost:7001 instead of t3://localhost:7001
Thanks.

Workshop 8.1 and I/O operations

Hi everybody.
Does anyone have a glue about why i/o operations are slowly inside a running Workshop instance than "outside" it ?
I've an I/O intensive process that runs in 2-3 seconds when using a main method of a simple Java Class. When i try to run the same process (at same machine) inside a Java Control Class, they become about 4 times more slow.
I've run some tests and even when it is just reading and writing some big data from and to ByteArrayStreams, these operations perform slower inside than outside my Workshop Server instance (and i really don't know why).
I'm running out of ideas. Can the antivirus software be affecting read/write operations when Weblogic runs ?
I would appreciate any help of any kind.
Thanks in advance.

Hi Daniel
When you say inside I assume that you are running the app within IDE connected to a server. Can you please confirm?
If so please turn off the logging in the setDomainEnv.cmd/.sh (verboseLoggingFlag, debugFlag, logErrorsToConsoleFlag)
Also please set all the priority to 'error' in the workshopLogCfg.xml under WL_HOME/common/lib folder.
Let me know if the performance improves.
Thanks
Vimala

Unable to create a JMS Message bridge between Weblogic 12c and Weblogic 8.1

Hi,
I am unable to successfully create a Message Bridge between Weblogic 12.1.1.0 and Weblogic 8.1. The error message being received is:
eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException generated by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3://localhost:8001, user name = System) ">
The error on the monitoring tab is WARN: failed to connect to target.
Both domains are deployed on one box for testing purposes. The bridge itself is deployed on Weblogic 12c. The areas of config that may be of interest are:
<server>
<name>AdminServer</name>
<listen-address></listen-address>
</server>
<messaging-bridge>
<name>Bridge</name>
<target>AdminServer</target>
<source-destination>JMSBridgeSource12c</source-destination>
<target-destination>JMSBridgeTarget81</target-destination>
<selector>Test</selector>
<quality-of-service>Exactly-once</quality-of-service>
<qos-degradation-allowed>false</qos-degradation-allowed>
<durability-enabled>true</durability-enabled>
<idle-time-maximum>60</idle-time-maximum>
<async-enabled>true</async-enabled>
<started>true</started>
<preserve-msg-property>false</preserve-msg-property>
</messaging-bridge>
<app-deployment>
<name>jms-xa-adp</name>
<target>AdminServer</target>
<module-type>rar</module-type>
<source-path>D:\ORACLE~3\WLSERV~1.1\server\lib\jms-xa-adp.rar</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<jms-bridge-destination>
<name>JMSBridgeSource12c</name>
<adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDIXA</adapter-jndi-name>
<user-name>System</user-name>
<user-password-encrypted>{AES}nfFzhs+0J/O2Cenf0g4zDsDyvIKENMF7cZ5sAVUehX0=</user-password-encrypted>
<classpath></classpath>
<connection-factory-jndi-name>JMSConnectionFactory12c</connection-factory-jndi-name>
<connection-url>t3://localhost:7001</connection-url>
<destination-jndi-name>JMSQueue12c</destination-jndi-name>
</jms-bridge-destination>
<jms-bridge-destination>
<name>JMSBridgeTarget81</name>
<adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDIXA</adapter-jndi-name>
<user-name>System</user-name>
<user-password-encrypted>{AES}eBkO46cHvtrzEraOMIOdXow6WvEAtA4NCUDTQ4mC+9w=</user-password-encrypted>
<classpath></classpath>
<connection-factory-jndi-name>JMSConnectionFactory81</connection-factory-jndi-name>
<connection-url>t3://localhost:8001</connection-url>
<destination-jndi-name>JMSQueue81</destination-jndi-name>
</jms-bridge-destination>
I have enforced global trust between the two domains. I have disabled the guest user on the 8.1 domain but can’t see where to do this on 12c.
Any suggestions would be much appreciated.
Regards
John
Edited by: 958336 on 13-Sep-2012 03:11

Thanks for the recommendation. Unfortunately it did not help solve the problem.
I have managed to get a JMS bridge working between 12c and 8.1 by including the 8.1 weblogic.jar on the classpath. This setup was using eis.jms.WLSConnectionFactoryJNDINoTX.
After trying to use the adapter that supports transactions, WLSConnectionFactoryJNDIXA I received the following error:
java.lang.IllegalStateException: can only be called from server
Is this because the Weblogic 12c server now views the 8.1 server as being foreign?

Workshop (9.2 and 3.x) and Mylar

Hello,
I am currently using Workshop 9.2 in a major portal Project (both based on 9.2 and 8.1.5 Servers)
Input into Eclipse Foundation's WTP project (with people like Tim Wagner or IBM's Arthur Ryman) over the last 12 months, resulted in some good progress now visible in Workshop 9.2 (and 3.2 based on Callisto)
Beside Subversion Plugins (which I was pleased to see widely supported by default) I am now using Eclips Mylar a lot and find it very useful.
It is fully compatible with Workshop 9.2 (should be with 3.2, too) and enables true task-based development under WebLogic Workshop (Eclipse)
I am also writing an article on Mylar for the German Eclipse Magazin based on those real hands-on success stories in WLW 9.2.
If there is interest here in the community, I'd be happy to provide information in English, too. Either via Newsgroups, or in an article (together with examples) or a blog.
Kind Regards,
Werner Keil

Hello Werner,
Please post the document to this newsgroup. You could also consdider submitting it to the BEA dev2dev site at http://dev2dev.bea.com/
cheers
Raj

Workshop 9.2 and Mylar

Hello,
I am currently using Workshop 9.2 in a major portal Project (both based on 9.2 and 8.1.5 Servers)
Input into Eclipse Foundation's WTP project (with people like Tim Wagner or IBM's Arthur Ryman) over the last 12 months, resulted in some good progress now visible in Workshop 9.2 (and 3.2 based on Callisto)
Beside Subversion Plugins (which I was pleased to see widely supported by default) I am now using Eclips Mylar a lot and find it very useful.
It is fully compatible with Workshop 9.2 (should be with 3.2, too) and enables true task-based development under WebLogic Workshop (Eclipse)
I am also writing an article on Mylar for the German Eclipse Magazin based on those real hands-on success stories in WLW 9.2.
If there is interest here in the community, I'd be happy to provide information in English, too. Either via Newsgroups, or in an article (together with examples) or a blog.
Kind Regards,
Werner Keil

Hi Werner
Thanks a lot for the information. Yes we would be interested in the article.
Can you please share the article once it's available?
Thanks again,
Vimala

Workshop 10.1 and EJB 3.0

I am using Weblogic Workshop 10.1 and I am trying to create an EJB 3.0 stateless session bean. Is there support for this?

Hi,
There is no direct tooling support for Java EE5 yet with Workshop10.1, so you cannot create EJB3.0 ejb's with tools.
With that being said, one of the workshop engineer came up with a workaround to support EJB3 ejb's, so you can manually write them up and deploy to WLS server. I have pasted his steps below.
Thanks,
Vimala-
===Response Start
Regarding using EE5 constructs in Workshop, much of this can be done today despite not having the facet versions, though it does require a couple of workarounds that I'll mention here.
Create EJB module and add to EAR
1. Create (Basic WTP) EJB Module. The main reason for creating an EJB module is to get application.xml updated with the correct module type.
     1. Disable the Weblogic EJB Extensions facet (See note above).
     2. De-select the "create client jar" option.
     3. Finish. The project will now be tagged with an error because the ejb-jar.xml (v2.1) doesn't include any EJB definitions.
2. Replace ejb-jar.xml with the EJB3 descriptor (WTP produces errors when the 2.1 is not present, and the 2.1 descriptors doesn't validate when empty).
3. Create EJB Beans and Interfaces
Create Web App and add to EAR
1. Create dynamic web project
2.Replace web.xml root element to update version to EE 5
3. Update J2EE Module Dependencies. If the web project is created after the EJB project. You have to add the module dependency.
4. Add Servlet
1. WTP has a handy way to add the web.xml entry for an existing Servlet or create it from scratch (via template). If you copy the Servlet into the project, you can still to file->new->Servlet and pick the class. The dialog will prompt for any non-default changes to web.xml.
2. Annotate Servlet To Reference the first EJB
It's true that EJB3 doesn't require descriptors, but the version of WTP in the product today requires a descriptor to be there. As long as it's the 3.0 version,
you can leave it empty and proceed to do all your development with annotations, WTP will be happy.
=== Response End

Workshop 9.2 - ear - weblogic 8.1 problem

I've written my application in workshop 9.2 and successfully deployed it as EAR file to other domain in the same server. But I'm running into troubles when trying to deploy it to the 8.1 weblogic server. I'm getting the following error:
weblogic.management.DeploymentException: Error while loading descriptors: Error processing file 'META-INF/application.xml'. weblogic.xml.process.XMLProcessingException: XML document does not appear to contain a properly formed DOCTYPE header - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header] - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header]
I'm quite new to this all and any tips will be helpful :)
Risto

Hello Risto,
Unfortunately, deploying a 9.2 application to a 8.1.x server is unsupported.
Hope this helps.
-Raj

Can weblogic workshop be installed without weblogic server

I was trying a custom installation to install weblogic workshop 8.1 without weblogic server. But, when I only choose weblogic workshop, it still picks the weblogic server to install.
I want to understand can we just have weblogic workshop installed on various machines, so that we can build on various machines and finally deploy them all to a single server??
Any help for me to understand this will be much appreciated.
Note: I've installed a evaluation version of the software, not sure if that makes any difference..

Has anyone else solved this problem? We too are experiencing the same problem.
We are trying to build a .JWS file from within an ANT build script. The build script compiles the site into a single EAR file that should contain a deployable and usable JWS component, however it obviously does not.
If anyone has a solution, please let us know. We're facing a code freeze on this project by this Friday and really need some help.

The problem about Secure Reliable Messaging between WCF and Weblogic

I'm doing a project for testing the interoperability between WCF and Weblogic with secure reliable messaging.
When WCF client talk to Weblogic service with Secure Reliable feature enabled.We got error when CreateSequence, the error message is below:
The incoming message was signed with a token which was different from what used to encrypt the body. This was not expected.
The remote endpoint requested an address for acknowledgements that is not the same as the address for application messages. The channel could not be opened because this is not supported. Ensure the endpoint address used to create the channel is identical to the one the remote endpoint was set up with.
My understanding is that the client accepted the RSTR from weblogic (so both sides now share the secure conversation token) and moved on to CreateSequence (and failed due to config mismatches). But I don't how the error happen and how to get it fixed.
-- below is the wsdl you are using --
Any ideas about it?
Thanks in advance!!!!!!
<?xml version='1.0' encoding='utf-8'?>
<WL5G3N4:definitions name="EchoStringSignOnly" targetNamespace="http://tempuri.org/" xmlns="" xmlns:WL5G3N0="http://www.w3.org/ns/ws-policy" xmlns:WL5G3N1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:WL5G3N2="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" xmlns:WL5G3N3="http://docs.oasis-open.org/ws-rx/wsrmp/200702" xmlns:WL5G3N4="http://schemas.xmlsoap.org/wsdl/" xmlns:WL5G3N5="http://tempuri.org/" xmlns:WL5G3N6="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:WL5G3N7="http://schemas.xmlsoap.org/wsdl/soap12/">
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly1_EchoString_Input_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<sp:SignedParts xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<sp:Body/>
<sp:Header Name="Sequence" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="SequenceAcknowledgement" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="AckRequested" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly1_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<WL5G3N2:RMAssertion>
<WL5G3N2:InactivityTimeout Milliseconds="600000"/>
<WL5G3N2:AcknowledgementInterval Milliseconds="200"/>
</WL5G3N2:RMAssertion>
<sp:SymmetricBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:ProtectionToken>
<wsp15:Policy>
<sp:SecureConversationToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp15:Policy>
<sp:RequireDerivedKeys/>
<sp:BootstrapPolicy>
<wsp15:Policy>
<sp:SignedParts>
<sp:Body/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
<sp:EncryptedParts>
<sp:Body/>
</sp:EncryptedParts>
<sp:AsymmetricBinding>
<wsp15:Policy>
<sp:InitiatorToken>
<wsp15:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp15:Policy>

<sp:WssX509V3Token10/>
</wsp15:Policy>
</sp:X509Token>
</wsp15:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp15:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/Never">
<wsp15:Policy>

<sp:WssX509V3Token10/>
</wsp15:Policy>
</sp:X509Token>
</wsp15:Policy>
</sp:RecipientToken>
<sp:AlgorithmSuite>
<wsp15:Policy>
<sp:Basic128Rsa15/>
</wsp15:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp15:Policy>
<sp:Strict/>
</wsp15:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp15:Policy>
</sp:AsymmetricBinding>
<sp:Wss11>
<wsp15:Policy>
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefThumbprint/>
<sp:MustSupportRefEncryptedKey/>
</wsp15:Policy>
</sp:Wss11>
<sp:Trust13>
<wsp15:Policy>
<sp:MustSupportIssuedTokens/>
<sp:RequireClientEntropy/>
<sp:RequireServerEntropy/>
</wsp15:Policy>
</sp:Trust13>
</wsp15:Policy>
</sp:BootstrapPolicy>
</wsp15:Policy>
</sp:SecureConversationToken>
</wsp15:Policy>
</sp:ProtectionToken>
<sp:AlgorithmSuite>
<wsp15:Policy>
<sp:Basic128Rsa15/>
</wsp15:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp15:Policy>
<sp:Strict/>
</wsp15:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp15:Policy>
</sp:SymmetricBinding>
<sp:Wss11 xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefThumbprint/>
<sp:MustSupportRefEncryptedKey/>
</wsp15:Policy>
</sp:Wss11>
<sp:Trust13 xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:MustSupportIssuedTokens/>
<sp:RequireClientEntropy/>
<sp:RequireServerEntropy/>
</wsp15:Policy>
</sp:Trust13>
<wsam:Addressing xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
<wsp:Policy xmlns:wsp="http://www.w3.org/ns/ws-policy">
<wsam:NonAnonymousResponses/>
</wsp:Policy>
</wsam:Addressing>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly_EchoString_output_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<sp:SignedParts xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<sp:Body/>
<sp:Header Name="Sequence" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="SequenceAcknowledgement" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="AckRequested" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="UsesSequenceSTR" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="ChannelInstance" Namespace="http://schemas.microsoft.com/ws/2005/02/duplex"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly1_EchoString_output_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<sp:SignedParts xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<sp:Body/>
<sp:Header Name="Sequence" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="SequenceAcknowledgement" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="AckRequested" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly_EchoString_Input_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<sp:SignedParts xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<sp:Body/>
<sp:Header Name="Sequence" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="SequenceAcknowledgement" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="AckRequested" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="UsesSequenceSTR" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="ChannelInstance" Namespace="http://schemas.microsoft.com/ws/2005/02/duplex"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<WL5G3N3:RMAssertion/>
<sp:SymmetricBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:ProtectionToken>
<wsp15:Policy>
<sp:SecureConversationToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp15:Policy>
<sp:RequireDerivedKeys/>
<sp:BootstrapPolicy>
<wsp15:Policy>
<sp:SignedParts>
<sp:Body/>
<sp:Header Name="ChannelInstance" Namespace="http://schemas.microsoft.com/ws/2005/02/duplex"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
<sp:EncryptedParts>
<sp:Body/>
</sp:EncryptedParts>
<sp:AsymmetricBinding>
<wsp15:Policy>
<sp:InitiatorToken>
<wsp15:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp15:Policy>

<sp:WssX509V3Token10/>
</wsp15:Policy>
</sp:X509Token>
</wsp15:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp15:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/Never">
<wsp15:Policy>

<sp:WssX509V3Token10/>
</wsp15:Policy>
</sp:X509Token>
</wsp15:Policy>
</sp:RecipientToken>
<sp:AlgorithmSuite>
<wsp15:Policy>
<sp:Basic128Rsa15/>
</wsp15:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp15:Policy>
<sp:Strict/>
</wsp15:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp15:Policy>
</sp:AsymmetricBinding>
<sp:Wss11>
<wsp15:Policy>
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefThumbprint/>
<sp:MustSupportRefEncryptedKey/>
</wsp15:Policy>
</sp:Wss11>
<sp:Trust13>
<wsp15:Policy>
<sp:MustSupportIssuedTokens/>
<sp:RequireClientEntropy/>
<sp:RequireServerEntropy/>
</wsp15:Policy>
</sp:Trust13>
</wsp15:Policy>
</sp:BootstrapPolicy>
</wsp15:Policy>
</sp:SecureConversationToken>
</wsp15:Policy>
</sp:ProtectionToken>
<sp:AlgorithmSuite>
<wsp15:Policy>
<sp:Basic128Rsa15/>
</wsp15:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp15:Policy>
<sp:Strict/>
</wsp15:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp15:Policy>
</sp:SymmetricBinding>
<sp:Wss11 xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefThumbprint/>
<sp:MustSupportRefEncryptedKey/>
</wsp15:Policy>
</sp:Wss11>
<sp:Trust13 xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:MustSupportIssuedTokens/>
<sp:RequireClientEntropy/>
<sp:RequireServerEntropy/>
</wsp15:Policy>
</sp:Trust13>
<cdp:CompositeDuplex xmlns:cdp="http://schemas.microsoft.com/net/2006/06/duplex"/>
<ow:OneWay xmlns:ow="http://schemas.microsoft.com/ws/2005/05/routing/policy"/>
<wsam:Addressing xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
<wsp:Policy xmlns:wsp="http://www.w3.org/ns/ws-policy">
<wsam:NonAnonymousResponses/>
</wsp:Policy>
</wsam:Addressing>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N4:types>
<xsd:schema targetNamespace="http://tempuri.org/Imports" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://tempuri.org/" schemaLocation="RequestReplySignOnly.svc.xsd0.xml"/>
<xsd:import namespace="http://schemas.microsoft.com/2003/10/Serialization/" schemaLocation="RequestReplySignOnly.svc.xsd1.xml"/>
</xsd:schema>
</WL5G3N4:types>
<WL5G3N4:message name="PingRequest">
<WL5G3N4:part element="WL5G3N5:PingRequest" name="parameters"/>
</WL5G3N4:message>
<WL5G3N4:message name="PingResponse">
<WL5G3N4:part element="WL5G3N5:PingResponse" name="parameters"/>
</WL5G3N4:message>
<WL5G3N4:portType name="IEchoStringSignOnly">
<WL5G3N4:operation name="EchoString">
<WL5G3N4:input message="WL5G3N5:PingRequest" name="PingRequest"/>
<WL5G3N4:output message="WL5G3N5:PingResponse" name="PingResponse"/>
</WL5G3N4:operation>
</WL5G3N4:portType>
<WL5G3N4:binding name="CustomBinding_IEchoStringSignOnly" type="WL5G3N5:IEchoStringSignOnly">
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly_policy"/>
</WL5G3N0:Policy>
<WL5G3N6:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<WL5G3N4:operation name="EchoString">
<WL5G3N6:operation soapAction="urn:wsrm:EchoString" style="document"/>
<WL5G3N4:input name="PingRequest">
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly_EchoString_Input_policy"/>
</WL5G3N0:Policy>
<WL5G3N6:body use="literal"/>
</WL5G3N4:input>
<WL5G3N4:output name="PingResponse">
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly_EchoString_output_policy"/>
</WL5G3N0:Policy>
<WL5G3N6:body use="literal"/>
</WL5G3N4:output>
</WL5G3N4:operation>
</WL5G3N4:binding>
<WL5G3N4:binding name="CustomBinding_IEchoStringSignOnly1" type="WL5G3N5:IEchoStringSignOnly">
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly1_policy"/>
</WL5G3N0:Policy>
<WL5G3N7:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<WL5G3N4:operation name="EchoString">
<WL5G3N7:operation soapAction="urn:wsrm:EchoString" style="document"/>
<WL5G3N4:input name="PingRequest">
<WL5G3N7:body use="literal"/>
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly1_EchoString_Input_policy"/>
</WL5G3N0:Policy>
</WL5G3N4:input>
<WL5G3N4:output name="PingResponse">
<WL5G3N7:body use="literal"/>
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly1_EchoString_output_policy"/>
</WL5G3N0:Policy>
</WL5G3N4:output>
</WL5G3N4:operation>
</WL5G3N4:binding>
<WL5G3N4:service name="EchoStringSignOnly">
<WL5G3N4:port binding="WL5G3N5:CustomBinding_IEchoStringSignOnly" name="CustomBinding_IEchoStringSignOnly">
<WL5G3N6:address location="http://mss-rrsp-01/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReplySignOnly.svc/SecureReliable_Addressable_Soap11_WSAddressing10_RM11"/>
<wsa10:EndpointReference xmlns:wsa10="http://www.w3.org/2005/08/addressing">
<wsa10:Address>http://mss-rrsp-01/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReplySignOnly.svc/SecureReliable_Addressable_Soap11_WSAddressing10_RM11</wsa10:Address>
<Identity xmlns="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity">
<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
<X509Data>
<X509Certificate>MIIDCjCCAfKgAwIBAgIQYDju2/6sm77InYfTq65x+DANBgkqhkiG9w0BAQUFADAwMQ4wDAYDVQQKDAVPQVNJUzEeMBwGA1UEAwwVT0FTSVMgSW50ZXJvcCBUZXN0IENBMB4XDTA1MDMxOTAwMDAwMFoXDTE4MDMxOTIzNTk1OVowQDEOMAwGA1UECgwFT0FTSVMxIDAeBgNVBAsMF09BU0lTIEludGVyb3AgVGVzdCBDZXJ0MQwwCgYDVQQDDANCb2IwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMCquMva4lFDrv3fXQnKK8CkSU7HvVZ0USyJtlL/yhmHH/FQXHyYY+fTcSyWYItWJYiTZ99PAbD+6EKBGbdfuJNUJCGaTWc5ZDUISqM/SGtacYe/PD/4+g3swNPzTUQAIBLRY1pkr2cm3s5Ch/f+mYVNBR41HnBeIxybw25kkoM7AgMBAAGjgZMwgZAwCQYDVR0TBAIwADAzBgNVHR8ELDAqMCiiJoYkaHR0cDovL2ludGVyb3AuYmJ0ZXN0Lm5ldC9jcmwvY2EuY3JsMA4GA1UdDwEB/wQEAwIEsDAdBgNVHQ4EFgQUXeg55vRyK3ZhAEhEf+YT0z986L0wHwYDVR0jBBgwFoAUwJ0o/MHrNaEd1qqqoBwaTcJJDw8wDQYJKoZIhvcNAQEFBQADggEBAIiVGv2lGLhRvmMAHSlY7rKLVkv+zEUtSyg08FBT8z/RepUbtUQShcIqwWsemDU8JVtsucQLc+g6GCQXgkCkMiC8qhcLAt3BXzFmLxuCEAQeeFe8IATr4wACmEQE37TEqAuWEIanPYIplbxYgwP0OBWBSjcRpKRAxjEzuwObYjbll6vKdFHYIweWhhWPrefquFp7TefTkF4D3rcctTfWJ76I5NrEVld+7PBnnJNpdDEuGsoaiJrwTW3Ixm40RXvG3fYS4hIAPeTCUk3RkYfUkqlaaLQnUrF2hZSgiBNLPe8gGkYORccRIlZCGQDEpcWl1Uf9OHw6fC+3hkqolFd5CVI=</X509Certificate>
</X509Data>
</KeyInfo>
</Identity>
</wsa10:EndpointReference>
</WL5G3N4:port>
<WL5G3N4:port binding="WL5G3N5:CustomBinding_IEchoStringSignOnly1" name="CustomBinding_IEchoStringSignOnly1">
<WL5G3N7:address location="http://mss-rrsp-01/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReplySignOnly.svc/SecureReliable_Anonymous_Soap12_WSAddressing10_RM10"/>
<wsa10:EndpointReference xmlns:wsa10="http://www.w3.org/2005/08/addressing">
<wsa10:Address>http://mss-rrsp-01/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReplySignOnly.svc/SecureReliable_Anonymous_Soap12_WSAddressing10_RM10</wsa10:Address>
<Identity xmlns="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity">
<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
<X509Data>
<X509Certificate>MIIDCjCCAfKgAwIBAgIQYDju2/6sm77InYfTq65x+DANBgkqhkiG9w0BAQUFADAwMQ4wDAYDVQQKDAVPQVNJUzEeMBwGA1UEAwwVT0FTSVMgSW50ZXJvcCBUZXN0IENBMB4XDTA1MDMxOTAwMDAwMFoXDTE4MDMxOTIzNTk1OVowQDEOMAwGA1UECgwFT0FTSVMxIDAeBgNVBAsMF09BU0lTIEludGVyb3AgVGVzdCBDZXJ0MQwwCgYDVQQDDANCb2IwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMCquMva4lFDrv3fXQnKK8CkSU7HvVZ0USyJtlL/yhmHH/FQXHyYY+fTcSyWYItWJYiTZ99PAbD+6EKBGbdfuJNUJCGaTWc5ZDUISqM/SGtacYe/PD/4+g3swNPzTUQAIBLRY1pkr2cm3s5Ch/f+mYVNBR41HnBeIxybw25kkoM7AgMBAAGjgZMwgZAwCQYDVR0TBAIwADAzBgNVHR8ELDAqMCiiJoYkaHR0cDovL2ludGVyb3AuYmJ0ZXN0Lm5ldC9jcmwvY2EuY3JsMA4GA1UdDwEB/wQEAwIEsDAdBgNVHQ4EFgQUXeg55vRyK3ZhAEhEf+YT0z986L0wHwYDVR0jBBgwFoAUwJ0o/MHrNaEd1qqqoBwaTcJJDw8wDQYJKoZIhvcNAQEFBQADggEBAIiVGv2lGLhRvmMAHSlY7rKLVkv+zEUtSyg08FBT8z/RepUbtUQShcIqwWsemDU8JVtsucQLc+g6GCQXgkCkMiC8qhcLAt3BXzFmLxuCEAQeeFe8IATr4wACmEQE37TEqAuWEIanPYIplbxYgwP0OBWBSjcRpKRAxjEzuwObYjbll6vKdFHYIweWhhWPrefquFp7TefTkF4D3rcctTfWJ76I5NrEVld+7PBnnJNpdDEuGsoaiJrwTW3Ixm40RXvG3fYS4hIAPeTCUk3RkYfUkqlaaLQnUrF2hZSgiBNLPe8gGkYORccRIlZCGQDEpcWl1Uf9OHw6fC+3hkqolFd5CVI=</X509Certificate>
</X509Data>
</KeyInfo>
</Identity>
</wsa10:EndpointReference>
</WL5G3N4:port>
</WL5G3N4:service>
</WL5G3N4:definitions>

Bruce Stephens <[email protected]> wrote:
Hi Michael,
The short answer, at this time, OOTB, WS-RM interop with an unknown
vendor would be doubtful. For a longer answer, David Orchard has a good
review of the emerging web services specs [0]. You might consider ebXML
messaging [1] as a more mature solution.
Thank you Bruce. I will look at these docs.
Mike S.
Hope this helps,
Bruce
[0]
http://dev2dev.bea.com/technologies/webservices/articles/ws_orchard.jsp
[1]
http://e-docs.bea.com/wli/docs70/ebxml/getstart.htm
Michael Shea wrote:
Hello,
We have developed an application that is running on the WebLogic AppServer v8.1
sp1.
Recently we have received a request/query on providing reliable SOAPmessaging
from our application to 3rd party.
I have read the documentation on Reliable messaging support and havenoted that
it is only supported between two WebLogic Application servers.
My questions are, since we do not have control of the 3rd party's application,
and it may not be based on a WebLogic App Server:
1. Will this work?
2. Does anyone have any idea of the type of issues that may be experienced?
3. How close is the implementation to the WS Reliable Messaging specification?
So, if the other party was based on an IBM or Microsoft implementationis this
likely to work?
It goes without saying that any work done would need to be very throughlytested
and qualified.
I have looked through the WebLogic Documentation on WebServices aswell as searching
this newgroup for other posts on this topic, hopefully I have not missedanything
(If so, my apologies.)
Thanks,
Mike Shea.

Workshop 3.2 and WebLogic Launch Config

Similar Messages

Maybe you are looking for