Registering a servlet

Hi,
I'm creating a simple shared-files-type provider - a place where users can upload files to and download files form. The question is about getting (viewing) a file from the web.
Probably I need to register my custom servlet to do the job. Then it could access the local file system, read the file, and send it via HttpServletResponse using appropriate content-type header. So the question is: how to register a servlet, where to put .class, and where is the web.xml?
Maybe there is another approach to accomplish this?
Please let me know.
Much of thanks,
Denis

Hi,
You can also find some useful information in DSAME
docs (see registering new services)
A different approach would be:
Create a worker Java Bean and a FrontEnd jsp.
By deriving your jsp from JSPProvider you will
have access to all portal goodies(e.g. parameters)
and you can pass them to your Java Bean.
(See JSPSampleChannel jsp code for more details)
The benefit: Easy portable on any version of any portal.
Cheers,
Alex :-)

Similar Messages

How do you register/define servlet to be used in tomcat?

How do u register/define servlet to be used in tomcat?

specify servler mapping in web.xml
<servlet>
    <servlet-name>xxxxx</servlet-name>
   <servlet-class>com.eplus.xxxx.server.ViewUserServlet</servlet-class>
</servlet>
<servlet-mapping>
      <servlet-name>xxxx</servlet-name>
      <url-pattern>/xxxx</url-pattern>
</servlet-mapping>sudhir
http://www.jyog.com

How do you register a servlet on 8i?

I am so new at this. How do you go about registering a servlet
on 8i? We have iFS 1.1 running on a Linux box with Oracle 8i.
In the 9iFS developer's guide there are instructions on how to
register a servlet. They don't work for 8i and I can't find any
instructions for registering servlets for 8i.
Thanks for the help.

If you are using Java Web Server in Oracle8i, this technical
brief describe how to register a servlet.
http://otn.oracle.com/sample_code/products/ifs/htdocs/xsl/index.h
tm
See the section Configure the Java Web Server to Run the Servlet.
Apache will have a different way of registration.

Registering Servlet on JDeveloper

Good morning,
I4d like to know if there is some bug about registering servlet on JDeveloper version 3.2.3 - Build 1018. I try to use the Web Object Manager to register a servlet but only one servlet got registered and I register more than one. My environment is composed by:
JSP(in) ---> Servlet1 ---> Servlet2 ---> JSP(out)
I registered both servlets(1 and 2) on Web Object Manager
On the first stage where the JPS(in) calls Servlet1 its ok, but when the servlet1 try to calls servlet2, its the problem. JDeveloper doesn4t recognize the second servlet and it4s registered.
I hope for help and thanks
Sandro Brandco

You should switch to using Jdeveloper 9i RC and register your servlets using the web.xml file that is created for your project.

Registering servlets with JDeveloper

Hi! I'm new at using JDeveloper (3.2.2). I'm having some
problems on registering servlets using the Web Object Manager. I
tried following the instructions given on the JDeveloper help. I
was able to register 4 servlets but only one can be accessed.
The other servlets post a Web2Go 'unable to find url' error of
some sort. Could somebody help me?
Mildred :)

You should switch to using Jdeveloper 9i RC and register your servlets using the web.xml file that is created for your project.

Registering a partner application with SSO SDK

Good day
Since 2 days, I am struggling for the issue of registering a Servlet application as a partner
application using the SSO Login Server.
As per the suggested note id 182701.1 in metalink , I implement the following steps :
- Step A : Create the partner Application Schemas (Succesful & the name of the shemas is : ssopartner)
- Step B : Load Packages for the partner application (Successful)
- Step C : Obtain the registration information (Successful)
- Step D : Run the regapp.sql (successful but they forgot to mention that I should load the
SSOHash.class )
- Step E : Compile and Run
I deploy the application under 9iAS in order to test it.
I add the ssosdk307.jar the the jserv.properties file.
I invoke the SSOPartnerServlet java program by entering :
http://name of the webserver/servlet/SSOPartnerServlet
I got the message "redirecting to the login server" and I got the
login page of the SSO Server.
Once I submit the user/password , I got HTTP 400: Page cannot be
displayed.
I check the mod_jserv.log file and find out the following message :
[08/04/2002 13:54:16:949] (ERROR) ajp12: Servlet Error: POST is not
supported by this URL
Could you please advise
Your prompt feedback is highly appreciated
regards

