Semi-colon in URL from WebLogic 7.0

Hello,
We're running WebLogic 7.0 SP1 on two Sun Solaris 8 boxes clustered
together with JDK 1.3.1_04 and all the necessary Sun patches to suite. The
problem I have is that quite a few of our URLs are hardcoded to have a
question mark (?) to begin a list of parameters, and then that gets encoded
to include the SessionID at the end with an ampersand. That was in WebLogic
5.1, now WebLogic 7.0 uses semi-colons to start the encoded URL, and my URLs
that begin with a question mark are no longer valid and just comes up with a
'Page Cannot Be Displayed' browser message. Anybody else experience this
problem? How do I get around it?
Many thanks!
Dustin

Similar Messages

JMS issues when migration from weblogic 9.2 to 10.3.5

We are facing some issues when migration from weblogic 9.2 to 10.3.5
In weblogic 9.2 :_
BMP Entity EJBs used in our project are read-only in nature using entity cache, below is the configuration details
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN" "http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>
Company
</ejb-name>
<entity-descriptor>
<pool>
<max-beans-in-free-pool>300</max-beans-in-free-pool>
<initial-beans-in-free-pool>150</initial-beans-in-free-pool>
</pool>
<entity-cache>
<max-beans-in-cache>3500</max-beans-in-cache>
<idle-timeout-seconds>100000</idle-timeout-seconds>
<read-timeout-seconds>0</read-timeout-seconds>
<concurrency-strategy>ReadOnly</concurrency-strategy>
</entity-cache>
Entity beans will get refreshed using the JMS messges. with in the MDB descriptor files(weblogic-ejb-jar.xml) we are using the provider URL directly and XA enabled connection factory is set to false.
migration to Weblogic 10.3.5_
With the same configurations MDB are not not getting deployed in weblogic 10 with some exception, so we removed the provider URL from weblogic-ejb-jar.xml and changed the JMS configuration to use foreign JMS and XA enable connection factory is set to true. Now when ever the JMS message is triggered Entity bean is not getting refreshed with the updated values. i.e values are stale.
Can some one look into this and provide your inputs to resolve this issue.

I think the Entity bean refresh problem appears to be unrelated to MDBs. The MDB is only responsible for getting the message to your application (which in turn interacts with Entity beans). You might want to try posting your question to an EJB newsgroup.
Tom

Accessing External Url using Http Utility | Error when using from Weblogic on Solaris

We are using Http Utility (http://jakarta.apache.org/commons/httpclient/) from
Apache for accessing external URL. A XML string is sent as POST parameter to the
URL and the response is also an XML string. The URL is accessed over HTTPS protocol.
I am setting the following parameters in the java class:
Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
// set the property
System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
The java class written to access the external URL using Http Utility works perfectly
fine when it is run from either the command line (of Windows or Solaris using
main() ) or from weblogic on windows. The same java class throws an exception
when run from Solaris instance of Weblogic
2003-09-30 11:02:12,411 FATAL [com.bp.beyondbp.presentation.userregistration.action.LloydsValidator]
EXCEPTION: com.bp.beyondbp.presentation.userregistration.exception.LlyodsValidationFailedException,
MESSAGE: Write Channel Closed, possible SSL handshaking or trust failure;
CAUSE: (java.io.IOException: Write Channel Closed, possible SSL handshaking or
trust failure)
at com.bp.beyondbp.presentation.userregistration.action.LloydsValidator.postXMLtoLloyd(LloydsValidator.java:243)
at com.bp.beyondbp.presentation.userregistration.action.LloydsValidator.validateLlyodsForNewUser(LloydsValidator.java:95)
at com.bp.beyondbp.presentation.userregistration.action.PreferencesActionForm.validate(PreferencesActionForm.java:326)
at org.apache.struts.action.RequestProcessor.processValidate(RequestProcessor.java:942)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:255)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
java.io.IOException: Write Channel Closed, possible SSL handshaking or trust failure
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown
Source)
at com.certicom.tls.record.ReadHandler.interpretContent(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown
Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown
Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at org.apache.commons.httpclient.HttpConnection$WrappedOutputStream.write(HttpConnection.java:1344)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:67)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:125)
at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:779)
at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2179)
at org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase.java:2534)
I tried to debug the problem by looking at system properties on windows and solaris,
the difference that I found was
On Windows
[exec] tModelInstanceInfo_description : com.sun.net.ssl.internal.www.protocol
On Solaris
[exec] tModelInstanceInfo_description : weblogic.utils|weblogic.tils|weblogic.net|weblogic.management
After this I changed the startWLS.sh on Solaris and set
-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol in java options.
On looking the system properties again, the output was
[exec] tModelInstanceInfo_description : com.sun.net.ssl.internal.www.protocol|weblogic.utils|weblogic.utils|weblogic.net|weblogic.management
But still the error is same. Can somebody help me out here as to what is going
wrong? Please find the java class attached for reference, please have a look at
postXMLtoLloyd() method in the class file..
[LloydsValidator.java]

We are using Http Utility (http://jakarta.apache.org/commons/httpclient/) from
Apache for accessing external URL. A XML string is sent as POST parameter to the
URL and the response is also an XML string. The URL is accessed over HTTPS protocol.
I am setting the following parameters in the java class:
Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
// set the property
System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
The java class written to access the external URL using Http Utility works perfectly
fine when it is run from either the command line (of Windows or Solaris using
main() ) or from weblogic on windows. The same java class throws an exception
when run from Solaris instance of Weblogic
2003-09-30 11:02:12,411 FATAL [com.bp.beyondbp.presentation.userregistration.action.LloydsValidator]
EXCEPTION: com.bp.beyondbp.presentation.userregistration.exception.LlyodsValidationFailedException,
MESSAGE: Write Channel Closed, possible SSL handshaking or trust failure;
CAUSE: (java.io.IOException: Write Channel Closed, possible SSL handshaking or
trust failure)
at com.bp.beyondbp.presentation.userregistration.action.LloydsValidator.postXMLtoLloyd(LloydsValidator.java:243)
at com.bp.beyondbp.presentation.userregistration.action.LloydsValidator.validateLlyodsForNewUser(LloydsValidator.java:95)
at com.bp.beyondbp.presentation.userregistration.action.PreferencesActionForm.validate(PreferencesActionForm.java:326)
at org.apache.struts.action.RequestProcessor.processValidate(RequestProcessor.java:942)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:255)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
java.io.IOException: Write Channel Closed, possible SSL handshaking or trust failure
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown
Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown
Source)
at com.certicom.tls.record.ReadHandler.interpretContent(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown
Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown
Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at org.apache.commons.httpclient.HttpConnection$WrappedOutputStream.write(HttpConnection.java:1344)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:67)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:125)
at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:779)
at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2179)
at org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase.java:2534)
I tried to debug the problem by looking at system properties on windows and solaris,
the difference that I found was
On Windows
[exec] tModelInstanceInfo_description : com.sun.net.ssl.internal.www.protocol
On Solaris
[exec] tModelInstanceInfo_description : weblogic.utils|weblogic.tils|weblogic.net|weblogic.management
After this I changed the startWLS.sh on Solaris and set
-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol in java options.
On looking the system properties again, the output was
[exec] tModelInstanceInfo_description : com.sun.net.ssl.internal.www.protocol|weblogic.utils|weblogic.utils|weblogic.net|weblogic.management
But still the error is same. Can somebody help me out here as to what is going
wrong? Please find the java class attached for reference, please have a look at
postXMLtoLloyd() method in the class file..
[LloydsValidator.java]

