Throws a weblogic.i18n.tools.GenException

In WebLogic 6.0, I'm trying to use weblogic.i18ntools.l10ngen to
generate localized properties file for simple text. and when i
have a japanese AdderLabels.xml file, it fails during parse. the
japanese AdderLabels.xml just has english text in it. and it was
created using weblogic.i18ntools.gui.MessageLocalizer
Here's the error:
weblogic.i18n.tools.GenException: Code gen exception: Parse failed
for: \weblogic\msgcat\ja\AdderLabels.xml
at weblogic.i18ntools.l10ngen.parseIt(l10ngen.java:358)
at weblogic.i18ntools.l10ngen.buildLangOutputs(l10ngen.java:302)
at weblogic.i18ntools.l10ngen.generate(l10ngen.java:408)
at weblogic.i18ntools.l10ngen.run(l10ngen.java:422)
at weblogic.i18ntools.l10ngen.main(l10ngen.java:459)
Any ideas? Please email me at [email protected]
Thanks.

Similar Messages

Anyone tried the new Weblogic Scripting Tool (WLST)?

Has anyone tried using the new WebLogic Scripting Tool (WLST) that was recently
posted on the dev2dev WebLogic Utilities site: http://dev2dev.bea.com/resourcelibrary/utilitiestools/adminmgmt.jsp
It looks to be a handy tool that is built upon jython and enables you to easily
navigate, inspect and manipulate the WebLogic MBean tree on a running server.
It also has a nice scripting tool which allows you to convert a config.xml file
into a script that can be run to recreate a domain or specific resources within
the domain. This is exactly something I have been looking for because we occasionally
recreate domains or subsets of a domain for testing and POC purposes.
The utility is fairly well documented and works well for the most part. The only
issue I have run into so far is that is does not seem to understand JMS Distributed
Destinations. When I try to convert a config.xml that contains a DD to a script
it throws a null pointer exception. I have not tried a cluster yet.
I noticed the utility was authored by someone at BEA. Is there potential that
BEA will support this in the future if it catches on? Has anyone had experience
with WLST or jython that would cause you to reccomend (or not) using it?
Thanks.