I believe that this is not possible as the mod_osso realizes that the URL is below an URL that you want to protect.
The only way I see that you can do this is the following modification in the mod_osso.conf:
<Location /myApp/secure_partA>
AuthType basic
Require valid-user
</Location>
<Location /myApp/secure_partB>
AuthType basic
Require valid-user
</Location>
<Location /myApp/secure_partX>
AuthType basic
Require valid-user
</Location>
So your application /myApp/subApp will not be effected and people can just access this part. However you will have more administration in your mod_osso.conf
cu
Andreas

Error 404 -- Not Found, when a Servlet is invoked from browser

Obviously, I have not been able to configure my WebLogic Server 5.1.0 to run
          even the simplest servlet.
          I painstakenly went through all the steps that are listed in the WebLogic
          Server 5.1.0 documentation on the Web to enable servlets, but obviously, I
          have missed a step somewhere.
          I have modified the weblogic.properties file as per all the instrustions,
          but the server simply won't recognize any servlets, not even the SqlServlet
          that came with the server as an example.
          It would require more than 1 exchange of posts to resolve it for me, and I
          am wondering if one of you is willing to work with me on this until I have
          managed to configure the server to make a servlet work on it.
          The server does function as a Web server as I can run the index.html
          document by entering the URL: http://localhost:7001/index.html
          I am pasting the contents of weblogic.properties file below to get the
          person who is willing to help me started.
          The machine I have is a Pentium III with Windows 2000 Professional on it.
          It's a home machine and the WebLogic server is the freely downloadable
          version. I am using it to prepare for a potential contract work.
          I have managed to modify setEnv.cmd file and have managed to compile the
          SqlServlet.java, which is an example servlet. Neither this particular
          servlet nor a HelloWorld type of very basic servlet I have written are
          recognized by the server.
          As you can see from my weblogic.properties file (pasted at the end of this
          post), the SqlServlet has been registered. I have also uncommented the lines
          to allow for the following type of URL:
          http://localhost:7001/servlet/myServlet
          Thanks!
          Anjum Jaleel
          CONTENTS OF MY weblogic.properties file
          # THE WEBLOGIC PROPERTIES FILE
          # This file, which conforms to the java.util.Properties file
          # definition, configures your WebLogic products. You cannot run
          # WebLogic Server without setting required configuration properties in this
          # file. Required properties are marked and appear first in the file.
          # Details on each entry and important information about configuration
          # and security are documented on our website. Please go to:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # for full instructions on how to edit this file.
          # You do not need to include properties in this file unless you want to
          # change the default, embedded property. Some properties on the
          # AdminProps page are not listed here because the default property
          # is being used. You can change the default by adding the property and
          # its value to this file.
          # You cannot set weblogic.system.home in this file, since the WebLogic
          Server
          # must know where home is in order to retrieve this file. You can
          # change WebLogic home on the command line when you start the
          # WebLogic Server.
          # CLUSTER USERS: Note that the (shared) per-cluster properties file should
          # contain most all of the properties in this file. The only properties
          # that potentially belong in a per-server properties file for a server
          # running in a cluster are the registration (startup class) of pinned
          # RMI objects, and a few tuning properties that may be different for
          # servers in the cluster, depending upon hardware and memory. If you use
          # a per-server properties file, please REMOVE all properties except those
          # that are specifically required in the per-server properties file. You
          # can find specific notes on clusters by searching through this file for
          # "CLUSTER USERS".
          # The way this file is organized:
          # Core properties (includes REQUIRED and RECOMMENDED)
          # Core system properties
          # Core security-related properties
          # Core security-related properties for SSL
          # Core HTTPD administrative properties
          # Optional properties
          # Administrator properties
          # System properties
          # System startup files
          # System shutdown files
          # Security-related properties for Workspaces
          # Jolt for WebLogic properties
          # WebLogic Enterprise Connectivity properties
          # WebLogic File properties
          # WebLogic JMS demo properties
          # WebLogic RMI demo properties
          # WebLogic EJB demo properties
          # WebLogic XML demo properties
          # WebLogic ZAC demo properties
          # HTTPD administrative properties
          # WebLogic JDBC driver properties
          # WebLogic JDBC connection pool management
          # WebLogic demo connection pool
          # WebLogic HTTP Servlet properties
          # Proxy servlet registration
          # Classpath servlet registration
          # File servlet registration
          # ServerSideInclude servlet registration
          # PageCompileServlet (used by JHTML)
          # JSPServlet (used by JSP)
          # ServletServlet registration
          # Servlet reload properties
          # Servlet ACLs
          # WebLogic JSP properties
          # WebLogic JHTML properties
          # WebLogic RMI over IIOP properties
          # User-written and demo servlet registrations
          # CORE PROPERTIES
          # You should set these before you start the WebLogic Server the first time.
          # If you need more instructions on individual properties in this
          # section, check the same section in the Optional Properties, where
          # we've left the long explanations. Or, better yet, go to our
          # website and read all about properties, at:
          # http://www.weblogic.com/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=lovkako1
          # 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=true
          # If authentication is required, add username/password for each user
          # who will be included in an ACL, as in this commented-out example:
          #weblogic.password.peter=#8gjsL4*
          # OPTIONAL PROPERTIES
          # These properties affect the behavior of the WebLogic Server.
          # You only need to set these properties if you want
          # to change the default setting, which is the property shown.
          # ADMINISTRATOR PROPERTIES
          # Administrator properties are optional information properties,
          # particularly useful for clusters.
          #weblogic.administrator.location=3355 California Drive, West Hampshire, CA
          94104
          #weblogic.administrator.name=Joe Administrator
          #weblogic.administrator.phone=1 415 555 1234
          # SYSTEM PROPERTIES
          # System properties in this section are set to system defaults
          # Performance pack. The shared library must be accessible from your
          # PATH (NT) or from your shared library path (UNIX; the name of the
          # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
          weblogic.system.nativeIO.enable=true
          # Outputs logging information to the console as well as to the log file
          weblogic.system.enableConsole=true
          # Sets the directory or URL for the WebLogic Admin help pages
          # The help pages are shipped in the "docs/adminhelp" directory, in the
          # default document root in public_html
          weblogic.system.helpPageURL=g:/weblogic/myserver/public_html/docs51/adminhel
          p/
          # 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:
          #weblogic.ejb.deploy=\
          # g:/weblogic/myserver/ejb_basic_beanManaged.jar, \
          # g:/weblogic/myserver/ejb_basic_containerManaged.jar, \
          # g:/weblogic/myserver/ejb_basic_statefulSession.jar, \
          # g:/weblogic/myserver/ejb_basic_statelessSession.jar, \
          # g:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
          # g:/weblogic/myserver/ejb_extensions_readMostly.jar, \
          # g:/weblogic/myserver/ejb_subclass.jar, \
          # g:/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=g:/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=\
          # guest,joe,jill
          #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
          # joe,jill
          #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\