Subtitle semi\colon question & subtitles take forever to remove from project

I have been having problems with two NTSC DVDs. The subtitles would line up perfectly in Subtitle Workshop put upon importing into Encore (CS3) they would lose sync after about 10 minutes or so. Turns out I was looking in the wrong area (at my MPEG files). On a whim I remembered reading somewhere about replacing the ":" in the subs with ";" and it worked fine!
But I don't know why it worked? I always thought only PAL subtitles needed to be in ";" ??
I went back to all of the subtitle files I did work with on prior projects and they had ":" as well? Those were NTSC how come they did'nt give me problems?
On a related note when I had to "remove subtitles" in CS3 it would take about 4-5 minutes before they cleared. It was faster to shut it down and re-open. Is it a CS3 thing? I know Encore 2 did not do that.

You have it backwards.
NTSC subtitles must use the semi-colon (
;) delimiter because it's drop-frame. PAL timecode is not drop-frame so it always uses the colon (
:) delimiter.
I'm guessing you didn't see problems before because either the video wasn't long enough, or you weren't watching as carefully? Hard to say, but Encore (and other DVD authoring apps that support subtitles) has always behaved in this way.
I'm confused by your related note. You mean to delete a subtitle track takes 4-5 minutes?

Problem with SAX parser - entity must finish with a semi-colon

Hi,
I'm pretty new to the complexities of using SAXParserFactory and its cousins of XMLReaderAdapter, HTMLBuilder, HTMLDocument, entity resolvers and the like, so wondered if perhaps someone could give me a hand with this problem.
In a nutshell, my code is really nothing more than a glorified HTML parser - a web page editor, if you like. I read in an HTML file (only one that my software has created in the first place), parse it, then produce a Swing representation of the various tags I've parsed from the page and display this on a canvas. So, for instance, I would convert a simple <TABLE> of three rows and one column, via an HTMLTableElement, into a Swing JPanel containing three JLabels, suitably laid out.
I then allow the user to amend the values of the various HTML attributes, and I then write the HTML representation back to the web page.
It works reasonably well, albeit a bit heavy on resources. Here's a summary of the code for parsing an HTML file:
      htmlBuilder = new HTMLBuilder();