Darryl,
Thanks for the valuable feedback. My comments are inline.
Darryl Stoflet wrote:
As a fairly long time wlshell user who recently started testing wlst there are
few features I have found lacking in wlst.
1. For monitoring purposes I am frequently using the -g and -r options to wlshell's
get command for graphing and repeating respectivelyI haven't looked at -g and -r options in wlshell, but will do so.
Although there is no graphical monitoring of attributes in wlst, but
there is certainly some monitoring capability (which will be enhanced
further in the coming version). Please take a look at the
monitorAttribute() function.
wls:/(offline)> help('monitorAttribute')
Description:
Monitors the specified attribute every by polling every interval.
Syntax:
monitorAttribute(attributeName, interval, monitorFile)
attributeName = Name of the attribue that you would like to monitor.
interval = Time (in seconds) to wait before the next fetch
monitorFile=[optional] File path where the monitored data will be
written to.
Example:
wls:/mydomain/runtime/ServerRuntimes/myserver/ExecuteQueueRuntimes/weblogic.kernel.Default>
monitorAttribute("ServicedRequestTotalCount",10)
Press Return to quit monitoring
Monitoring started for attribute ServicedRequestTotalCount
wls:/(offline)>
>
2. wlshell 2.0 adds the option when connecting to the admin server to also connect
to all managed servers in that domain. This is a nice feature for monitoring because
you then have access to all the runtime mbeans in each managed serverYes, this indeed seems to be a very nice feature. We will consider this
for our next release.
>
3. There is not a good way to pass cmd line options(variables) to wlst. In wlshell
I can send cmd line options via -v. I have tried something similar with wlst using
-loadProperties but this is a little laborious because I do not necessarily want
to create a properties file when a passing in only one or two variables. Also
I find loadProperties lacking somewhat (see 4 below)ok, I just realised that there is indeed a bug in wlst where the command
line arguments are not being honored. In Jython one can access the
command line arguments from the sys.argv variable. For example,
java weblogic.WLST -i foo.py var1 var2 var3
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to Weblogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> print sys.argv
['foo.py', 'var1', 'var2', 'var3']
wls:/offline>
But this isn't working properly, please keep using the loadProperties
untill this has been fixed.
>
4) loadProperties treats all created variables as strings. While this is understandable
from the perspective that getProperty returns a string, it would be nice if wlst
was smart enough that when a property is numbers only its an int, otherwise a
string etc.
wlshell does this logic/conversion for you which really simplifies calling methods
that expect the particular datatype. To get around this problem you can create a script file say,
variables.py which would look like,
# variables that will be used
theInterpreter.set('var1',10)
theInterpreter.set('var2','i am a string')
java weblogic.WLST variables.py
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to Weblogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/(offline)> print var1
10
wls:/(offline)> print var2
'i am a string'
>
5. I'd like to be able to send cmd output etc to a file while running within wlst.
In wlshell its a simple as adding >> filename to the end of the command. In wlst it is not as simple as doing >>, it is more than that. You can
choose any output stream to direct your output to. In your case you can
create a FileOutputStream and route the output to this stream for any
particular command.
Example,
# create a file output stream say fos
from java.io import FileOutputStream
fos = FileOutputStream("output.txt")
# save the default output stream to a variable to
# switch it back
sys.stdout=fos
# Now all output for any function will go to output.txt
ls()
cd('foo')
# after done with your functions switch it back
sys.stdout=origOutput
This is the right Jython way to do it. This works for all output streams
, very useful when you embed an interpreter in a servlet and would like
to display the output via a PrintStream etc.
>
>
All in all wlst is a nice tool. Personally if the above features were added it
would be much easier to transistion to wlst for good.
Also I really like the wlst offline tool. Its nice to be able to do the whole
create and configure domain process with one tool. Will this be supported. Yes indeed. We are working on merging both the tools into one.
I do
not want to rely on it too much if it will not work in future weblogic versions.It will be supported in future release of weblogic.
Thanks,
-satya
>
Thanks,
Darryl
"Steve Hess" <[email protected]> wrote:
Hello,
I am the BEA Product Manager behind WLST.
WLST, as it appears today on dev2dev, is an early release version of
a tool that
BEA does intend to support as part of our next major release. We decided
to issue
early versions of the tool because of the demand for a supported scripting
solution,
and to generate feedback from our user community. I encourage you to
work with
WLST, and assure you that this tool represents our current direction
in management
scripting.
Also note, this newsgroup can be used to issue questions, concerns and
feedback
about WLST. The engineering and PM team will monitor this group and
respond to
your questions as quickly as we can. While we will not be able to respond
to
every feature request, we really value your suggestions, and will endeavor
to
improve the tool in ways that meet your real-world needs.
Cheers,
Steve Hess
Director, WLS PM
"George Lupanoff" <[email protected]> wrote:
Has anyone tried using the new WebLogic Scripting Tool (WLST) that was
recently
posted on the dev2dev WebLogic Utilities site: http://dev2dev.bea.com/resourcelibrary/utilitiestools/adminmgmt.jsp
It looks to be a handy tool that is built upon jython and enables you
to easily
navigate, inspect and manipulate the WebLogic MBean tree on a running
server.
It also has a nice scripting tool which allows you to convert a config.xml
file
into a script that can be run to recreate a domain or specific resources
within
the domain. This is exactly something I have been looking for because
we occasionally
recreate domains or subsets of a domain for testing and POC purposes.
The utility is fairly well documented and works well for the most part.
The only
issue I have run into so far is that is does not seem to understandJMS
Distributed
Destinations. When I try to convert a config.xml that contains a DDto
a script
it throws a null pointer exception. I have not tried a cluster yet.
I noticed the utility was authored by someone at BEA. Is there potential
that
BEA will support this in the future if it catches on? Has anyone had
experience
with WLST or jython that would cause you to reccomend (or not) using
it?
Thanks.

Unable to start MS NoClassDefFoundError: weblogic/sip/tools/SipToolsFactory