Problem Resolved!
          I found out that I had 'http' instead of 'httpd' in the statement where I
          registered my servlet, SqlServlet.
          Now, I am having difficulty with hot deployment. The server is returning
          error 404.

Servlet reloading not working with WLS 5.1 sp8

          I downloaded and installed WLS 5.1's sp8 to fix the "java.net.SocketException: Connection aborted by peer: socket write error"
          problem. Although that problem is fixed, I have found that, however, the servlet (automatic) reloading does not
          work anymore. If I remove the sp8 from my Java system classpath and WL classpath (i.e. not using sp8), then
          the servler reloading works fine.
          Does anybody experience similar problem or have I forgot to do something?
          WLS properties/env vars setting:
          - weblogic.httpd.servlet.reloadCheckSecs=0
          - WEBLOGIC_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8.jar;...
          - JAVA_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8boot.jar;...
          Thanks in advance for any help.


          I've experienced the same problem with both sp6 and sp8. In both cases I performed several test, including
          - varied the value of weblogic.httpd.servlet.reloadCheckSecs
          - changes to the package depth the servlet belonged to
          - changes to the string length of the package names the servlet belonged to
          At best, the servlet would reload sometimes. I've moved back to sp5 and the problem has subsided.
          Note: I did not try registering the servlet to see how that would effect the dynamic reloading.
          Hope this helps
          - Dave
          "Michel Dinh" <[email protected]> wrote:
          >
          >I downloaded and installed WLS 5.1's sp8 to fix the "java.net.SocketException: Connection aborted by peer: socket write error"
          >problem. Although that problem is fixed, I have found that, however, the servlet (automatic) reloading does not
          >work anymore. If I remove the sp8 from my Java system classpath and WL classpath (i.e. not using sp8), then
          >the servler reloading works fine.
          >
          >
          >Does anybody experience similar problem or have I forgot to do something?
          >
          >WLS properties/env vars setting:
          >
          >- weblogic.httpd.servlet.reloadCheckSecs=0
          >- WEBLOGIC_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8.jar;...
          >- JAVA_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8boot.jar;...
          >
          >Thanks in advance for any help.