parserFactory = SAXParserFactory.newInstance();
parserFactory.setValidating(false);
parserFactory.setNamespaceAware(true);
FileInputStream fileInputStream = new FileInputStream(htmlFile);
InputSource inputSource = new InputSource(fileInputStream);
DoctypeChangerStream changer = new DoctypeChangerStream(inputSource.getByteStream());
changer.setGenerator(
   new DoctypeGenerator()
      public Doctype generate(Doctype old)
         return new DoctypeImpl
         old.getRootElement(),
                          old.getPublicId(),
                          old.getSystemId(),
         old.getInternalSubset()
      resolver = new TSLLocalEntityResolver("-//W3C//DTD XHTML 1.0 Transitional//EN", "xhtml1-transitional.dtd");
      readerAdapter = new XMLReaderAdapter(parserFactory.newSAXParser().getXMLReader());
      readerAdapter.setDocumentHandler(htmlBuilder);
      readerAdapter.setEntityResolver(resolver);
      readerAdapter.parse(inputSource);
      htmlDocument = htmlBuilder.getHTMLDocument();
      htmlBody = (HTMLBodyElement)htmlDocument.getBody();
      traversal = (DocumentTraversal)htmlDocument;
      walker = traversal.createTreeWalker(htmlBody,NodeFilter.SHOW_ELEMENT, null, true);
      rootNode = new DefaultMutableTreeNode(new WidgetTreeRootNode(htmlFile));
      createNodes(walker); However, I'm having a problem parsing a piece of HTML for a streaming video widget. The key part of this HTML is as follows:
            <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
              id="client"
        width="100%"
        height="100%"
              codebase="http://fpdownload.macromedia.com/get/flashplayer/current/swflash.cab">
              <param name="movie" value="client.swf?user=lkcl&stream=stream2&streamtype=live&server=rtmp://192.168.250.206/oflaDemo" />
         etc....You will see that the <param> tag in the HTML has a value attribute which is a URL plus three URL parameters - looks absolutely standard, and in fact works absolutely correctly in a browser. However, when my readerAdapter.parse() method gets to this point, it throws an exception saying that there should be a semi-colon after the entity 'stream'. I can see whats happening - basically the SAXParser thinks that the ampersand marks the start of a new entity. When it finds '&stream' it expects it to finish with a semi-colon (e.g. much like and other such HTML characters). The only way I can get the parser past this point is to encode all the relevant ampersands to %26 -- but then the web page stops working ! Aaargh....
Can someone explain what my options are for getting around this problem ? Some property I can set on the parser ? A different DTD ? Not to use SAX at all ? Override the parser's exception handler ? A completely different approach ?!
Could you provide a simple example to explain what you mean ?
Thanks in anticipation !

You probably don't have the ampersands in your "value" attribute escaped properly. It should look like this:
value="client.swf?user=lkcl&stream=...{code}
Most HTML processors (i.e. browsers) will overlook that omission, because almost nobody does it right when they are generating HTML by hand, but XML processors won't.

Multiple Artist, Genre... Separator (Semi-Colon) instead of Smart Playlists

In my opinion, one of the greatest features of ID3 tags is the ability to use semi-colons to differentiate between multiple artists, genres, albums, etc... for any given field. This feature has been available since ID3 tags for MP3's were first implemented over a decade ago.
With Windows Media Player 10, it's database was finally able to parse the information separated by semi-colons correctly. What this means is that if I have a song like "Picture" by Sheryl Crow and Kid Rock, in the ID3 tag, I type "Sheryl Crow; Kid Rock", and in WMP, if I click on Artist | Sheryl Crow, "Picture" appears. And if I click on Artist | Kid Rock, "Picture" appears. In fact, when I rip songs using WMP, it places semi-colons in numerous ID3 fields from the album description.
In iTunes, however, when I import a song with a semi-colon in an ID3 tag field, the database reads the artist as "Sheryl Crow; Kid Rock", or essentially, it treats "Sheryl Crow; Kid Rock" as a THIRD artist. The same is true if I have a song that I feel crosses two genres--like "Picture". In WMP, if I put in the Genre field "Pop; Country", when I choose Genres | Pop, "Picture" appears, and when I choose Genres | Country, "Picture" appears.
Does anyone know if a bug fix for this is in the works for iTunes? It seems Apple and iTunes have been trying to push Smart Playlists for this kind of organization, but that's the poor man's way of organizing songs and not nearly as efficient. I don't want to have to create Smart Playlist for all songs with "Sheryl Crow" in the artist field. It should be inherent based on the semi-colon.
Does anyone know if anything smarter than Smart Playlists is in the works that matches the intuitiveness of Windows Media Player's database?
Thanks,
Bill

Whereas in WMP & the ID3 spec. you would use a semi-colon to separate items you will find that iTunes & the Music store use a slash instead. However as you so rightly say iTunes takes the information and construes a new artist entity rather than two artists connected to the same track. (WMP might also respond to slash - I recall AC/DC always presenting issues so they exist as AC-DC in my library.)
If you'd like to make feature request go to: iTunes Feedback.
Working on the assumption that such ideas are unlikely to implemented any time soon however you might like to see my post on Grouping Tracks Into Albums which covers workarounds for this & other quirks.
tt2

No output at all from weblogic.Admin HELP | GETSTATE | VERSION on linux

Hi, somehow I am getting zero output from weblogic.Admin command, is it redirected somewhere?
#>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -adminurl $AURL -username weblogic -password $WPWD VERSION
#>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -adminurl $AURL -username weblogic -password $WPWD GETSTATE
#>
#>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -username weblogic -password $WPWD HELP
#>
Thanks.

Hi,
You need to Run the SetDomainEnv.sh/cmd from the Domain_Home/bin and then you can execute the below Commands and they will execute succesfully
Eg:From Windows Environment Same applies in Linux Environmet as well
C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl t3://localhost:7001 -username weblogic -password weblogic1 VERSION
WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638
C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl t3://localhost:7001 -username weblogic -password weblogic1 GETSTATE
Current state of "AdminServer" : RUNNING
C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl t3://localhost:7001 -username weblogic -password weblogic1 HELP
Usage: java [<SSL trust options>] weblogic.Admin
        [ [-url | -adminurl] [<protocol>://]<listen-address>:<port>]
        -username <username> [-password <password>]
        <COMMAND> <ARGUMENTS>
Hope it helps

How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?

Dear All,
I have one statement int weblogic 5.1 weblogic.propertis as follow,
weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
but after converting to weblogic 6.1 there are no corresponding statement in
the file config.xml. And when i start the new application, error occured.
what should I do?
The error message is:
<2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
.\config\tbcn\config.xml
<2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initializatio
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception

Dear Satya,
My weblogic propertis file as follow,
# CORE PROPERTIES
# You should set these before you start the WebLogic Server the first time.
# If you need more instructions on individual properties in this
# section, check the same section in the Optional Properties, where
# we've left the long explanations. Or, better yet, go to our
# website and read all about properties, at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# CORE SYSTEM PROPERTIES
# TCP/IP port number at which the WebLogic Server listens for connections
weblogic.system.listenPort=7001
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8 characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.password.system=12345678
# RECOMMEND Set to 'everyone' if HTTPD is enabled
weblogic.allow.execute.weblogic.servlet=everyone
# Set individual ACLs to restrict access to HTTP-related resources,
# such as the Administration servlets.
# To make your own servlets generally available, follow this
# pattern (provide a weblogic.allow.execute) for your packages and
# set ACLs as appropriate.
# CORE SECURITY-RELATED PROPERTIES FOR SSL
# Read important information about SSL at:
# http://www.weblogic.com/docs51/classdocs/API_secure.html
# Enable SSL
# (default if property not defined is false)
weblogic.security.ssl.enable=true
# SSL listen port
weblogic.system.SSLListenPort=7002
# Servlets for SSL
# Authentication servlet for creating tokens for applets
weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
ervlet
# Limits number of unclaimed stored tokens
weblogic.security.certificateCacheSize=3
# Capture CA root of client servlet
weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
# Certificates for SSL
# Name of acceptable CA roots
# For client authentication change value to a valid .pem file
#weblogic.security.clientRootCA=SecureServerCA.pem
# Server certificates for SSL
weblogic.security.certificate.server=democert.pem
weblogic.security.key.server=demokey.pem
weblogic.security.certificate.authority=ca.pem
# registration for certificate generator servlet
weblogic.httpd.register.Certificate=utils.certificate
weblogic.allow.execute.weblogic.servlet.Certificate=system
# CORE HTTPD ADMINISTRATIVE PROPERTIES
# True permits the HTTPD to run (default)
# Uncomment this property to disable HTTPD
#weblogic.httpd.enable=false
# If authentication is required, add username/password for each user
# who will be included in an ACL, as in this commented-out example:
#weblogic.password.peter=#8gjsL4*
# SYSTEM PROPERTIES
# System properties in this section are set to system defaults
# Performance pack. The shared library must be accessible from your
# PATH (NT) or from your shared library path (UNIX; the name of the
# variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
weblogic.system.nativeIO.enable=true
# Outputs logging information to the console as well as to the log file
weblogic.system.enableConsole=true
# Sets the directory or URL for the WebLogic Admin help pages
# The help pages are shipped in the "docs/adminhelp" directory, in the
# default document root in public_html
weblogic.system.helpPageURL=/weblogic/myserver/public_html/docs51/adminhelp/
# If you prefer to access the most recent help pages, you can do so online
# by commenting out the previous property and uncommenting this one:
#weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
# Properties for tuning the server's performance
# Number of WebLogic Server execute threads.
weblogic.system.executeThreadCount=15
# Other optional system properties
# Limits size of weblogic.log (in K) and versions old log
weblogic.system.maxLogFileSize=1024
# Adjust minimum length of password
weblogic.system.minPasswordLen=8
# UNIX only: If running on port 80 on UNIX, enable the setUID program
#weblogic.system.enableSetUID=false
# UNIX only: Unprivileged user to setUID to after starting up
# WebLogic Server on port 80
#weblogic.system.nonPrivUser=nobody
# CLUSTER-SPECIFIC PROPERTIES
# Cluster-specific properties in this section are set to system defaults.
# CLUSTER USERS: Note that ALL Cluster-specific properties should be set
# in the per-cluster properties file ONLY.
# Time-to-live (number of hops) for the cluster's multicast messages
# (default 1, range 1-255).
#weblogic.cluster.multicastTTL=1
# Sets the load-balancing algorithm to be used between
# replicated services if none is specified. If not specified,
# round-robin is used.
#weblogic.cluster.defaultLoadAlgorithm=round-robin
# SERVER-SPECIFIC CLUSTER PROPERTIES
# Cluster-related properties in this section are set to system defaults.
# CLUSTER USERS: Note that these server-specific cluster-related properties
# should be set in the per-server properties file ONLY.
# Sets the weight of the individual server for the weight-based
load-balancing.
# Range is 0 - 100.
# Larger numbers increase the amount of traffic routed to this server.
#weblogic.system.weight=100
# SYSTEM STARTUP FILES - Examples
# CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
# objects should be registered in the per-server properties file.
# All other startup classes should be registered in the per-cluster
# properties file.
# For more info on writing and using startup file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
# This example shows the entry for examples/t3client/StartupQuery.java
#weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
#weblogic.system.startupArgs.doquery=\
# query=select * from emp,\
# db=jdbc:weblogic:pool:demoPool
# SYSTEM SHUTDOWN FILES - Examples
# For more info on writing and using shutdown file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a shutdown class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
# Add arguments for the shutdown class
#weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
# This example shows the entry for examples/t3client/ShutdownTest.java
#weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
#weblogic.system.shutdownArgs.ShutdownTest=\
# outfile=c:/temp/shutdown.log
# SECURITY-RELATED PROPERTIES FOR WORKSPACES
# For backward compatibility, the following entries disable Access
# Control on Workspaces
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
# JOLT FOR WEBLOGIC PROPERTIES
# These properties configure a BEA Jolt connection pool for use with
# the simpapp and bankapp examples, and register a servlet for use with
# with the simpapp example. The default server address provided here
# points to a public TUXEDO server that is hosted by BEA for use with
# this example.
# Servlet registration for simpapp example:
#weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
t
# Pool creation and cleanup
# note this example is set up to work with the public
# demo TUXEDO server available from BEA's website:
#weblogic.system.startupClass.demojoltpoolStart=\
# bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
#weblogic.system.startupArgs.demojoltpoolStart=\
# poolname=demojoltpool,\
# appaddrlist=//beademo1.beasys.com:8000,\
# failoverlist=//beademo1.beasys.com:8000,\
# minpoolsize=1,\
# maxpoolsize=3
#weblogic.system.shutdownClass.demojoltpoolStop=\
# bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
#weblogic.system.shutdownArgs.demojoltpoolStop=\
# poolname=demojoltpool
# WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
# The registrations enable a BEA IIOP connection pool and
# register servlets for use with the simpapp and university examples.
# Configure for your environment and uncomment to use.
# Uncommenting these properties requires WebLogic Enterprise Connectivity
# and an operating WebLogic Enterprise Server.
# Servlet registration for simpapp servlet example
#weblogic.httpd.register.SimpappServlet=\
# examples.wlec.servlets.simpapp.SimpappServlet
#weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
# Servlet registration for simpapp EJB example
# (You'll need to add the wlec_ejb_simpapp.jar to the
# weblogic.ejb.deploy property in this file.)
#weblogic.httpd.register.ejbSimpappServlet=\
# examples.wlec.ejb.simpapp.ejbSimpappServlet
#weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
# Pool creation and cleanup for the simpapp example
#weblogic.CORBA.connectionPool.simplepool=\
# appaddrlist=//wlehost:2468,\
# failoverlist=//wlehost:2468,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# domainname=simpapp
# Servlet registration for university Servlet example:
#weblogic.httpd.register.UniversityServlet=\
# examples.wlec.servlets.university.UniversityServlet
#weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
# Pool creation and cleanup for the University example:
#weblogic.CORBA.connectionPool.Univpool=\
# appaddrlist=//wlehost:2498,\
# failoverlist=//wlehost:2498,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# apppassword=wlepassword,\
# domainname=university
# WEBLOGIC FILE PROPERTIES
# Maps a volume name to a path, for client file read/write
#weblogic.io.fileSystem.[volumeName]=[fullPathName]
# WEBLOGIC JMS DEMO PROPERTIES
# CLUSTER USERS: Note that ALL JMS deployment should be done in the
# per-cluster properties file ONLY.
# You set up a JDBC connection pool if you want persistent messages
# (including durable subscriptions). To use JMS and EJBs in the same
# transaction, both must use the same JDBC connection pool. Uncomment
# the following property to use the default JDBC connection pool
# 'demo', which is defined in the Demo connection pool section of this file.
#weblogic.jms.connectionPool=demoPool
# The JMS Webshare example demonstrates how the ClientID for a
# durable subscriber is configured in the connection factory:
#weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
#weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
#weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
#weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
# The JMS trader example shows how to use JMS with an EJB. In addition
# to uncommenting the following properties, you must also set up and
# deploy the EJB example examples.ejb.basic.statelessSession.Trader in
# ejb_basic_statelessSession.jar to try out this JMS example:
#weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
#weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
#weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
#weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
# Registers the underlying servlet
#weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
# These properties are used with the ServerReceive JMS example,
# which demonstrates how to establish a JMS message consumer
# in a startup class:
#weblogic.system.startupClass.serverReceive=\
# examples.jms.startup.ServerReceive
#weblogic.system.startupArgs.serverReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# These properties are used with the PoolReceive JMS example,
# which demonstrates how to establish a pool of JMS message consumers
# in a startup class:
#weblogic.system.startupClass.poolReceive=\
# examples.jms.startup.PoolReceive
#weblogic.system.startupArgs.poolReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
#weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
# WEBLOGIC RMI DEMO PROPERTIES
# CLUSTER USERS: Note that pinned RMI objects should be registered
# in the per-server properties file ONLY. All other RMI startup
# classes should be registered in the per-cluster properties file.
# Remote classes registered at startup after the pattern:
#weblogic.system.startupClass.[virtualName]=[fullPackageName]
# These examples can be compiled to see RMI in action. Uncomment to use:
#weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
#weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
#weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
# WEBLOGIC EJB DEMO PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# See WebLogic Demo Connection Pool below for a connection pool
# to use with these examples.
# Deploys EJBeans. Uncomment the appropriate lines below and
# modify DBMS-related info and paths to match your particular installation:
# TBCN EJB PROPERTIES
weblogic.ejb.deploy=\
C:/weblogic/myserver/AccountSB.jar, \
C:/weblogic/myserver/AddressEntryDet.jar, \
C:/weblogic/myserver/AddressEntry.jar, \
C:/weblogic/myserver/Affiliate.jar, \
C:/weblogic/myserver/ContactPerson.jar, \
C:/weblogic/myserver/ContactSB.jar, \
C:/weblogic/myserver/Factory.jar, \
C:/weblogic/myserver/FactorySups.jar, \
c:/weblogic/myserver/LoginUsers.jar, \
c:/weblogic/myserver/Member.jar, \
c:/weblogic/myserver/MemberQuotaUsage.jar,\
c:/weblogic/myserver/MemberToCategory.jar,\
c:/weblogic/myserver/Organization.jar, \
c:/weblogic/myserver/Person.jar, \
c:/weblogic/myserver/QuotaType.jar,\
c:/weblogic/myserver/Registration.jar, \
c:/weblogic/myserver/TempAccounts.jar, \
c:/weblogic/myserver/TempDomain.jar, \
c:/weblogic/myserver/UserAccount.jar, \
c:/weblogic/myserver/UserRole.jar, \
c:/weblogic/myserver/BuyerProducts.jar, \
c:/weblogic/myserver/Catalog.jar, \
c:/weblogic/myserver/Categories.jar, \
c:/weblogic/myserver/CategoryToCategory.jar, \
c:/weblogic/myserver/CountryToCategory.jar, \
c:/weblogic/myserver/InvitedMember.jar, \
c:/weblogic/myserver/ProductOrigin.jar, \
c:/weblogic/myserver/ProductOtherFee.jar,\
c:/weblogic/myserver/ProductSups.jar, \
c:/weblogic/myserver/Products.jar,\
c:/weblogic/myserver/ProductToCategory.jar, \
c:/weblogic/myserver/SecondaryQcEntry.jar, \
c:/weblogic/myserver/CodeClass.jar,\
c:/weblogic/myserver/ConfirmationSB.jar, \
c:/weblogic/myserver/PurchasedPackage.jar,\
c:/weblogic/myserver/RejectReasonCode.jar, \
c:/weblogic/myserver/ServiceOrder.jar,\
c:/weblogic/myserver/ServiceOrderLog.jar,\
c:/weblogic/myserver/ServiceOrderState.jar,\
c:/weblogic/myserver/ServiceOrderType.jar,\
c:/weblogic/myserver/ServicePackageDetails.jar, \
c:/weblogic/myserver/ServicePackage.jar, \
c:/weblogic/myserver/ServicePayment.jar, \
c:/weblogic/myserver/ServiceReqSB.jar, \
c:/weblogic/myserver/TAM.jar, \
c:/weblogic/myserver/SubscriptionEB.jar, \
c:/weblogic/myserver/PostingCategoryEB.jar, \
c:/weblogic/myserver/PostingBrowsedEB.jar, \
c:/weblogic/myserver/PostingInfoEB.jar, \
c:/weblogic/myserver/TransactionLogEB.jar, \
c:/weblogic/myserver/PostingSB.jar
#weblogic.ejb.deploy=\
# d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
# d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
# d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
# d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
# d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
# d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
# d:/weblogic/myserver/ejb_subclass.jar, \
# d:/weblogic/myserver/jolt_ejb_bankapp.jar
# Servlet used by the EJB basic beanManaged example
# Uncomment to use:
weblogic.httpd.register.beanManaged=\
examples.ejb.basic.beanManaged.Servlet
# Add a list of users (set the password with
weblogic.password.[username]=XXX)
# to set an ACL for this servlet:
#weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
#weblogic.password.user1=user1Password
#weblogic.password.user2=user2Password
# WEBLOGIC XML DEMO PROPERTIES
# These properties are required to run the XML examples.
# Uncomment to use.
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
#weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
# BizTalk example properties
#weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
#weblogic.jms.queue.tradeError=biztalk.jms.tradeError
#weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
dapter
#weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
# WEBLOGIC ZAC DEMO PROPERTIES
# These registrations enable the ZAC Publish Wizard.
weblogic.zac.enable=true
# Set the publish root for a WebLogic Server. Edit and
# uncomment to use.
#weblogic.zac.publishRoot=d:/weblogic/zac
# Set an ACL for each package you publish. The [name] is
# the "Package name" you assign in the ZAC Publish Wizard.
# Publish a package, edit this property, and uncomment to use.
#weblogic.allow.read.weblogic.zac.[name]=[user list]
#weblogic.allow.write.weblogic.zac.[name]=system
# HTTPD ADMINISTRATIVE PROPERTIES
# Enables logging of HTTPD info in common log format and
# sets the log file name (default is "access.log" in "myserver")
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
# Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
weblogic.httpd.enableEvents=false
# Enables HTTP sessions
weblogic.httpd.session.enable=true
# Sets an optional cookie name. The default name is "WebLogicSession".
# Prior to version 4.0, the default was "TengahSession". To make
# this backward compatible with cookies generated from previous
# installations, you should set this property to "TengahSession".
# Uncomment this line and set this to any string of your choice,
# or comment out this property to use the default.
#weblogic.httpd.session.cookie.name=WebLogicSession
# MIME types
weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.image/gif=gif
weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.application/pdf=pdf
weblogic.httpd.mimeType.application/zip=zip
weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.application/x-java-archive=jar
weblogic.httpd.mimeType.application/x-java-serialized-object=ser
weblogic.httpd.mimeType.application/octet-stream=exe
weblogic.httpd.mimeType.text/vnd.wap.wml=wml
weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
# In seconds, the keep-alive for HTTP and HTTPS requests
weblogic.httpd.http.keepAliveSecs=60
weblogic.httpd.https.keepAliveSecs=120
# WEBLOGIC JDBC DRIVER PROPERTIES
# Enables JDBC driver logging and sets the file name for the log
# The weblogic.jdbc.logFile is placed in the per-server
# directory (default is "myserver")
weblogic.jdbc.enableLogFile=false
weblogic.jdbc.logFileName=jdbc.log
# WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# For creating JDBC connection pools. This example shows a connection
# pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
# to use 4 JDBC connections (with a potential for up to 10 connections,
# incremented by two at a time, with a delay of 1 second between each
# attempt to connect to the database), to an Oracle database server called
# "DEMO." If more than 4 connections are opened, after 15 minutes, unused
# connections are dropped from the pool until only 4 connections remain
open.
# Every 10 minutes, any unused connections in the pool are tested and
# refreshed if they are not viable.
#weblogic.jdbc.connectionPool.oraclePool=\
# url=jdbc:weblogic:oracle,\
# driver=weblogic.jdbc.oci.Driver,\
# loginDelaySecs=1,\
# initialCapacity=4,\
# maxCapacity=10,\
# capacityIncrement=2,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshMinutes=10,\
# testTable=dual,\
# props=user=SCOTT;password=tiger;server=DEMO
# Get more details on each argument for this property in the
# Administrators Guide on setting properties at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# Set up ACLs for this connection pool with the following:
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
# guest,joe,jill
#weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
#weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
# This property is an ACL that specifies the users who can
# create dynamic connection pools:
#weblogic.jdbc.connectionPoolcreate.admin=joe,jill
# Read more about setting up and using connection pools in the
# developers guide for WebLogic JDBC at:
# http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
# TBCN JDBC CONNECTION POOL MANAGEMENT
weblogic.jdbc.connectionPool.oraclePool=\
url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=2,\
maxCapacity=10,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,\
testTable=dual,\
props=user=tbcn;password=ca91768
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
# WEBLOGIC DEMO CONNECTION POOL PROPERTIES
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# This connection pool uses the sample Cloudscape database shipped
# with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
# Uncomment to use:
#weblogic.jdbc.connectionPool.demoPool=\
# url=jdbc:cloudscape:demo,\
# driver=COM.cloudscape.core.JDBCDriver,\
# initialCapacity=1,\
# maxCapacity=2,\
# capacityIncrement=1,\
# props=user=none;password=none;server=none
# Add a TXDataSource for the connection pool:
#weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
# Add an ACL for the connection pool:
#weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
# WEBLOGIC HTTP SERVLET PROPERTIES
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
# WebLogic offers different types of servlets for various uses.
# Classpath servlet registration
# The ClasspathServlet is used to serve classes from
# the system CLASSPATH. It is used by applets to load
# classes they depend upon, and is registered against
# the virtual name 'classes' here by default. This means
# you should set your applet codebase to "/classes".
# You can register multiple virtual names for this servlet.
# Note that it can also be used to serve other
# resources/files from the system CLASSPATH.
# Don't confuse the ClasspathServlet with the ServletServlet. The
# ClasspathServlet is used for serving classes for client-side Java only.
# The ServletServlet is used to invoke unregistered servlets.
# See the Administrators Guide "Setting up WebLogic as an HTTP server"
# http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
info.
weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
# We also set an open ACL for everyone to call the ClasspathServlet
# so that applets work without requiring further changes.
weblogic.allow.execute.weblogic.servlet.classes=everyone
# File servlet registration
# FileServlet searches below the documentRoot for the requested file
# and serves it if found. If the requested file is a directory,
# FileServlet will append the defaultFilename to the requested path
# and serve that file if found.
weblogic.httpd.register.file=weblogic.servlet.FileServlet
weblogic.httpd.initArgs.file=defaultFilename=index.html
weblogic.httpd.indexFiles=zh_TW/index.htm
# ServerSideInclude servlet registration
# SSIServlet searches below the documentRoot for the
# requested .shtml file and serves it if found.
weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
# Example URL: http://localhost:7001/portside/welcome.shtml
# for the file /weblogic/myserver/public_html/portside/welcome.shtml
# PageCompileServlet (used by JHTML)
# See the information below under WebLogic JHTML
# JSPServlet (used by JSP)
# See the information below under WebLogic JSP
# ServletServlet registration
# Allows unregistered servlets in the servlet classpath (see Servlet
# reload properties below) to be r

Error connecting to websphere MQ from weblogic 10.3.0 :EndPointFinder

1)     We are in process of connection from weblogic 10.3.0 to websphere MQ series . We are trying connecting to the response queues using MQclient binding . I created .binding file using following configuration
DEFINE QCF(BBNMSRMSConnectionFactory2) QMGR(ESBMBJU2) CHAN(ESBMBJU2_SSL) HOST(bos69872.bst.bls.com) PORT(1414) TEMPMODEL(WEBLOGIC.MODEL.QUEUE) TRAN(CLIENT)
DEFINE QCF(BBNMSRMSConnectionFactory2) QMGR(ESBMBJU2) CHAN(ESBMBJU2_SSL) HOST(bos69874.bst.bls.com) PORT(1415) TEMPMODEL(WEBLOGIC.MODEL.QUEUE) TRAN(CLIENT)
DEFINE Q(BBNMSSERESPONSEQUEUE1) QUEUE(FUSIONQL.BBNMSE.BBNMSTORMS.1_0.D.JU.RSP) QMGR(ESBMBJU1) TARGCLIENT(MQ)
DEFINE Q(BBNMSSERESPONSEQUEUE2) QUEUE(FUSIONQL.BBNMSE.BBNMSTORMS.1_0.D.JU.RSP) QMGR(ESBMBJU2) TARGCLIENT(MQ)
DEFINE QCF(BBNMSRMSCF1) QMGR(ESBMBJU1) CHAN(ESBMBJU1_SSL) HOST(bos69872.bst.bls.com) PORT(1414) TEMPMODEL(WEBLOGIC.MODEL.QUEUE) TRAN(CLIENT)
ALTER QCF(BBNMSRMSConnectionFactory1) CHAN(ESBMBJU1_SSL) SSLCIPHERSUITE(SSL_RSA_WITH_NULL_MD5)
ALTER QCF(BBNMSRMSConnectionFactory2) CHAN(ESBMBJU2_SSL) SSLCIPHERSUITE(SSL_RSA_WITH_NULL_MD5)
2)     The I created the foreign JMS-server as such :
<foreign-server name="ForeignRmsServer-1">
<default-targeting-enabled>true</default-targeting-enabled>
<foreign-destination name="RmsFusionBusRequestQueue1">
<local-jndi-name>RmsResponseQueue1</local-jndi-name>
<remote-jndi-name>BBNMSSERESPONSEQUEUE1</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="RmsFusionBusFactory1">
<local-jndi-name>RmsFusionBusfactory1</local-jndi-name>
<remote-jndi-name>BBNMSRMSConnectionFactory1</remote-jndi-name>
<username>m66300d</username>
<password-encrypted xsi:nil="true"/>
</foreign-connection-factory>
<initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
<connection-url>file:/opt/mqm/java/bin/mqjndi</connection-url>
</foreign-server>
3)     Subsequently I use the JNDI names configured in foreign server(above) in weblogic-ejb-jar.xml .
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<weblogic-enterprise-bean>
<ejb-name>RMSRespMDB</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>10</max-beans-in-free-pool>
<initial-beans-in-free-pool>5</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>BBNMSSERESPONSEQUEUE1</destination-jndi-name>
<initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
<provider-url>file:/opt/mqm/java/bin/mqjndi</provider-url>
<connection-factory-jndi-name>BBNMSRMSConnectionFactory1</connection-factory-jndi-name>
</message-driven-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>jms.RMSRespMDB</jndi-name>
<dispatch-policy>JbbosServicesServerXQ</dispatch-policy>
</weblogic-enterprise-bean>
<weblogic-compatibility>
<entity-always-uses-transaction>true</entity-always-uses-transaction>
</weblogic-compatibility>
</weblogic-ejb-jar>
4)     Now when my MDB comes up its giving following error
Mar 8, 2011 10:13:16 AM EST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application
'RMSRespMDB'.
weblogic.application.ModuleException: Exception activating module: EJBModule(RMSRespMDB)
Unable to deploy EJB: RMSRespMDB from RMSRespMDB.jar:
unable to find EndPointFinder for file:/opt/mqm/java/bin/mqjndi
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
Truncated. see log file for complete stacktrace
java.lang.AssertionError: unable to find EndPointFinder for file:/opt/mqm/java/bin/mqjndi
at weblogic.rmi.spi.RMIRuntime.getEndPointFinder(RMIRuntime.java:61)
at weblogic.rmi.spi.RMIRuntime.findOrCreateEndPoint(RMIRuntime.java:42)
at weblogic.rmi.extensions.server.RemoteDomainSecurityHelper.isRemoteDomain(RemoteDomainSecurityHelper.java:379)
at weblogic.jms.common.ServerCrossDomainSecurityUtil.isRemoteDomain(ServerCrossDomainSecurityUtil.java:319)
at weblogic.jms.common.ServerCrossDomainSecurityUtil.getRemoteSubject(ServerCrossDomainSecurityUtil.java:116)
Truncated. see log file for complete stacktrace
>
My binding file is correctly placed on the following location file:/opt/mqm/java/bin/mqjndi with appropriate permissions
Some info :
Our weblogic version is 10.3.0
I tracked this exception (unable to find EndPointFinder) to bug id 8168598
Can anyone please suggest what can be issue potentially
Thanks in advance