Hi Folks,
I really need ur assistance on this, I am failing to start my weblogic managed server which is on WL 10.3.4 and hosted on Windows 2008R2 server.
I am getting the below exception:
<<WLS Kernel>> <> <> <1365769487402> <BEA-000386> <Server subsystem failed. Reason: java.lang.NoClassDefFoundError: weblogic/sip/tools/SipToolsFactory
java.lang.NoClassDefFoundError: weblogic/sip/tools/SipToolsFactory
     at weblogic.sip.plugin.SipPlugin.startService(SipPlugin.java:25)
     at weblogic.server.ServiceActivator.start(ServiceActivator.java:96)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused By: java.lang.ClassNotFoundException: weblogic.sip.tools.SipToolsFactory
     at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
     at weblogic.sip.plugin.SipPlugin.startService(SipPlugin.java:25)
     at weblogic.server.ServiceActivator.start(ServiceActivator.java:96)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Now the I dont want to use the SIP and have done the following:
1. Disabled the SIP from my Weblogic Console and restarted the Admin Server
2. Modified my init script from
<setenv name="WLSS_HOME">
<value>E:\Oracle\Middleware\wlserver_10.3/sip</value>
</setenv>
     <setenv name="SIP_ENABLED">
          <value>true</value>
     </setenv>
to
<setenv name="WLSS_HOME">
<value>E:\Oracle\Middleware\wlserver_10.3/sip</value>
     </setenv>
          <setenv name="SIP_ENABLED">
          <value>false</value>
               </setenv>
3. Modified my class paths so SIP wont be called.
Now the interesting part, actually this setup is a running setup and I have installed it from scratch..The thing here is it might sound silly....But the weblogic still picks up the Classpath for SIP during startup, be it via node manger or even on the server.
<WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
E:\Oracle\Middleware\user_projects\domains\DOMAIN_XYZ\lib\sipactivator.jar>
<BEA-002647> <The service plugin, com.oracle.core.sip.activator, was added from E:\Oracle\Middleware\user_projects\domains\DOMAIN_XYZ\lib\sipactivator.jar.>
If you see its a extension lib file, now my query without deleting the file from the extension lib how can i get rid of it.
Hope someone can help me out.
Thanks

