Servlet engine invoked FROM CGI script?

Yes this is a backwards request, but I need a simple servlet engine that can be invoked through a CGI script. I perfectly realize the problems associated with this like session management, benefits in threading, etc not to mention the overhead of JVM startup on each request...
Anything with which anyone's familiar? Searching returns (of course) how to invoke CGI from Servlet containers which is obviously not what I need.
Thanks!

Hi Michael,
I am running 7.0 on Win NT while its the same case its displaying the whole content
as it is setted the weblogic.servlet.CGIServlet in the web.xml file and providing
the compiler for perl also .
Looking for a quick reply
Thanks
Shivani
Michael Young <[email protected]> wrote:
Hi.
What platform/OS version are you running WLS on?
Thanks,
Michael
Suren Jain wrote:
Hi,
We are having problems invoking cgi scripts from the browser.
When we try to access it, it is not executed, instead the script is displayed
in the browser.
We are using weblogic 5.1 and sp9.
In the properties file we have specified
weblogic.httpd.register.cgi-bin=weblogic.servlet.CGIServlet
weblogic.httpd.initArgs.cgi-bin=\
cgiDir=/opt/equitydev/geo/cgi-bin,\
*.pl=/usr/local/bin/perl5,\
*.sh=/bin/ksh
Appreciate your help.
Thanks
Suren.--
Michael Young
Developer Relations Engineer
BEA Support