hi,
Even i want to connect webspere MQ 7 with weblogic 10.3, can u suggest me some document where i can follow step by step?
I have too tried using some binding file,but it is not reading the same.

Calling a webservice from weblogic EJB Application

Hello,
I have a webservice running on IIS server. I created a simple java client program to call the webservice and it works fine. However, when I wrapped the same java client program as a EJB Application, I am unable to call the webservice.
I get the following error:
####<Apr 3, 2007 1:59:30 AM CDT> <Info> <WebService> <CASEJBServer> <ExecuteThread: '24' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-220094> <An IOException was thrown trying to access the WSDL at the given URL.>
And
"java.io.FileNotFoundException: Response: '401: Unauthorized' for url: XXXXXX"
Could you please give some simple steps as what are the JAR Files required to be included in the Weblogic Server's classpath to call the webservice.
Thanks.

To start off you need to make sure that your client api is in the classpath, either in your ejb or your ear or the server classpath.
The other concern I would have is that it seems you are just not authorized to access the URL.
- Does the WSDL require credentials? So in other words when you go to the URL are you allowed to access the WSDL without athenticating.
- How does your Impl get created?
MyServiceImpl service = new MyServiceImpl()
If you are using the empty constructor then what is the wsdl endpoint in your jar file since that is the wsdl it will use. If the endpoint is localhost/xxx/xxx then you will have issues since that means your not deployed on localhost. What url is at the endpoint? Do you have access to the url from your server?
If you are using "new MyServiceImpl(url);" then again is the wsdl locked down because in this case you will need to do somthing like http://username:[email protected]/xxx?wsdl
Hope this helps.
-Jesus

