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>

Similar Messages

  • Oracle Server 11.2.0.1.0 64-bit fails when invoked from InstallShield

    I'm trying to install the Oracle Server 11.2.0.1.0 64-bit on Windows 2008 SP1 from the InstallShield 2010.
    The installation is silent. Invoked by command line:
    J:\Oracle_11.2.0_x64\OracleServer_11.2.0.1_x64\setup.exe ORACLE_HOME_NAME="ARAXI_11" -silent -nowelcome -force -nowait -noconsole -loglevel fine -noconfig -ignoreSysPrereqs use_prereq_checker=false -responseFile C:\Oracle\11.2.0\installation\scripts\SVRCUSTOM11.2.0.rsp
    The problem is that when the command is invoked from command line (cmd), the installation is successful.
    However, when the same command is invoked from under the InstallShield, the installation fails on Architecture requirement check:
    INFO: *********************************************
    INFO: Architecture: This is a prerequisite condition to test whether the system has a certified architecture.
    INFO: Severity:CRITICAL
    INFO: OverallStatus:OPERATION_FAILED
    INFO: All forked task are completed at state performChecks
    INFO: Completed background operations
    INFO: Moved to state <performChecks>
    INFO: Waiting for completion of background operations
    INFO: Completed background operations
    INFO: Validating state <performChecks>
    INFO: Using default Validator configured in the Action class oracle.install.ivw.db.action.PrereqAction
    INFO: Adding ExitStatus PREREQUISITES_NOT_MET to the exit status set
    SEVERE: [FATAL] [INS-13013] Target environment do not meet some mandatory requirements.
    CAUSE: Some of the mandatory prerequisites are not met. See logs for details. C:\Oracle\Inventory\logs\installActions2011-05-19_12-58-13PM.log
    ACTION: Identify the list of failed prerequisite checks from the log: C:\Oracle\Inventory\logs\installActions2011-05-19_12-58-13PM.log. Then either from the log file or from installation manual find the appropriate configuration to meet the prerequisites and fix it manually.
    INFO: Advice is ABORT
    INFO: Adding ExitStatus INVALID_USER_INPUT to the exit status set
    The questions:
    1. Why the requirement checks give different results when installation is invoked from CMD and from InstallShield?
    2. Why the requirement checks are done despite the parameters "-ignoreSysPrereqs" and "use_prereq_checker=false"?
    3. What should I do to get the installation pass (either remove the check or make it satisfying)?
    PS. The 32 bit Oracle Server installation on Windows 2003 works without problem when invoked from InstallShield.

    Please use 2008R2 if you want to install 11gR2 versionThank you for that update. Possibly it will help me to solve another trouble.
    Regarding the problem I described, the issue is that I install Oracle Client 32 bit prior to trying to install Oracle Servier 64 bit.
    The Oracle Client setup had started RemoteExecService.exe 32 bit process. And the process remained running after the installation completed.
    The Oracle Server setup utilizes the running RemoteExecService.exe process. Since the process is 32 bit, the architecture requirement check had failed.
    I've added to my script killing the process
    taskkill /F /IM RemoteExecService.exe
    before invoking the Oracle Server installation.
    That way the Oracle Server setup starts another RemoteExecService.exe process and the new process is 64 bit.
    The architecture requirement succeed.

  • Faults in BPEL when invoked from a Custom built Web Application

    Hello there,
    I have developed a BPEL flow for a HealthCare demo and it works fine and all is well when it is invoked from the BPEL Console's initiate screen.
    I developed a webapplication to invoke the same (using the regular com.collaxa api for invokation of any BPEL process). It invokes the BPEL successfully and I can see the whole Payload in the 'receiveInput' section of the BPEL Flow. But the very First 'Assign' in which i just assign a text string as a default value to an input element faults out stating that the 'to' field is a 'zero node'... The assign stage also shows the payload with all values in it. But it errors out...
    here is the payload in the 'receiveInput' stage:
    <inputVariable>
    <part name="payload" >
    <HealthCareWorkFlowProcessRequest>
    <enduser_name>pavan</enduser_name>
    <enduser_phone_number>08046521345</enduser_phone_number>
    <enduser_username>pkvedam</enduser_username>
    <enduser_email_id>[email protected]</enduser_email_id>
    <problem_desc>cancer</problem_desc>
    <prob_relates_to>onchology</prob_relates_to>
    <doctor_assigned/>
    <doctor_assigned_email_id/>
    <proposed_date>13-10-2006</proposed_date>
    <proposed_time>09:00</proposed_time>
    <proposed_duration>01:00</proposed_duration>
    <patient_comments>swelling in the arm pit</patient_comments>
    <receptionist_comments/>
    <doctor_comments/>
    <receptionist_username>employee</receptionist_username>
    <receptionist_email_id>[email protected]</receptionist_email_id>
    </HealthCareWorkFlowProcessRequest>
    </part>
    </inputVariable>
    Here is the ASSIGN stage errors out (copied to clipboard):
    [2006/10/14 10:44:54]
    Error in <assign> expression: <to> value is empty at line "46". The XPath expression:
    "/child::client:HealthCareWorkFlowProcessRequedst/child::client:receptionist_username"
    returns zero node, when applied to document shown below:
    <HealthCareWorkFlowProcessRequest>
    <enduser_name>pavan</enduser_name>
    <enduser_phone_number>08046521345</enduser_phone_number>
    <enduser_username>pkvedam</enduser_username>
    <enduser_email_id>[email protected]</enduser_email_id>
    <problem_desc>cancer</problem_desc>
    <prob_relates_to>onchology</prob_relates_to>
    <doctor_assigned/>
    <doctor_assigned_email_id/>
    <proposed_date>13-10-2006</proposed_date>
    <proposed_time>09:00</proposed_time>
    <proposed_duration>01:00</proposed_duration>
    <patient_comments>swelling in the arm pit</patient_comments>
    <receptionist_comments/>
    <doctor_comments/>
    <receptionist_username>employee</receptionist_username>
    <receptionist_email_id>[email protected]</receptionist_email_id>
    </HealthCareWorkFlowProcessRequest>
    <selectionFailure>
    <part name="summary" >
    <summary>XPath query string returns zero node. According to BPEL4WS spec 1.1 section 14.3, The assign activity &lt;to&gt; part query should not return zero node. Please check the BPEL source at line number "46" and verify the &lt;to&gt; part xpath query. </summary>
    </part>
    </selectionFailure>

    oops... sorry... I had typed it in as there is no way to copy that 'error message' on to the clipboard from the BPEL FLOW depiction.
    it must have read 'HealthCareWorkFlowProcessRequest'...
    the problem is not with the typo... :(
    Am not able to find the root cause... but the flow fails when invoked from my web application...

  • Unix shell script run from pl/sql procedure

    Hi Guru
    I want to run unix shell script from pl/sql procedure. Actual I want to run it from developer 10g form.
    Please guide me in this regards
    Regards
    Jewel

    Look at the host or client_host builtins in the help

  • Parameters for Shell Script running through DBMS_SCHEDULER as Executable

    Hi,
    I'm using Oracle 10.2.0.1 on Solaris.
    I have a shell script to run through DBMS_SCHEDULER.
    DBMS_SCHEDULER.CREATE_PROGRAM (
    program_name => 'PROGRAM_NAME',
    program_type => 'EXECUTABLE',
    program_action => '/home/oracle/test.sh',
    enabled => TRUE,
    comments => 'Test Shell Script'
    But how do I define the parameters for the shell script?
    Lets say if I run the shell script from the Unix promt I will enter as below:
    /home/oracle/test.sh PITS aed5 XYZ
    How do I define it in the DBMS_SCHEDULER.define_program_argument?
    Thanks,
    Shail

    When you create the program you define the number of parameters it will accept:
    DBMS_SCHEDULER.CREATE_PROGRAM (
    program_name => 'PROGRAM_NAME',
    program_type => 'EXECUTABLE',
    program_action => '/home/oracle/test.sh',
    enabled => TRUE,
    comments => 'Test Shell Script',
    number_of_arguments     => 3
    );then you define your job arguments and set default values. This is optional - but if you don't then you will have to define the values using the set_job_argument_value:
    -- defines the first argument
    DBMS_SCHEDULER.DEFINE_PROGRAM_ARGUMENT(
       program_name   => 'PROGRAM_NAME',
       argument_position   => 1,
       argument_name           => 'arg1',
       argument_type           'CHAR',
       default_value          => 'PITS',
    );You can set the argument vaues using:
    DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE (
       job_name => 'JOB1',   
       argument_position  => 1,
       argument_value => 'PITS');or using the argument name defined using the define_program argument
    DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE (
       job_name => 'JOB1',   
       argument_name  => 'arg1',
       argument_value => 'PITS');where JOB1 is a job for program PROGRAM_NAME created using the dbms_scheduler.create_job procedure
    see docmentation: http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_sched.htm for more details...

  • Parameters for Shell Script running DBMS_SCHEDULER as Executable

    Hi,
    I have a shell script to run through DBMS_SCHEDULER.
    DBMS_SCHEDULER.CREATE_PROGRAM (
    program_name => 'PROGRAM_NAME',
    program_type => 'EXECUTABLE',
    program_action => '/home/oracle/test.sh',
    enabled => TRUE,
    comments => 'Test Shell Script'
    But how do I define the parameters for the shell script?
    Lets say if I run the shell script from the Unix promt I will enter as below:
    /home/oracle/test.sh -d aed5 -p "XYZ"
    How do I define it in the DBMS_SCHEDULER.define_program_argument?
    Thanks in advance,
    Samujjwal Basu

    Re: Excute Unix command Using PL SQL might help.

  • EBS Forms functional script runs fine in OpenScript but not from OTM

    Hi,
    I have an EBS forms functional test script which runs fine in OpenScript, but when scheduled from OTM, the web part runs fine but when it comes to forms, the script fails with the following error:
    Forms Object Not Found! XPath: //forms:window[(@name='NAVIGATOR')], Type: oracle.oats.scripting.modules.formsFT.helper.test.FormWindow, Cause: No Matches <Less>
    I have performed all the steps below already:
    1) Stopping the OATS Agent service and changing it to manual.
    2) Starting the command prompt and running the AgentManagerService command as mentioned in your forum.
    3) The console displays
    C:\>C:\OracleATS\agentmanager\bin\AgentManagerService.exe -c AgentManagerService
    .conf
    wrapper  | --> Wrapper Started as Console
    wrapper  | Launching a JVM...
    jvm 1    | Wrapper (Version 3.0.3)
    jvm 1    |
    4) I have added the test in the OTM with the following command line settings:
    -browser.type InternetExplorer -formsft.startup_timeout 30 -formsft.action_timeout 20 -formsft.response_timeout 10 -delayPercentage -1 -delayMin 0 -delayMax 5 -FormsAutomationEnabler.bat -enableForms true
    But each time the script fails, please note that my script has assets and they are placed within the script folder.
    Please help me on this at earliest.
    Thanks,
    Aarti

    Hello Aarti!
    I had the same problem and this steps help to solve the problem:
    You need to enable Forms Automation under agent. Please follow by below steps.
    1.open command prompt
    2.cd C:\OracleATS\agent
    3.FormsAutomationEnabler.bat -enableForms true
    4. Run script from OTM
    Attila

  • Default admin user when restoring from time machine backup in setup assistant

    Hello,
    Apologies if this has already been answered elsewhere.
    I will soon take delivery of a new iMac running Mac OS Mountain Lion, and I will want to restore my full Time Machine backup which was made on a MacBook Pro (which was my main machine, but is now faulty - it was running Snow Leopard).
    On the MacBook Pro I had 2 user accounts.  Mine which was the default admin account (named Ian Johnson), and my wife's which was a standard user account.
    Now, I know that I should use SetUp Assistant to restore user accounts etc from the Time Machine backup, but I'm wondering whether during that process I will be asked to create another admin user account when I first run SetUp Assistant.  Ideally I would like to end up with exactly the same user accounts as on my old MacBook Pro.
    The reason I'm asking in advance is that I believe it's hard to "undo" whatever default admin user account you set up on first use of a new Mac, so want to be prepared.
    Any help appreciated, thanks.
    Ian

    I'm wondering whether during that process I will be asked to create another admin user account when I first run SetUp Assistant.
    You won't be, provided you go straight into Setup Assistant the first time you boot the new machine.

  • Start-up script to access public folder on iMac from iBook

    I have a public folder on my iMac (running Leopard) that I can access from my iBook (running Tiger) by routing through with Finder each time I start up my iBook. I would like to have a script automatically run at start up on my iBook to connect to the public folder on my iMac. If the iMac is powered on, the connection is to be made; if the iMac is off, obviously the connection is not made, but the iBook does not hang-up, it continues without the public folder connection.

    Well this can be done with some caveats. Here is what I did(on Tiger iBook G3( I didn't try on my Panther ibook G4), but it should work on that too. Forgive me. This G3 is a tester so....) and some explanations about it.
    I made a unix executable with pico in Terminal. Ran chmod u+x on it. Called it contoamac.
    #!/bin/bash
    open afp://192.168.0.6/
    The 0.6 is my other machine(your iMac per se) with Leopard. I put the executable in my iBook(your iBook also as reference) in Sys.Pref., Accounts,LoginItems. Only turned on sharing on Leopard machine. But you either have to catch the Leopard machine awake or set it in energy savings to never sleep. Possibly you could have both machines never go to sleep and that would work unless there is a time out on server uptime. Rebooted ibook and it autoed to login password(to do with no pass is another story involving visudo, etc.) on Connect to server menu. I know I have forgotten something to explain.
    I'm going to run this reboot and try and get a quick screen shot of boot/connect process next. Right back. Whew!

  • Allow other users when upgrading from version 8 to 9

    When I originally installed Parallels 8 I did not allow access to Windows to other users on my iMac.  I am now upgrading to Parallels 9 and want to enable another user on my computer to access my Windows programs.  Will I be prompted to allow other users when I install the Parallels 9 upgrade or will I have to go into Parallels 9 later to allow this.  If I have to go in later, how do i do it.

    You might want to ask in the Parallels forum as to how Parallels 9 works. http://forum.parallels.com/forum.php

  • Indesign CC lags when switching from browser/another app then back to Indesign

    When i copy text from say, Word, and go to paste it into my indesign document, there is a delay. Example: When I go from Word, then back to indesign, I click on the text block and other items in my indesign window, but it's unresponsive, almost like it is frozen. After several seconds, which seem like forever, all is fine and i'm able to paste. This also happens when jumping from Chrome or Safari. It does not happen only when I'm pasting text, but also going from Chrome/Safari back to indesign, sometimes indesign is unresponsive then too. I have not noticed this in illustrator.
    Today I had to a lot of copying and pasting from word into indesign and it happened all the time. I'm pasting anywhere from half a page to a full page of text. not giants amount at once.
    fyi, i have "prevent app nap" disabled
    I have a late 2013 mac pro
    running yosemite
    24 gb memory

    i hear you. i just bought my new mac pro. my last mac was 8 years old and i used to only update my adobe software every couple of years, allowing the bugs to be worked out. i don't jump on the always-need-the-newest bandwagon.
    however, i am now being forced into that very model by both companies:
    having to join the cable company of software, creative cloud, or choose to never upgrade my 3 apps again, and by being subjected to apple's hardware/software updates, which can affect my workflow.
    for me, apple and adobe have managed to work together fine for the past 20 years: bugs being worked out through updates/forums.
    the blame game has been going on for as long as i've used these products. it doesn't really add to the conversation at this point.

  • How do I run a shell script as a different user

    I'm setting up a daily.local file to put in the /etc directory. This file will then be run as root but the file contains a script that must be run as a different user.
    Here's what I've tried.
    su - differentuser path/to/script/script.sh parameter1 parameter2
    I'm getting an error with the script because the parameters are not being passed. The script worked fine in 10.4.11 Server but 10.5.8 Server doesn't like it.
    Any ideas?
    Thanks
    Bart

    I'm setting up a daily.local file to put in the /etc directory. This file will then be run as root but the file contains a script that must be run as a different user.
    Here's what I've tried.
    su - differentuser path/to/script/script.sh parameter1 parameter2
    I'm getting an error with the script because the parameters are not being passed. The script worked fine in 10.4.11 Server but 10.5.8 Server doesn't like it.
    Any ideas?
    Thanks
    Bart

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

  • Bug?: layers.add() is not working properly when invoked from menu (ID/CS6/Win7)

    Hello Devs,
    I am facing a mysterious issue with the layers.add() method.
    I am trying to create n number of layers for my document. So I have decided to create a menu for this.
    I have creatd two scripts
    1. For creating menu & menu action,
    2. Actual script that creates n number of layers.
    When I run the script #2 direclty from ESTK it works fine.
    Now when I try to invoke the same script from the Menu it is not working fine. Only the last layer is created.
    Script 1: LayerPopupMenuAction
    #target indesign
    #targetengine createLayerset
    var layerTemplateScript = File(File(getActiveScriptPath()).parent.fsName+"/IntializeTemplate.jsx");
    var initTemplateHandler = {
        'beforeDisplay' : function(ev)
                ev.target.enabled = (app.documents.length>0);
        'onInvoke' : function()
                app.doScript(layerTemplateScript, ScriptLanguage.JAVASCRIPT, undefined, UndoModes.FAST_ENTIRE_SCRIPT, "Initialize Script");
    var layerMenuAction = app.scriptMenuActions.add("&Create Layer Set");
    for(var init_ev in initTemplateHandler) {
        layerMenuAction.eventListeners.add(init_ev, initTemplateHandler[init_ev]);
    var refMenuItem = app.menus.item("$ID/LayerPanelPopup");
    refMenuItem.menuItems.add(layerMenuAction, LocationOptions.AFTER, refMenuItem.menuItems.item(2));
    function getActiveScriptPath() {
        // This function returns the path to the active script, even when running from ESTK
        try {
            return app.activeScript;
        } catch(e) {
            return e.fileName;
    Script 2: IntializeTemplate
    #target indesign
    if (app.documents.length == 0){
        alert("Please open a document and try again", "Document Error", true);
        exit();
    var templateDoc = app.activeDocument;
    var layerNameArray = ["Fixed_Static_Assets", "Absolute_User_Assets", "Relative_User_Assets"];
    CreateLayers(layerNameArray);
    alert("Initialization Successful");
    //--------------------------------FUNCTIONS ARE DEFINED HERE--------------------------------
    function CreateLayers(LayerNameList){
        var layerListLength = LayerNameList.length;
        var layerObject;
        for (var ln=0; ln<layerListLength; ln++){
            layerObject = templateDoc.layers.itemByName(LayerNameList[ln]);
            if (layerObject.isValid==false){
                layerObject = templateDoc.layers.add({name:LayerNameList[ln]});
                //$.writeln('Layer Creation: ' + layerObject.isValid + ' for '+layerObject.name);
        //Merger Default Layer with the bottom layer:
        var defaultLayer = templateDoc.layers.itemByName("Layer 1");
        if(defaultLayer.isValid==true){
            //$.writeln('Default is Valid and will be merged with top most layer');
            layerObject.merge([defaultLayer]);
    Any help / guidance on this regard will be much helpful.
    @Marijan Tompa [tomaxxi]: I googled for the solution and noticed that you have already worked on similar type of script. Please help me if you can.
    Thanks
    Green4ever

    Hi Green4ever,
    At a very first sight I'd suspect UndoModes.FAST_ENTIRE_SCRIPT which, as you may know, can deeply scramble script steps, especially when a try...catch is in use.
    Try to replace FAST_ENTIRE_SCRIPT by ENTIRE_SCRIPT and tell us.
    @+
    Marc

  • Losing relationship public names when updating from 10.3 to 10.4

    Hi
    Pretty much as the subject line says! When creating a rulebase in 10.3 OPM automatically creates public names (for containment relationships) when you name the forward and reverse relationships. When you open the project in 10.4 and run the upgrade wizard on the rulebase it doesn't carry the relationship public names across. Then if you try to build the rulebase as a module it says it can't export the entities as the relationships have no public names and you then have to go through all the relationships and enter by hand.
    Am I missing something here?

    Hi Roger,
    No you didn't miss anything. There might be a bug in the upgrade process which only affects containment relationship.
    I have logged this to be fixed in future release.
    Thanks,
    Kevin
    Edited by: Kevin Wan on 16-Oct-2012 16:35

Maybe you are looking for

  • Re: [iPlanet-JATO] .select()

    Prashanth, I assume you are trying to set the default values of the selectables. Matt, Actually, I believe this is a view type behavior because it is manipulating the html properties upon preparing the object for display, however, currently it appear

  • Get current value of the voltage of an AO channel

    Hello, Is it possible to query the state of an AO channel? I would like to know what the current value of the voltage is, but can't seem to find a way to do it. Thank you

  • Re-Arrange Images In Library

    OK, time for me to feel dense. I am trying to re-arrange the images in the library so I can compare multiple images by f stop. I can't find the way to drag them into f stop order from file name order. I tried changing the sort to user order but that

  • HT1338 After a software update, how do I get my camera to work on my Mac Air?

    After a software update, how do I get my camera to work on mu MacBook Air?

  • Can I sell my copy of DW to my company?

    I've been using DW as a hobbyist. Now I plan to start my own business. If I register the business can I sell my copy of DW to my company? The reason is so when I get a new PC with a new OS for my business, I can use this copy of DW on the new OS with