Hi Kishore,
Thanks for the update, but I had already done those changes, please find my current config.xml but I noticed one thing when I restart my weblogic instance it creates a new config.xml with a name like this config.xml and it doesnt reflect the original config.xml which I am trying to use. I some how feel that the config.xml is being picked up while stating the instance instead of the original config.xml.
I am placing both of them below with the respective names.
config.xml (the one i am trying to use)
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>TEST</name>
<domain-version>10.3.4.0</domain-version>
<security-configuration>
<name>TEST</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{AES}xxxxx</credential-encrypted>
<node-manager-username>wlxxxx</node-manager-username>
<node-manager-password-encrypted>{AES}xxxxx</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<machine>localhost</machine>
<listen-address></listen-address>
</server>
<server>
<name>Test01</name>
<machine>localhost</machine>
<listen-port>9001</listen-port>
<listen-address></listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
</server-start>
</server>
<server>
<name>Test02</name>
<machine>Machine2</machine>
<listen-port>9001</listen-port>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test03</name>
<machine>localhost</machine>
<listen-port>9002</listen-port>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test04</name>
<machine>Machine2</machine>
<listen-port>9002</listen-port>
<listen-address></listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<class-path>E:\Oracle\Middleware\user_projects\domains\TEST\properties\Test</class-path>
<arguments>-Xms128m -Xmx512m -XX:MaxPermSize=256m</arguments>
</server-start>
</server>
<server>
<name>Test_ES01</name>
<machine>localhost</machine>
<listen-port>9003</listen-port>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_ES02</name>
<machine>Machine2</machine>
<listen-port>9003</listen-port>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_ES03</name>
<machine>localhost</machine>
<listen-port>9004</listen-port>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_ES04</name>
<machine>Machine2</machine>
<listen-port>9004</listen-port>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_HK01</name>
<machine>localhost</machine>
<listen-port>9005</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_HK02</name>
<machine>Machine2</machine>
<listen-port>9005</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_HK03</name>
<machine>localhost</machine>
<listen-port>9006</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test_HK04</name>
<machine>Machine2</machine>
<listen-port>9006</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<server-start></server-start>
</server>
<server>
<name>Test05</name>
<machine>localhost</machine>
<listen-port>9007</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
</server>
<server>
<name>Test07</name>
<machine>localhost</machine>
<listen-port>9008</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
</server>
<server>
<name>Test06</name>
<machine>Machine2</machine>
<listen-port>9007</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<class-path>E:\Oracle\Middleware\user_projects\domains\TEST\properties\Test</class-path>
<arguments>-Xms128m -Xmx512m -XX:MaxPermSize=256m</arguments>
</server-start>
</server>
<server>
<name>Test08</name>
<machine>Machine2</machine>
<listen-port>9008</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<class-path>E:\Oracle\Middleware\user_projects\domains\TEST\properties\Test</class-path>
<arguments>-Xms128m -Xmx512m -XX:MaxPermSize=256m</arguments>
</server-start>
</server>
<server>
<name>Test_IN01</name>
<jms-thread-pool-size>0</jms-thread-pool-size>
<machine>localhost</machine>
<listen-port>9003</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<server-debug>
<debug-scope>
<name>default</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.application</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.classloader</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.cluster</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.connector</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.core</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.debug</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.default</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.deploy</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.descriptor</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.diagnostics</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.ejb</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.iiop</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.jdbc</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.jms</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.jpa</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.management</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.messaging</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.messagingbridge</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.protocol</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.sca</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.security</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.servlet</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.store</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.t3</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.transaction</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.work</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.workarea</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic.wtc</name>
<enabled>false</enabled>
</debug-scope>
</server-debug>
<listen-address></listen-address>
<xml-registry xsi:nil="true"></xml-registry>
<xml-entity-cache xsi:nil="true"></xml-entity-cache>
<default-file-store>
<synchronous-write-policy>Direct-Write</synchronous-write-policy>
</default-file-store>
</server>
<server>
<name>Test_IN02</name>
<jms-thread-pool-size>0</jms-thread-pool-size>
<machine>Machine2</machine>
<listen-port>9003</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<server-debug>
<debug-scope>
<name>default</name>
<enabled>false</enabled>
</debug-scope>
<debug-scope>
<name>weblogic</name>
<enabled>false</enabled>
</debug-scope>
<debug-libraries>true</debug-libraries>
<class-finder>true</class-finder>
<classpath-servlet>true</classpath-servlet>
<class-loader>true</class-loader>
<debug-server-life-cycle>true</debug-server-life-cycle>
</server-debug>
<listen-address></listen-address>
<xml-registry xsi:nil="true"></xml-registry>
<xml-entity-cache xsi:nil="true"></xml-entity-cache>
<default-file-store>
<synchronous-write-policy>Cache-Flush</synchronous-write-policy>
</default-file-store>
</server>
<server>
<name>Test_IN03</name>
<jms-thread-pool-size>0</jms-thread-pool-size>
<machine>localhost</machine>
<listen-port>9004</listen-port>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address></listen-address>
<xml-registry xsi:nil="true"></xml-registry>
<xml-entity-cache xsi:nil="true"></xml-entity-cache>
<default-file-store>
<synchronous-write-policy>Cache-Flush</synchronous-write-policy>
</default-file-store>
</server>
<server>
<name>Test_IN04</name>
<ssl>
<enabled>false</enabled>
</ssl>
<machine>Machine2</machine>
<listen-port>9004</listen-port>
<listen-port-enabled>true</listen-port-enabled>
<cluster xsi:nil="true"></cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<java-compiler>javac</java-compiler>
<client-cert-proxy-enabled>false</client-cert-proxy-enabled>
<server-diagnostic-config>
<wldf-diagnostic-volume>Low</wldf-diagnostic-volume>
</server-diagnostic-config>
</server>
<embedded-ldap>
<name>TEST</name>
<credential-encrypted>{AES}xxxxx</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.4.0</configuration-version>
<app-deployment>
<name>Test_hkapp01</name>
<target>Test_HK01</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Test_hkapp01</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Test_hkrp01</name>
<target>Test_HK03</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Test_hkrp01</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Testapp05</name>
<target>Test05</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Testapp05\test.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>testrp07</name>
<target>Test07/target>
<module-type>war</module-type>
<source-path>applications\TestApp\Testrp07\Testrp.war</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Testrp08</name>
<target>Test08</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Testrp08\Testrp.war</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>stage</staging-mode>
</app-deployment>
<app-deployment>
<name>Testapp06</name>
<target>Test06</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Testapp06\Test.war</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>stage</staging-mode>
</app-deployment>
<app-deployment>
<name>Test_hkrp04</name>
<target>Test_HK04</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Test_hkrp04</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>stage</staging-mode>
</app-deployment>
<app-deployment>
<name>Test_hkapp02</name>
<target>Test_HK02</target>
<module-type>war</module-type>
<source-path>applications\TestApp\Test_hkapp02</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>stage</staging-mode>
</app-deployment>
<machine>
<name>localhost</name>
<node-manager>
<name>localhost</name>
<nm-type>SSL</nm-type>
<listen-address>xxx-xxx-xxx-xxx</listen-address>
<listen-port>5556</listen-port>
<debug-enabled>false</debug-enabled>
</node-manager>
</machine>
<machine>
<name>Machine2</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>xxx-xxx-xxx-xxx</listen-address>
<listen-port>5556</listen-port>
<debug-enabled>false</debug-enabled>
</node-manager>
</machine>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>Test01app_DS</name>
<target>Test01</target>
<descriptor-file-name>jdbc/Test01app_DS-4659-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>Test03rp_DS</name>
<target>Test03</target>
<descriptor-file-name>jdbc/Test03rp_DS-3850-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>Test02app_DS</name>
<target>Test02</target>
<descriptor-file-name>jdbc/Test02app_DS-7531-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>Test04rp_DS</name>
<target>Test04</target>
<descriptor-file-name>jdbc/Test04rp_DS-5676-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
</domain>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Eclipse:package weblogic.webservice.tools.wsdlp does not exist