EncodeURL - uses semi-colon or question mark in path?

I am confused about the encodeURL method and how it formats urls when adding the session ID. It was my understanding that the sessionID is added as a path parameter, which means it becomes part of the query string following a "?" in the url, like so:
www.mydomain.com/servlet/CheckOut?jsessionid=567
However, the book I'm using (Java 2 Web Developer Certification Study Guide by Sybex), says that a semi-colon is used instead, like so:
www.mydomain.com/servlet/CheckOut;jsessionid=567
Which one is it? Or is this entirely server-dependent? Either way the next processing servlet needs to be able to access that ID using getPathInfo().

encudeURL exactly does what you says
www.mydomain.com/servlet/CheckOut;jsessionid=567
I am also using the same book you use, it seems that you are preparing for the exam?
Regards
the exam?
Regards

Author metadata separated by semi-colons truncated in file properties and "Get Info"

I'm using Acrobat Professional 9.0 (CS3) for Mac to edit the metadata for a collection of PDFs to be made available on the web. When I enter the data, I am inputting a list of authors separated by commas, like this: Smith J, Watson C, Brown J. If I click on "Additional metadata", the data I've already entered is transposed into the various XMP fields. And the commas separating the author names are changed to semi-colons. I gather that this happens because XMP wants to separate multiple authors with semi-colons, and Acrobat wants the metadata in XMP fields to match the metadata stored for the file properties. Fine.
However, if I save such a PDF and then use Get Info on my Mac (OSX 10.4) to look at the file properties, the list of authors is now truncated where the first semi-colon appears. The list is also truncated in Windows XP if I right-click and select properties. The list is also truncated when I look at the file properties in Preview on my Mac, or if I look at file properties using FoxIT, or using Adobe Acrobat Reader 7 or earlier. The only way a site visitor will actually be able to view the full list of authors in a file saved this way is to use Adobe Reader version 8 or later.
I would like to preserve XMP/Dublin Core/etc metadata in the proper format in the XMP code, but would also like users of standard, popular file viewers to be able to access the full list of authors. Is there a way to do this with Acrobat 9?
Also, once I've saved a file and the XMP metadata has been altered, Acrobat seems to permanently change the way that the authors are listed in the file properties. I cannot manually change those settings any longer without Acrobat overriding my changes and converting commas to semi-colons, or surrounding the entire list of authors in quotation marks. Is there a way to get around these Acrobat overrides and manually take control of my metadata again?
Does Windows Vista read the authors list correctly in the file properties if it is separated by semi-colons?
It seems to me that in an attempt to get XMP metadata working smoothly across the entire CS line, Adobe has jumped the gun somewhat and is now forcing Acrobat users to use "file properties" metadata that is really only fully compatible with Adobe products. Is there a way I can get some backwards compatibility on this?
Thanks for any suggestions or insight anyone can provide to this vexing issue.
Phil.