Starting Servlet at Server Startup

Hi all!
          We are desperately trying to initialize a servlet at weblogic 5.1
          startup.
          When simply registering the servlet it works well.
          Now we tried to set up autostart for the servlet according to the docs
          at http://www.weblogic.com/docs51/classdocs/API_servlet.html#128566:
          <doc>
          # Here we register the myservletclass servlet class
          weblogic.httpd.register.MyServlet=\
          examples.servlets.myservletclass
          # Configure the ServletStartup class to run MyServlet's init()
          # method at startup
          weblogic.system.startupClass.StartMyServlet=\
          weblogic.servlet.utils.ServletStartup
          weblogic.system.startupArgs.StartMyServlet=\
          servlet=MyServlet
          </doc>
          We register our servlet with alias "stest":
          weblogic.httpd.register.stest=our.servlet
          This works well.
          Then we add the startup info:
          weblogic.system.startupClass.Startstest=\
          weblogic.servlet.utils.ServletStartup
          weblogic.system.startupArgs.Startstest=\
          servlet=stest
          But when starting weblogic it says:
          <I> <WebLogicServer> T3StartupDef stest
          weblogic.servlet.utils.ServletStartup reports:servlet: stest
          not found
          What is going wrong here?
          Thanks!


Here is mine...
I do have it load at login so it is different but I do NOT have it running as root, include other environmental variables you do not..
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>KeepAlive</key>
<true/>
<key>Label</key>
<string>com.compute.FetchMail</string>
<key>ProgramArguments</key>
<array>
<string>/usr/bin/fetchmail</string>
<string>--nodetach</string>
<string>--timeout</string>
<string>60</string>
<string>--fetchall</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>UserName</key>
<string>admin</string>
<key>WorkingDirectory</key>
<string>/Users/admin</string>
<key>EnvironmentVariables</key>
<dict>
<key>home</key>
<string>/Users/admin</string>
</dict>
</dict>
</plist>

Servlet hot deployment with a webApp

Hi everybody,
Does anybody know something about hot deployment of servlets in a web
application (.war) ?
I tried many things (setting reloadCheckSecs in properties, in web.xml,
hot-deploy from console...) but nothing really worked.
So I have to register a servlet for hot deployment in the properties, but
then it doesn't belong to the application.
Thanx,
Markus.