Hi, everyone! I got an error While I was Compiling the Entire MedRec Project application on Eclipse3.1 with ant. However, when I used setEnv.cmd and ant command(), it's all Ok! The error message shows as below:
banner:
[echo] #### S T A R T C O M M O N W E B A P P ####
[mkdir] Created dir: C:\medrec_tutorial\build\tmp
build:
[javac] Compiling 23 source files to C:\medrec_tutorial\build\tmp
[javac] C:\medrec_tutorial\src\common\web\com\bea\medrec\utils\MedRecWebAppUtils.java:319: package weblogic.webservice.tools.wsdlp does not exist
[javac] if (th instanceof weblogic.webservice.tools.wsdlp.WSDLParseException) {
[javac] ^
[javac] 1 error
BUILD FAILED
file:C:/medrec_tutorial/src/common/web/build.xml:29: Compile failed; see the compiler error output for details.

Bruce Stephens <[email protected]> wrote:
Hello,
This looks like a bug that has already been reported and resolved. If
you could provide your test case to our super support group [1], and
reference CR127344, they should be able to sort out this issue.
Thanks,Hi ,
I also got the same error.If u find the solution please email me
isuru [email protected]
Thanx
Bruce
[1]
http://support.bea.com
[email protected]
Franck wrote:
Hello,
when I try to build my webservice with a stateless bean and a complexdata type (byte[]), by using ANT and SERVICEGEN.
I have the following exception (with WL 8.1, but it works witout problemwith WL 7.0.4).
*** ERROR:
-package weblogic.xml.schema.binding does not exist
[servicegen] extends weblogic.xml.schema.binding.BeanCodecBase
What has changed between the both version.
can somebody help me
Tank you
Regards

How to use weblogic.DDconverter Tool to upgrade Deployment Descriptors.

Hi,
I want to know how to use weblogic.DDconverter Tool to upgrade Deployment Descriptors using EAR of previous verisons(JDK and weblogic).
Regards,
Neeraj

Looks like the protocol is not correct (Unable to connect to 'http://localhost:7001': Destination unreachable)
Could you try the t3 protocol, for example,
java weblogic.Deployer -adminurl t3://localhost:7001 -username weblogic -password welcome1 -listapps

Taskdef class weblogic.wsee.tools.anttasks.JwscTask cannot be found

Hi,
I use ant to deploy adf web applications. However, I get errors:
--------------error----------------
Buildfile: E:\SOAworkspace\ANT\Project1\build2.xml
[echo] Classpath: D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server\bin\weblogic.jar
BUILD FAILED
E:\SOAworkspace\ANT\Project1\build2.xml:14: taskdef class weblogic.wsee.tools.anttasks.JwscTask cannot be found
Total time: 0 seconds
--------------ant------------------
<project default="all">
<property name="weblogic.jar.classpath" value="D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server\bin\weblogic.jar"/>
<echo>Classpath: ${weblogic.jar.classpath}</echo>
<target name="all" depends="clean,build-service,deploy" />
<target name="clean">
<delete dir="output" />
</target>
<path id="my.path">
<pathelement path="D:\weblogicSA2011\jdk160_18\lib\tools.jar"/>
<pathelement path="D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server\bin\weblogic.jar"/>
</path>
<taskdef name="jwsc"
classname="weblogic.wsee.tools.anttasks.JwscTask" classpath="D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server\bin\weblogic.jar" />
<target name="build-service">
<jwsc srcdir="HelloWorld" destdir="c:\helloWorldEar">
<jws file="ping.java" type="JAXWS"/>
</jwsc>
</target>
<taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy" classpath="D:\weblogicSA2011\wlserver_10.3\server\lib\weblogic.jar"/>
<target name="deploy">
<wldeploy action="deploy"
name="otnapp_application1.ear"
source="E:\SOAworkspace\otnapp\deploy\" user="weblogic"
password="welcome1"
adminurl="t3://localhost:7001"
targets="wl_server"/>
</target>
</project>

Those taskdefs are in the %WL_HOME%/server/lib/weblogic.jar file. Are you sure that you have that file in a <path> element of the Ant build.xml script (or in the CLASSPATH environment variable that Ant is using)?

BEA Weblogic i18n

Hi,
Can anyone point me to some general documentation on BEA Weblogic
i18n?
Thanks

http://e-docs.bea.com/wls/docs60/i18n/index.html
Cornee vd Linden <[email protected]> wrote in message
news:3aa8fed1$[email protected]..
>
Hi,
Can anyone point me to some general documentation on BEA Weblogic
i18n?
Thanks

Using MBeans and weblogic.admin tools..

The main use I see for using weblogic.admin tools and programmatic access to mbeans
is to script or automate tasks that you can otherwise accomplish in the Admin
Console

The main use I see for using weblogic.admin tools and programmatic access to mbeans
is to script or automate tasks that you can otherwise accomplish in the Admin
Console

WebLogic Server Tools 1.1.2 Released

The WebLogic Server Tools team has announced the release of a new service release that fixes a number of important bugs. The recommendation is all current users migrate to this release by using the Eclipse update manager. Additional information about this release can be found in the release notes.
Main Page
[url https://dev2devclub.bea.com/updates/wls-tools/]https://dev2devclub.bea.com/updates/wls-tools/
Release Notes
[url https://dev2devclub.bea.com/updates/wls-tools/release-notes/v1.1.2.html]https://dev2devclub.bea.com/updates/wls-tools/release-notes/v1.1.2.html
The Eclipse 3.4 "Ganymede" version of WebLogic Server Tools has also been updated. Version 2.0.1 is now available and has been tested with Ganymede M4 milestone build.
Release Notes
[url https://dev2devclub.bea.com/updates/wls-tools/release-notes/v2.0.1.html]https://dev2devclub.bea.com/updates/wls-tools/release-notes/v2.0.1.html
Cheers
Raj Alagunmal

Luca Rossi wrote:
Does 2.0.1 version supports remote deployments (bug 197 on bugzilla.bea.com ?)No, it does not. Remote deployment support is currently being worked on
and will likely be made available sometime in April.
- Konstantin

WebLogic Server Tools 1.1.3 Released

A service release for WebLogic Server Tools is now available. The focus
of this release was to fix several remaining issues affecting current
users and to certify WLS Tools on Eclipse Europa SP2 that was released
at the end of February. We recommend that all current users migrate to
this release by using the Eclipse update manager. More information
about this release can be found in the release notes.
Main Page
https://dev2devclub.bea.com/updates/wls-tools/
Release Notes
https://dev2devclub.bea.com/updates/wls-tools/release-notes/v1.1.3.html
The Eclipse 3.4 "Ganymede" version of WebLogic Server Tools has also
been updated. Version 2.0.2 is now available and has been tested with
Ganymede M5 milestone build. Of course, since Ganymede platform is still
under development we don't recommend this version for most users, but
early adopters with tolerance for pre-release stability can get a sneak
peak of what's coming in the next Eclipse release.
Release Notes
https://dev2devclub.bea.com/updates/wls-tools/release-notes/v2.0.2.html
Konstantin Komissarchik
Team Lead for WebLogic Server Tools

WebLogic Server Tools is built on Eclipse Web Tools Platform which has a
particular project structure that has to be followed. Basically, you
create an EAR project. This contains your app-level descriptors,
APP-INF/lib and any binary modules. Then, for every module in an EAR,
you create a separate project. For web module, use the Dynamic Web
Project. For EJB modules, there is an EJB project. The projects are
wired up using the "J2EE Module Dependencies" project properties page.
Use this page on the EAR project to specify which module projects should
be included in the EAR. Once you've done that, you can use this page in
the module projects to specify inter-module dependencies.
Basically, you have to take your app and convert it into the form that
Eclipse can understand. The easiest way to do that is to create the
projects based on the module structure of your app and then copy content
from your application into those projects. Once you are done, you will
be able to use WebLogic Server Tools to deploy to WLS. The split
directory magic will happen behind the scenes to give you a fast
iterative development experience.
Hope this answers your questions.
- Konstantin

WebLogic Server Tools 1.1 Certified on WTP 2.0.1

WebLogic Server Tools team has just finished certifying the 1.1 release
of WLS Tools on Eclipse 3.3.1 and Web Tools Platform 2.0.1. We recommend
that all WLS Tools 1.1 users move up to these service releases to gain
access to numerous bugs fixes.
Eclipse Downloads
http://www.eclipse.org/downloads/
WebLogic Server Tools 1.1
https://dev2devclub.bea.com/updates/eclipse-3.3/wls-plugins/

I imagine WLS Tools is similar to these plugins in purpose, but I have not used these plugins myself so I do not know for sure. Unlike these older plugins, WLS Tools is based on Eclipse Web Tools Platform and the code base for what makes up WLS Tools originates from BEA Workshop for WebLogic product.
Really, the key to using WLS Tools is getting familiar with Eclipse Web Tools Platform (WTP). Most of the following resources will be framed in terms of deploying to Tomcat. You can just use WLS instead of Tomcat where referenced in the articles and tutorials.
General information about Eclipse Web Tools Platform (WTP)
http://www.eclipse.org/webtools/
Links to books and articles about WTP
http://www.eclipse.org/webtools/community/communityresources.php
Web Application Development User Guide
* find this by going to help content in your Eclipse installation
Hope this helps,
Konstantin
BEA WebLogic Server Tools Team

WebLogic Server Tools 1.1.1 Released

WebLogic Server Tools team has just put finishing touches on another
release. This is mainly a service release that fixes a number of
important bugs. We recommend that all current users migrate to this
release by using the Eclipse update manager. More information about this
release can be found in the release notes.
Main Page
https://dev2devclub.bea.com/updates/wls-tools/
Release Notes
https://dev2devclub.bea.com/updates/wls-tools/release-notes/v1.1.1.html
On a related note, we now have support for Eclipse 3.4 "Ganymede"
platform which is currently under development. This is accomplished via
a separate version of WebLogic Server Tools that's released in parallel
with the existing Eclipse 3.3 "Europa" version. So version 2.0 of WLS
Tools is the 1.1.1 equivalent for Ganymede. Since Ganymede platform is
still under development we don't recommend this version for most users,
but early adopters with tolerance for pre-release stability can get a
sneak peak of what's coming in the next Eclipse release.
Release Notes
https://dev2devclub.bea.com/updates/wls-tools/release-notes/v2.0.0.html
Konstantin Komissarchik
BEA WebLogic Server Tools Team

Hello,
WLS Tools only works with the the admin server.
Interactive development against a managed server is a little different, because they require the admin server during startup and deployment is also a little different with a managed server
is there a specific reason why you are trying to run against a managed server ?
Thanks
Raj

WebLogic Server Tools 1.1 Released

We are happy to announce the 1.1 release of WebLogic Server Tools for Eclipse 3.3. This release contains two major new features as well as 28 bug fixes and enhancements. One of these new features is a direct result of community input. Thanks for helping us make WLS Tools a better product and we hope that you will give the 1.1 release try.
For more information, you can read my blog entry:
http://dev2dev.bea.com/blog/kosta/archive/2007/10/weblogic_server_tools_11_relea.html

WebLogic Server Tools is built on Eclipse Web Tools Platform which has a
particular project structure that has to be followed. Basically, you
create an EAR project. This contains your app-level descriptors,
APP-INF/lib and any binary modules. Then, for every module in an EAR,
you create a separate project. For web module, use the Dynamic Web
Project. For EJB modules, there is an EJB project. The projects are
wired up using the "J2EE Module Dependencies" project properties page.
Use this page on the EAR project to specify which module projects should
be included in the EAR. Once you've done that, you can use this page in
the module projects to specify inter-module dependencies.
Basically, you have to take your app and convert it into the form that
Eclipse can understand. The easiest way to do that is to create the
projects based on the module structure of your app and then copy content
from your application into those projects. Once you are done, you will
be able to use WebLogic Server Tools to deploy to WLS. The split
directory magic will happen behind the scenes to give you a fast
iterative development experience.
Hope this answers your questions.
- Konstantin

Weblogic 8.1 and Eclipse using Weblogic Server Tools

I am working on a project that has been developed with Weblogic 8.1 without integration into an IDE (Eclipse, etc.) We are trying to convert the source tree to a form usable within Eclipse using Weblogic Server Tools. We want to make deployment on developer workstations quicker and easier and provide for server side debugging. There is not much documentation on how to do this that I have been able to find. I have just finished reading the details of the split directory strucuture in the Weblogic documentation and understand that Server Tools uses the split directory concept. My question is basically how we create the project in Eclipse (with Server Tools plug-ins) initially. Is anyone out there still using Weblogic 8.1 and Eclipse 3.3 (Europa) using Weblogic Server Tools that can help?

There isn't much in a way of documentation that's explicit to WebLogic Server Tools, but a lot of Workshop 10.2 documentation applies. Basically, you will want to create Dynamic Web Projects to house your code. On the first page of Dynamic Web Project wizard, you will get a chance to define and target a server (WLS 8.1 in your case). That will configure your project classpath for WLS 8.1 and get everything else squared away.
Note that there is only very basic support for 8.1. In particular, the split-directory concept is not supported, but deployment is taken care of for you behind the scenes, so the details shouldn't matter that much.

Dependency conflicts when installing WebLogic Server Tools in Eclipse Juno

Installing the WebLogic Server Tools in Eclipse (Juno) on Windows 7, 64 bit cannot be completed. Eclipse is up to date and several other plugins are installed.
When installing the server tools, either via the Marketplace or the Server view -> New Server -> Download additional server adapters it fails because of incompatible dependencies. The error message is:
Cannot complete the install because one or more required items could not be found.
Software being installed: Oracle WebLogic Server Tools 2.2.0.201211211917 (oracle.eclipse.tools.juno.weblogic.feature.group 2.2.0.201211211917)
Missing requirement: Oracle Eclipse Tools Environment Checker 5.2.0.201211211917 (oracle.eclipse.tools.envcheck 5.2.0.201211211917) requires 'bundle org.eclipse.ui [3.8.0,3.104.0)' but it could not be found
Cannot satisfy dependency:
From: Oracle Common Tools 2.2.0.201211211917 (oracle.eclipse.tools.juno.common.feature.group 2.2.0.201211211917)
To: oracle.eclipse.tools.envcheck [5.2.0.201211211917]
Cannot satisfy dependency:
From: Oracle WebLogic Server Tools 2.2.0.201211211917 (oracle.eclipse.tools.juno.weblogic.feature.group 2.2.0.201211211917)
To: oracle.eclipse.tools.juno.common.feature.group 0.0.0
Does anyone know how to solve this and get the WebLogic Server Tools installed?
rob schlüter
Edited by: Rob Schlüter on Mar 11, 2013 3:12 AM

See this thread:
Juno 4.2 SR2 and OEPE
Until the next OEPE release comes out, you need to make sure that you are running with Juno SR1 when installing OEPE. Installing into Juno SR2 will not work.
- Konstantin

Throws a weblogic.i18n.tools.GenException

Similar Messages

Maybe you are looking for