Bridge has some pretty powerful and helpful features. However, I am unable to figure out how to access the non-XMP "file properties" fields through Bridge, and if I add metadata via Bridge, then I run into the same problem regarding the use of semi-colons to separate authors.
If I had more time, or a larger set of files I might investigate the use of ExtendScript to import all my metadata from an Excel file (where it already exists) into the PDF file properties and XMP metadata.
The best solution for my case though appears to be to use Acrobat 9 and to do the double-edit process for each file. I should be able to just cut-and-paste the metadata from the Excel file, and then if I save the Authors list to the end, I can simply paste it once into the XMP field (through the Advanced metadata button) and then return to the regular file properties page and paste it again in there, where Acrobat will add quotes around it.
Lastly, if anyone else happens to find this post and is looking for similar information, I would recommend searching in the Bridge forum as well as the Acrobat forum.
Phil.

How to save an excel file as CSV with semi-colon as data separator?

We are creating a flat data file to load the flat file data to our BW system with Excel. When we save the file, there are three kinds of CSV types for selecting from the "Save as type" list box:
CSV (Comma delimited)
CSV (Macintosh)
CSV (MS-DOS)
There is no CSV (semi colon delimited) type. If we pick CSV (Comma delimted) as the type, then when clicking the "Preview ..." picture icon under the "DataSource/Trans. Structure" tab of the InfoSource for this flat file (with the CSV radio button checked the Data separator default is ";"), the File Upload Preview window shows the data is messed up that some columns of the excel flat file are combined into one column.
Since the save type we picked is "CSV (Comma delimited)", then we try to change the default Data separator from ";" to "," in the preview selection screen, but still not helpful!
How to resolve the above problem?
Thanks