I presume you are on 51.
we do not support hot deployment of webapps in 51. We support this in 6.0
Kumar
"M. Hammer" wrote:
Hi everybody,
Does anybody know something about hot deployment of servlets in a web
application (.war) ?
I tried many things (setting reloadCheckSecs in properties, in web.xml,
hot-deploy from console...) but nothing really worked.
So I have to register a servlet for hot deployment in the properties, but
then it doesn't belong to the application.
Thanx,
Markus.

Servlet Hot-Deploy with a WebApp

Hi everybody,
Does anybody know something about hot deployment of servlets in a web
application (.war) ?
I tried many things (setting reloadCheckSecs in properties, in web.xml,
hot-deploy from console...) but nothing really worked.
So I have to register a servlet for hot deployment in the properties, but
then it doesn't belong to the application.
Thanx,
Markus.

Are u saying that WARs are redeployed automatically but not individual servlets,
or neither?
Thanks.
Viresh Garg wrote:
Currently the automatic hot deployment of a servlet/JSP from exploaded WAR is
broken. We are in the process of fixing it for next release. You have to
redeploy your web application right now, for the change to take place.
Viresh Garg
Principal Developer Relations Engineer
BEA Systems
"M. Hammer" wrote:
Hi everybody,
Does anybody know something about hot deployment of servlets in a web
application (.war) ?
I tried many things (setting reloadCheckSecs in properties, in web.xml,
hot-deploy from console...) but nothing really worked.
So I have to register a servlet for hot deployment in the properties, but
then it doesn't belong to the application.
Thanx,
Markus.

Servlet not reachable by name in WebToGo

Every time I launch a servlet from the debugger, it comes up with a url of http://<myserver>/servlets/servlet. The servlet becomes unreachable by name. This makes the servlet unreachable by other pages and servlets when debugging.
I think this is occurs because everytime I launch a file for debugging, the file %JDEV_HOME%/myhtml/WebAppRunner.html runs first. In this file is a command to direct to the url described above.
What changes do I need to make to reach a servlet by name?

See the following topic in the JDeveloper online help:
User Guides
Developing Applications
Developing Web Applications
Developing Java Servlets
Registering a Servlet
You register your servlets with the Web-to-Go server via the Web Object Manager (available from the Wizards menu), by providing a path and classname for each servlet you want to run or debug in JDeveloper.
This allows you to call one servlet from the other by the name and path you register.
The servlets/servlet name is the 'default' used if the servlet is unregistered.
This was all new to me, so thanks for helping me learn something new about the product!

Problem accessing Servlet in Weblogic 6.0

          Using the console I verified that the servlet is available on examplesWebApp. When I try to access it as http:127.0.0.1:localhost/examplesWebApp/myServlet, I get the following error:
          Error 404--Not Found
          From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
          10.4.5 404 Not Found
          The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
          If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
          Does anyone have any suggestions.
          Thanks