Similar Messages

  • How to invoke from UNIX script and pass back return code?

    Though I am an experienced developer, I am new to java. I created a class containing a single method. I have performed my testing by running the class class.method from the command line in a UNIX (Solaris) environment. Now, I would like to have the class.method invoked from a UNIX shell script, and to return a success/failure indicator from the method, to the UNIX script. I modified the method to make it return char, rather than being defined as void. Within the class and method, I declared and initialized a char variable. I added a finally clause which contains a single return statement, returning the char return code variable. Within my UNIX script, I invoke the class/method as follows:
    return_code = java myClass
    This does not seem to be invoking the method however. Can someone please tell me what I am doing wrong? Or is more information needed in order for someone to help me out.
    Please let me know.
    Thanks.
    Brad

    stdunbar,
    Using your suggestion of System.exit(retVal); seems to allow the java method to be performed successfully (Thank You). But I am still having a problem with the value being recognized by the shell script.
    In my script, I'm doing the following:
    java MyClass inputparameter > return_code
    export return_code
    echo $return_code
    But return_code does not seem to contain a value. Just before the System.exit(retVal); I added System.out.println("return code = " + retVal ); and I can see that retVal. When I run the java method outside of the UNIX shell script, I can see that retVal does indeed contain a value. So I think my problem might actually be the code in the UNIX script.
    Thanks again.
    Brad

  • Multiple form recipients from CGI script

    Is there any way to code a cgi script to deliver the form to
    more than one recipient. I've tried a couple of things and can't
    seem to make anything work.

    So the mail server you are sending through does address verification.
    Maybe you should explain to them that it is a pointless exercise, as many mail servers on the internet will not allow verification. Thus, you will reject legit mail.
    I don't know if your CGI script can be modified as I have never seen it and am no psychic
    You can create a www user and set the shell to none. The user must be allowed to login, just don't give it a shell.
    Alternatively, check if your script will allow for authenticated SMTP and ask your sysadmin to allow you through when authenticated.

  • Invoking from shell script causes NoClassDefFoundError

    Hi, I have a reasonably simple class that I built, that runs perfectly fine when invoked like:
    java myClass params
    I need it to be invoked through a bash shell script however, so I wrote a real simple one of those, that is kept in the same directory and the .class build of my program.
    The bash script calls the class in the same way.
    Now, here's the odd part. When invoked directly from the directory (ie, both are kept in /xyz)
    pwd: xyz
    invoke_myclass.sh params
    The above works with no problem.
    In fact the following works too:
    pwd: xyz
    /xyz/invoke_myclass.sh params
    However, if I'm anywhere else this does not work!
    ex:
    pwd: abc
    /xyz/invoke_myclass.sh params -> Exception in thread "main" java.lang.NoClassDefFoundError: /xyz/myclass.sh
    What gives? The script is executing (it does a few other things that are working perfectly fine). This is driving me up the wall! Does anyone have any idea of what could be going on here?
    Thanks so much.
    -Jesse

    You didn't set the CLASSPATH, did you?
    In your shell script, you have this, right:
    java myClass params
    Try adding a -classpath argument:
    java -classpath /xyz myClass params

  • 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.
              

  • Oracle Servlet Engine!

    Hi,
    I'm just successful installed 9idb and 9iFS in w2k server. But I decided to change the Oracle Servlet Engine page from port 8080 to 8081. (the page Oracle Servlet Engine with the flying pig. Anyone has ides how to do this?
    Thanks
    Ken

    Anyone has idea???

  • Error running HAL routine from a perl cgi script via a browser

    Hi,
    I'm getting an error while trying to run a HAL routine from a perl- cgi initiated from a web browser. Perl-Cgi script runs fine when run from command line.
    07/23/2010|183648|N/A|Info|N/A|Analytic Services Adapter Log File Started
    07/23/2010|183648|AppName/Plan2|Info|Connect|Method Started
    07/23/2010|183648|AppName/Plan2*|Error|Connect|java.lang.UnsatisfiedLinkError: no HssJNIDriver950 in java.library.path*
    07/23/2010|183648|AppName/Plan2|Error|Connect|Method Ended - Connect completed with exceptions.
    07/23/2010|183648|N/A|Info|N/A|Analytic Services Adapter Log File Ended
    I've added the following env. variables in Apache server's httpd.conf file
    SetEnv ARBORPATH "E:\\Hyperion\\products\\Essbase\\EssbaseClient"
    SetEnv APS_HOME "E:\\Hyperion\\products\\Essbase\\aps"
    SetEnv ESSLANG "English_UnitedStates.Latin1@Binary"
    SetEnv EASPATH "E:\\Hyperion\\products\\Essbase\\eas\\server"
    SetEnv HYPERION_HOME "E:\\Hyperion"
    SetEnv ESSBASEPATH "E:\\Hyperion\\products\\Essbase\\EssbaseClient"
    SetEnv EAS_HOME "E:\Hyperion\products\Essbase\eas\console"
    SetEnv CLASSPATH "E:\\Vignette\\V7\\vbis\\Hyperion\\EssbaseAdapter"
    SetEnv PATH "E:\\Hyperion\\common\\ADM\\9.5.0.0\\Essbase\\9.5.0.0\\bin;E:\\Vignette\\V7\\vbis\\Hyperion\\EssbaseAdapter\\adm;C:\\Program Files (x86)\\Java\\jre1.5.0_17\\bin\\;E:\\Hyperion\\products\\Essbase\\EssbaseClient\\bin;E:\\Hyperion\\products\\Essbase\\EssbaseClient;E:\\Hyperion\\common\\CSS\\9.5.0.0\\bin;E:\\Hyperion\\products\\Essbase\\eas\\console\\bin;"
    Any pointers would be appreciated.
    Thanks in Advance!!

    Vipul,
    Vipul Sanghvi wrote:
    I am facing problem in running a Perl CGI Script on Weblogic
    Application
    Server
    I set the CGIServlet Property in the Weblogic Properties file as
    weblogic.httpd.register.cgi-bin=weblogic.servlet.CGIServlet
    weblogic.httpd.initArgs.cgi-bin=\
    cgiDir=/weblogic/myserver/public_html/cgi-bin,\
    *.pl=/bin/perl.exe,\It shouldn't end with ,\ right?
    Was it a mistake?
    -Kumar
    >
    I installed the Perl on my system and put the perl exe in the bin
    directory
    of the Weblogic App Server. But I am getting the error "failed to
    execute
    the test.pl ". Where test.pl is a simple test perl script.
    APP server ver is WLE5 Beta[att1.html]

  • Are servlets like cgi scripts?

    hi all,
    are servlets like cgi scripts?
    or
    they should be embedded within the html file,
    thank you very much
    :)

    Yes, Servlets are very similar to CGI scripts -- they both run on the server and grab input from the HTTP GET or POST request, then send generated HTML back to the client browser.
    Often Servlets are described as being superior to CGI scripts because each time a CGI script is run a new process must be created. However, you can run Perl CGI scripts without starting a new process (using mod_perl, for example), and therefore that claim is unfounded.

  • How can i call a CGI script from java?

    The subject pretty much says it all. I want to call a perl cgi script so i can read from/write to files on a server. I don't know how to sign applets and this would be the easiest way for me, if someone could please tell me.

    Let me get this clear. Basically what u want to do is to just call a URL, right?
    U can do it by using the following code:
    import java.applet.*;
    import java.net.*;
    import java.io.*;
    public class testhttp
    public static void main(String[] args)
    try
    URL url = new URL ("http://../testcgi.cfm");
    HttpURLConnection cxn =
    (HttpURLConnection)url.openConnection();
    cxn.setRequestMethod("POST");
    cxn.setUseCaches(false);
    cxn.setDoOutput(true);
    cxn.setDoInput(true);
    ByteArrayOutputStream bytes = new
    ByteArrayOutputStream(400);
    PrintWriter writer = new PrintWriter (bytes,true);
    writer.print("application=map&release=1&items=prog1");
    writer.flush();
    cxn.setRequestProperty("Content-
    Length",String.valueOf(bytes.size()));
    cxn.setRequestProperty("Content-
    Type","application/x-www-form-urlencoded");
    bytes.writeTo(cxn.getOutputStream());
    System.out.println(bytes);
    String currentLine;
    BufferedReader in = new BufferedReader (new
    InputStreamReader(cxn.getInputStream(),"8859_1"));
    while((currentLine = in.readLine()) != null) {
    System.out.println(currentLine); }
    catch(Exception e) { e.printStackTrace(); }
    There is also a library called HTTP client which can be found at:
    http://www.innovation.ch/java/HTTPClient/index.html
    It's very simple to use and the documentation is all there, but their web server seems to be down right now.
    Anyway, hope my post helps.

  • How do I control data transfer rate from Java applications to CGI scripts?

    Hi. I've written a test cgi script which echoes any data it's sent back to the client, and I'm trying to write a java application that reads data from files on my hard drive and sends it to the cgi application.
    The method I've used is the same as the one described in the tutorial on this site, ie. create an URL object, open an URLConnection, get output stream from URLConnection, write data to output stream.
    The problem however is that the java application writes to the output stream at a much faster rate than my internet connection can handle, and so when I try to send more than a few kb the data doesn't seem to get sent at all. Is there some way I can control the rate at which data is sent, or is there a better way of sending data to a cgi application?
    I'd really appreciate any help, thanks!
    Ose.

    I've done some experimenting, and it seems that the problem is with my CGI application and not the Java application after all! (sigh) I wish I hadn't spent those duke dollars now. Oh well.

  • How can I get a parameter back into a servlet invoked from an IMG tag ?

    I'm using a servlet to create several graphical plots per JSP i.e. per HTML page. Each graph is supposed to be different, according to a parameter which I want to pass back from my JSP. I'm getting several plots but they're all the same!
    I've tried setting an attribute in the session object before each IMG SRC= , but all I get is each plot the same! In fact, my debugging efforts show that the servlet is only called once despite 3 calls, each with a different session parameter value. I'm not sure the session parameter values are getting used properly.
    I just can't find a way of getting a parameter back into my servlet which is invoked from the IMG tag (i.e. SRC= "servlet name").
    Can anyone tell me the best way to pass a parameter back into a servlet which is invoked from an IMG tag? Can the request object be used? I can't, at the moment, see how it could be used?
    I'll certainly be very grateful if anyone can help with this - could even be useful for others as well!

    You said that, "by moving a copy of Mobile Docs back to the Library, from which I had moved it, my documents reapperared in Cloud." That says that you actually moved it. Obviously, I can't tell exactly what you did, but it sounds like you may have thought you were just putting it in the sidebar, but you actually put it somewhere else. The sidebar is not a location to put things, just a way to create a quick shortcut to access a file or folder, so you can't put things "back" from there.

  • Adobe Configurator - how to invoke action or script from html widget?

    How to invoke action or script from html wiget in Adobe Configurator?
    Please help! I tried to make it about 5 hours!
    I need something like that:
    I click link or image
    ...and it runs action.
    Thanks!

    If you click on the question mark ( as shown below) on the right of Configurator  2 window
    the user guide installed on your computer within Configurator 2  will open
    Anyway once you have your action or script button  in your panel you must select it and configure it in the  inspector palette

  • How to invoke SMS notification script from Siebel aplication.

    Hi
    I have a binary file written in shell script which i have placed in my siebel server(Linux platform) and i have executed it by providing Mobile number and message as parameters for sending SMS notifications. I am able to send SMS successfully.
    Now i would like to invoke this file from my Siebel application 8.1 based on Service request status change.
    Please let me how can i proceed?
    How do i invoke the shell script? Should i proceed with a creation of workflow and then invoke this script?
    Regards,
    Suman

    This is not something supported at this time. Please let Apple know that you would like this feature added:
    apple.com/feedback

  • Invoke CGI script in JSP?

    Hello All:
    I tried to use:
    <jsp:include flush="true" page="/cgi/test.cgi">to invoke CGI script. The problem is the parameters in request were not passed to CGI. There is no this issue if page invoked is JSP.
    I am using SunONE Web Server 6.1
    I appreciate you for any consideration.

    Well, you can only do that when the new page is complete - probably in the onload event. Which means you have to tell it which field you want to focus - probably by submitting an extra parameter.
    Heres a working example:
    <html>
    <head>
    <script language="javascript">
      function saveCurrentField(field){
        document.forms[0].currentField.value = field.name;
      function focusLastField(){
        var lastField = "${param.currentField}";
        document.forms[0][lastField].focus();
    </script>
    </head>
    <body onload="focusLastField()">
    <h1>Testing jsp to focus a field on load of the page</h1>
    <form>
    <table>
    <tr><td>Name:</td><td><input type="text" name="name" value="${param.name}" onchange="saveCurrentField(this); this.form.submit();"></td></tr>
    <tr><td>email:</td><td> <input type="text" name="email" value="${param.email}" onchange="saveCurrentField(this); this.form.submit();"></td></tr>
    <tr><td>Age:</td><td>
      <select name="age" onchange="saveCurrentField(this); this.form.submit();">
        <option>  0-20
        <option> 21-40
        <option> 41-60
        <option> 60+
      </select>
    </td></tr>
    </table>
    <input type="hidden" name="currentField">
    </form>
    </body>
    </html>I wrote it using EL expressions.
    If you don't have a JSP2.0 container, or EL is not enabled, replace those ${param.xxxxxx} expressions with <%= request.getParameter"xxxxxxx") %>
    Cheers,
    evnafets

  • SHELL SCRIPT RUNS AS PUBLIC USER WHEN INVOKED FROM BROWSER ALTHOUGH LOGGED

    I am trying to have a pdf converter which converts the HTML pages on the fly to pdf. For this I have an application
    installed on the MT called HTMLDOC(opensource app). Now I can convert static
    HTML pages on the MT using the command "HTMLDOC". After this I am using an sh
    file which is place in cgi-bin which executes the the conversion on the fly,
    getting the contents form the URL passed to it.
    I am using this sh script(test.sh)
    #!/bin/sh
    HTMLDOC_NOCGI=1; export HTMLDOC_NOCGI
    # The "options" variable contains any options you want to pass to HTMLDOC.
    options="-t pdf --webpage "
    # Tell the browser to expect a PDF file...
    echo "Content-Type: application/pdf"
    echo ""
    # Run HTMLDOC to generate the PDF file...
    htmldoc $options http://${SERVER_NAME}:${SERVER_PORT}$PATH_INFO
    My normal HTML page is invoked as follows
    http://<server>:<port>/dad/page.html
    To convert to pdf I call the page as follows
    http://<server>:<port>/cgi-bin/test.sh/dad/page.html
    This will convert the page.html to a pdf. However the user is always PUBLIC, although I have logged
    into the portal. Now since the user is always PUBLIC my application doesnt
    render as expected. I need to have the user be logged in a valid OID user,
    which it already is. I know this has something to do with the mod_osso.confg
    file, but just doesnt seem to work. Could anyone help on this

    Even though your cgi script is authenticated, it does not have access to your session/cookies when it makes it's own independent web request.<br>
    You could ask it to log on first, which is how web clipping works, but then you'd have to manage credentials, i.e. you'd have to communicate your user name and password to the script. There's all kinds of issues with that and although possible, I wouldn't recommend it.<br>
    <br>
    Getting back to your requirement, you're looking to produce a printed version of the web page, right? Why don't you just create a special stylesheet for this purpose?<br>
    You can override the portal classes, hide sections of the page, etc. <br>
    <br>
    The other option would be to setup a virtual PDF network printer using Ghostscript or something similar. There are also lots of PDF conversion services available on the net.<br>
    <br>
    HTH.<br>
    <br>
    Ingo<br>
    <br>

Maybe you are looking for