Hi Kevin,
This "," is defined in your windows setting. If you want to have ";" as separator then go to control Panel, select Regional Options, go to Numbers Tab and define the List separator as ";". After that when you will save your excel file as CSV(MS-DOS) it will have ";" as separator. This will make sure that the amounts are not broken in to two different fields while loading.
Else if you keep "," as separator then you can also go into the Excel and define all number fields as Number without thousand separator.
Let me know if you have any doubts in this.
Regards,
Rohit

Using JDriver for Oracle 8i from Weblogic server 6.1

Hi
We have solaris machine running Weblogic server 6.1 SP1 and another solaris running Oracle 8i. I have installed client libraries in machine running WLS 6.1. I have set the LD_SERVER_PATH in setEnv.sh file of weblogic. when i create coinnection pool from WLS CONSOLE and i restart it it is throwing an error
Jan 3, 2002 4:48:21 PM GMT-05:00> <Error> <JDBC> <Cannot startup
connection pool "OraclePool" weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary(weblogicoci37) threw
java.lang.UnsatisfiedLinkError:
/oracle8i/CAPS/bea/wlserver6.1/lib/solaris/oci816_8/libweblogicoci37.so:
ld.so.1:
/oracle8i/CAPS/bea/jdk131/jre/bin/../bin/sparc/native_threads/java:
fatal: /oracle8i/product/8.1.6/lib64/libclntsh.so.8.0: wrong ELF class:
ELFCLASS64
at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:226)
at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
at
weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connec
tionEnvFactory.java:192)
at
weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connec
tionEnvFactory.java:134)
at
weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocat
or.java:698)
at
weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java
:282)
at
weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java
:629)
at
weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deploym
entTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deploy
mentTarget.java:279)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploymen
ts(DeploymentTarget.java:233)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Dep
loymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBean
Impl.java:608)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.ja
va:592)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configuration
MBeanImpl.java:352)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy33.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployme
nts(ServerMBean_CachingStub.java:2734)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(
ApplicationManager.java:362)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationMa
nager.java:154)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBean
Impl.java:608)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.ja
va:592)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configuration
MBeanImpl.java:352)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy46.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.st
art(ApplicationManagerMBean_CachingStub.java:480)
at
weblogic.management.Admin.startApplicationManager(Admin.java:1151)
at weblogic.management.Admin.finish(Admin.java:570)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:506)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
at
weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connec
tionEnvFactory.java:208)
at
weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connec
tionEnvFactory.java:134)
at
weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocat
or.java:698)
at
weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java
:282)
at
weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java
:629)
at
weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deploym
entTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deploy
mentTarget.java:279)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploymen
ts(DeploymentTarget.java:233)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Dep
loymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBean
Impl.java:608)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.ja
va:592)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configuration
MBeanImpl.java:352)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy33.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployme
nts(ServerMBean_CachingStub.java:2734)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(
ApplicationManager.java:362)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationMa
nager.java:154)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBean
Impl.java:608)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.ja
va:592)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configuration
MBeanImpl.java:352)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
at $Proxy46.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.st
art(ApplicationManagerMBean_CachingStub.java:480)
at
weblogic.management.Admin.startApplicationManager(Admin.java:1151)
at weblogic.management.Admin.finish(Admin.java:570)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:506)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
I would appreciate if you can offer some help.
Thanks,
S Gopikrishna