From your servlet-class declaration, it seems that your servlet should be in
          (WEB-INF\)classes\examples\servlets, not (WEB-INF\)classes\servlets.
          "Varughese John" <[email protected]> wrote in message
          news:[email protected]...
          >
          > The directory structure is as follows
          > wlserver6.0\config\examples\applications\examplesWebApp\Web-inf\
          >
          > The contents of the web.xml is:
          > <servlet>
          > <servlet-name>myServlet</servlet-name>
          > <servlet-class>examples.servlets.myServlet</servlet- class>
          > </servlet>
          > <servlet-mapping>
          > <servlet-name>myServlet</servlet-name>
          > <url-pattern>/myServlet/*</url-pattern>
          > </servlet-mapping>
          >
          > myServlet.class is placed in the classes\servlets directory.
          >
          > I still get the following error:
          > Error 404--Not Found
          > From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
          > 10.4.5 404 Not Found
          > The server has not found anything matching the Request-URI. No indication
          is given of whether the condition is temporary or permanent.
          >
          > If the server does not wish to make this information available to the
          client, the status code 403 (Forbidden) can be used instead. The 410 (Gone)
          status code SHOULD be used if the server knows, through some internally
          configurable mechanism, that an old resource is permanently unavailable and
          has no forwarding address.
          >
          > Shold I manipulate the properties of the Internet Explorer.
          >
          > Thanks for the help.
          >
          >
          > Dana Jeffries <[email protected]> wrote:
          > >in the web.xml file you should have a component entry for the servlet
          class and a mapping entry.
          > >
          > >the servlet has to be in the correct package below WEB-INF/classes
          > >
          > >Varughese John wrote:
          > >
          > >> I need to update the url that I mentioned in the previous thread. I
          meant http:127.0.0.1:7001/examplesWebApp/myServlet.
          > >> I had used the deployment descriptor to register the servlet.
          > >> The error mentioned in the previos thread remains.
          > >> Thanks in advance for the help.
          > >>
          > >> "Varughese John" <[email protected]> wrote:
          > >> >
          > >> >Using the console I verified that the servlet is available on
          examplesWebApp. When I try to access it as
          http:127.0.0.1:localhost/examplesWebApp/myServlet, I get the following
          error:
          > >> >
          > >> >Error 404--Not Found
          > >> >From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
          > >> >10.4.5 404 Not Found
          > >> >The server has not found anything matching the Request-URI. No
          indication is given of whether the condition is temporary or permanent.
          > >> >
          > >> >If the server does not wish to make this information available to the
          client, the status code 403 (Forbidden) can be used instead. The 410 (Gone)
          status code SHOULD be used if the server knows, through some internally
          configurable mechanism, that an old resource is permanently unavailable and
          has no forwarding address.
          > >> >
          > >> >Does anyone have any suggestions.
          > >> >
          > >> >Thanks
          > >> >
          > >> >
          > >
          >

Servlet/JSP problems with WL 4.51

Hi all
          I have a set of Servlets and JSPs running on NewAtlanta's ServletExec
          servlet engine. I am currently porting them to WebLogic. I am facing a
          few problems. I do not want to change any of my HTML/JSP/Java files
          immediately. I want the same files to work in WL as it is. Pl help.
          1. The servlets in ServletExec used to be invoked as
          http://host/servlet/servletName. But in weblogic they are invoked
          as http://host/servletName. I tried registering the servlet names
          in weblogic.properties as
          weblogic.httpd.register.servlet/XServlet=com.foo.XServlet
          weblogic.httpd.initArgs.servlet/XServlet=param=value
          Now I can call this servlet as http://host/servlet/XServlet and so
          I dont have to change any html/JSP files. Will this cause any
          problems in the future?
          2. Since we used to run ServletExec on IIS, we created a virtual
          directory called /jsp in IIS under which we had all the html and
          JSP files. Our servlets will get the http requests, get data from
          database, put the results in session/request variables and dispatch
          it to appropriate JSP page. So, all our servlet code looks like
          this:
          RequestDispatcher dispatcher =
          getServletContext().getRequestDispatcher("/jsp/test.jsp");
          dispatcher.forward(request, response);
          How do I make this code work with WebLogic? Is there any way to
          create virtual directory and make it work like in IIS?
          Thanks for any help.
          shiv
          [email protected]


You might try
          weblogic.httpd.register.jsp/*.jsp=weblogic.servlet.JSPServlet
          but a better/ easier way would be to just move all of your jsp files to a 'jsp'
          subdirectory beneath public_html
          -rrc
          Shiv Kumar wrote:
          > Hi all
          >
          > I have a set of Servlets and JSPs running on NewAtlanta's ServletExec
          > servlet engine. I am currently porting them to WebLogic. I am facing a
          > few problems. I do not want to change any of my HTML/JSP/Java files
          > immediately. I want the same files to work in WL as it is. Pl help.
          >
          > 1. The servlets in ServletExec used to be invoked as
          > http://host/servlet/servletName. But in weblogic they are invoked
          > as http://host/servletName. I tried registering the servlet names
          > in weblogic.properties as
          >
          > weblogic.httpd.register.servlet/XServlet=com.foo.XServlet
          > weblogic.httpd.initArgs.servlet/XServlet=param=value
          >
          > Now I can call this servlet as http://host/servlet/XServlet and so
          > I dont have to change any html/JSP files. Will this cause any
          > problems in the future?
          >
          > 2. Since we used to run ServletExec on IIS, we created a virtual
          > directory called /jsp in IIS under which we had all the html and
          > JSP files. Our servlets will get the http requests, get data from
          > database, put the results in session/request variables and dispatch
          > it to appropriate JSP page. So, all our servlet code looks like
          > this:
          >
          > RequestDispatcher dispatcher =
          > getServletContext().getRequestDispatcher("/jsp/test.jsp");
          > dispatcher.forward(request, response);
          >
          > How do I make this code work with WebLogic? Is there any way to
          > create virtual directory and make it work like in IIS?
          >
          > Thanks for any help.
          > --
          > shiv
          > [email protected]
          Russell Castagnaro
          Chief Mentor
          SyncTank Solutions
          http://www.synctank.com
          Earth is the cradle of mankind; one does not remain in the cradle forever
          -Tsiolkovsky

Servlet as a welcome file: is it a myth?

Hello
There are many articles on the web that espouse that Servets 2.4 allow for a servlet to be specified as a welcome file thusly (taken from OnJava.com):
First, register the servlet in web.xml.
<?xml version="1.0" encoding="ISO-8859-1"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi=
"http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=
"http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4">
<servlet>
<servlet-name>MyServlet</servlet-name.
<servlet-class>com.jspservletcookbook.MyServlet</servlet-class>
</servlet>

<servlet-mapping>
<servlet-name>MyServlet</servlet-name>
<url-pattern>/myservlet</url-pattern>
</servlet-mapping>

Then create a welcome-file element in web.xml that specifies the registered servlet name.
<welcome-file-list>
<welcome-file>MyServlet</welcome-file>
<welcome-file>default.jsp</welcome-file>
</welcome-file-list>
Make sure to use the servlet name in the welcome-file element without a forward slash (/) preceding it.
Poppycock I say. At least it's not working for me with either Tomcat 5 or Tomcat 5.5. Has anyone out there ever seen this work on Tomcat?

It most certainly is possible now, but wasn't until rather late in TC 5.0.xx series I believe (5.0.18 or so?). You can chack the change logs to id exactly when...
But the reason it isn't working for you is you have to match the value in your <welcome-file> to the URL in the servlet's <url-pattern> servlet mapping. So your web XML should look like this:
<servlet>
<servlet-name>MyServlet</servlet-name.
<servlet-class>com.jspservletcookbook.MyServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>MyServlet</servlet-name>
<url-pattern>/myservlet</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>myservlet</welcome-file>
<welcome-file>default.jsp</welcome-file>
</welcome-file-list>Your porblem was case. Your url-pattern had lower case, but the welcome-file had upper case letters like the servlet name.
Here is an example app that I tested and worked:
//The servlet:
package net.thelukes.steven;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class WelcomeServlet extends HttpServlet {
     public void doGet(HttpServletRequest request, HttpServletResponse response)
       throws ServletException, IOException {
          PrintWriter out = response.getWriter();
          out.println("Hello World");
          out.flush();
          out.close();
//the web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4"
         xmlns="http://java.sun.com/xml/ns/j2ee"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
                             http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
     <display-name>WTPTest</display-name>
     <servlet>
          <servlet-name>Welcome</servlet-name>
          <servlet-class>net.thelukes.steven.WelcomeServlet</servlet-class>
     </servlet>
     <servlet-mapping>
          <servlet-name>Welcome</servlet-name>
          <url-pattern>/welcome</url-pattern>
     </servlet-mapping>
     <welcome-file-list>
          <welcome-file>welcome</welcome-file>
     </welcome-file-list>
</web-app>
//The address I typed (the web app is names WTPTest
http://localhost:8080/WTPTest
//The HTML Output
Hello World

Registering a servlet

Similar Messages

Maybe you are looking for