IT WORKS FINE FOR ME.
Script that starts the bwls...
CTP=t3://wls_ip:port
JAVA_HOME=/usr/j2se
WL_HOME=/weblogic61
ORACLE_HOME=/oracle/oracle_client
NLS_LANG=american_america.WE8ISO8859P1
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
PATH=$PATH:$JAVA_HOME/bin:/usr/ccs/bin:/usr/ucb:$ORACLE_HOME/bin
LD_LIBRARY_PATH=$WL_HOME/lib/solaris/oci815_8:$ORACLE_HOME/lib
export LD_LIBRARY_PATH PATH ORA_NLS33 NLS_LANG ORACLE_HOME
SET CLASSPATH
START WLS
weblogic.properties
weblogic.jdbc.connectionPool.MyOraPool=\
url=jdbc:weblogic:oracle,\
driver=weblogic.jdbc.oci.Driver,\
loginDelaySecs=1,\
initialCapacity=3,\
maxCapacity=9,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=12,\
refreshMinutes=10,\
props=user=orausr;password=orafoousr;server=ORASERVER;weblogic.oci.min_bind_size=1000

Semi colon madness

At the end of my quiz, the email opens up fine and the
information is there, but there is a semi-colon added to the end of
my email address for some reason. This brings up a syntax error
message from the email program. My quiz is going to go out to a lot
of non-computer savvy folks. They will not be able to figure out
that they have to delete the semi-colon.
Why does it appear? It is not there in the email field in the
Quiz preferences field of Captivate.
I think I'm going insane.
Thanks

If you think you're experiencing an episode of insanity, you
should seek out professional help immediately.
This forum is only intended for user-to-user support for
Adobe Captivate and is not intended to provide medical advice or
treatment.
Just kidding... welcome to the Captivate community!
It's very odd that the semi-colon is causing a problem. It's
a standard mechanism in e-mail, used primarily to separate names
when an e-mail is addressed to more than one person. Are you sure
the error you're seeing is not due to you having entered an invalid
e-mail address in Captivate, possibly due to a typo?
In testing, I didn't see a semi-colon in the value being
passed to the e-mail program so I suspect the semi-colon is being
added by the browser and/or the e-mail client itself. There may not
be any way to prevent it.
That said, if you only send the e-mail to a single recipient
and you're SURE you don't want the semi-colon, use the code at the
bottom of this post to ensure that the outgoing value doesn't
contain a semi-colon. I doubt it will do anything, but it can't
hurt to try.
If you still see a semi-colon afterwards, it's definitely
being added after the e-mail submission process is being kicked
off.

Semi-colon in URL from WebLogic 7.0

Similar Messages

Maybe you are looking for