Proxy.cfg skipAuthForViaHeader parameter

TID 3988333 says:
skipAuthForViaHeader=1 (0 to disable)(Default=0)
// Authentication to proxy bypassed when coming through another proxy.This setting must be configured in the proxy.cfg file to enable proxy to skip the authentication when the request is coming through another proxy.By default, proxy will request for authentication.
This means to me that if I don't want authentication skipped if the NBM proxy is accessed by another proxy, then I would want this set to 0.
Craig, in his Proxy.cfg says:
; New parameter from BM3.9SP1
; =1 prevents authentication from being bypassed when proxy accessed
; from another proxy. (Schools, take note!)
skipAuthForViaHeader=1
I read Craig's note as meaning that if I don't want authentication skipped if the NBM proxy is accessed by another proxy, then I would want this set to 1.
Which is correct?
Dan

Luckily I don't have to deal with those in this environment; just adults that are not too savvy. However, It might be good to include as well just in case.
Thanks, Craig. This is the kind of supporting information that might be useful to administrators so they can see 'why' you want to use the switch; not just what the states of the switch are. Of course I think I am 'preaching to the choir' as you have by far written the most on NBM and provided supporting documentation. Maybe a white paper on Proxy.cfg settings, when they are best used, whether they apply to just the forward proxy or reverse proxy or both, etc would be useful.
I just found out the other day from Gonzalo that the Virus Definition patterns only apply to the reverse proxy. Therefore if I am not using a reverse proxy, I don't want to turn on that switch so I don't incur the additional overhead.
Dan
Originally Posted by Craig Johnson
In article <[email protected]>, Dchunt wrote:
> BTW, this parameter only comes into play if you have a proxy hierarchy,
> right? IE, if you have a large organization and one part of it is using
> a squid proxy then the output of that goes to an NBM proxy then the
> output of that goes to the Internet, right? It doesn't come into play
> if you have a single NBM proxy between you and the Internet, even if
> you are going through the Internet to a site with a reverse proxy at
> the far end, right?
>
I'll tell you when it comes into play... When you have some smart-*ssed
teenager who finds out that without that switch he can run his own proxy
(perhaps off a thumb drive) in a cache hierarchy, and completely bypass
BMgr access rules.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to Craig Johnson Consulting - BorderManager, NetWare, and More ***

Similar Messages

Proxy.CFG file

The the revision 30 PROXY.CFG file from Craig Johnson, there appears to
be a duplicate entery for the "enableCacheInVersionDowngrade" switch.
Is this correct, or should one be deleted?
;New parameter from BM3.9SP1. Set this option to allow caching in
proxy ;when browser is set to http 1.1 and web server responds with
http 1.1
enableCacheInVersionDowngrade=1
;New parameter (from BM38SP5_IR1.ZIP) to allow
enableCacheInVersionDowngrade=1

In article <Gh1Km.1589$[email protected]>, Chris Premo
wrote:
> The the revision 30 PROXY.CFG file from Craig Johnson, there appears to
> be a duplicate entery for the "enableCacheInVersionDowngrade" switch.
> Is this correct, or should one be deleted?
>
Typo I missed. You can delete one of them, but it won't hurt to have it
in there twice. I'll try to correct it for rev 31!
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Proxy.cfg - Correct setting for ResolveProxyIPAddress

According to TID 3988333 the description of this parameter is "Default behaviour is to send an SSL authentication redirect to a host name instead of a IP address. 0 to disable the same. Requires PXY023 or later."
Also, the default setting in Proxy.nlm is 1. However, in Craig's Proxy.cfg he has it set to 0. I would think you would want this to be set to 1, no?
Dan

OK, I had no idea that that is what this parameter pertained to. Now I see what you are talking about with the BorderManager SSL login as an alternative to Client Trust. We don't use that so that is why I didn't understand.
To me this again proves that we need more documentation on what these parameters are and why you would use them. I would agree with you after hearing more background that it should be set to 0.
FYI, the default for 3.9 SP1 proxy is 1! I wonder why Gonzalo thinks this is preferred?
Dan
Originally Posted by Craig Johnson
In article <[email protected]>, Dchunt wrote:
> Also, the default setting in Proxy.nlm is 1. However, in Craig's
> Proxy.cfg he has it set to 0. I would think you would want this to be
> set to 1, no?
>
If that's what I think it is, no. I think that has to do with how the
SSL login page shows up on the browser. Default would have it show up
with the server name as a URL. Unfortunately, that also means you need
a DNS entry for the server name. The IP address has always worked,
which is why I set that to 0. (It may be that the problems I've seen
with SSL login failing with server name are related to incorrect host
file entries, but I think it was more widespread than that).
I definitely want the ssl logins redirected to IP address by default. I
might go to a URL if I had purchased a 3rd party certificate,
particularly if using authentication with reverse proxy. But I would be
ironing out DNS issues as well.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to Craig Johnson Consulting - BorderManager, NetWare, and More ***

Proxy.cfg IgnoreContent length vs IgnoreContentLengthCheck

In Craig's Proxy.cfg he has both 'IgnoreContentLength' and 'IgnoreContentLengthCheck'. In TID 3988333 and in the default Proxy.cfg settings from Proxy Console Screen 63 it only shows 'IgnoreContentLengthCheck'.
Apparently 'IgnoreContentLength' was used in BM 3.6 (bm36c02 TID 10072012). Are these both the same parameter but only 'IgnoreContentLengthCheck' applies to BM 3.9 SP1?
If not, then what is the difference between the two?
Dan

Maybe that does make sense as 3.9 is significantly different than 3.8 and below. I was just trying to clean things up for my own proxy.cfg so that I knew what the various parameters were for. That is when I came across some of these anomalies. I understand what you were trying to do in terms of making a 'universal' proxy.cfg.
Dan
Originally Posted by Craig Johnson
In article <[email protected]>, Dchunt wrote:
> Apparently 'IgnoreContentLength' was used in BM 3.6 (bm36c02 TID
> 10072012). Are these both the same parameter but only
> 'IgnoreContentLengthCheck' applies to BM 3.9 SP1?
>
Very likely. Which makes it worriesome to remove entries that appear
not to be needed in 3.9, if the proxy.cfg is to be used in other
versions.
I'm starting to think about creating a new version, for BM 3.9 only...
Leave the old one as-is for 3.8 and earlier, and just put in new stuff
for 3.9, with unnecessary settings removed. Should be the best of
both worlds.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to Craig Johnson Consulting - BorderManager, NetWare, and More ***

Proxy.cfg [Object Cache] section

In the [Object Cache] section of Proxy.cfg I have questions on two parameters:
cut thru no CLH length - The default is 51200 (Proxy Console #63) but Craig's Proxy.cfg sets it to 0. TID 10063926 talks about this but I wonder if this problem isn't fixed in NBM 3.9 SP1 and therefore doesn't need to be set to 0 now? Other TID's (10075563, 10069305 for instance) talk about setting it to 5120. What should be the correct setting for 3.9 SP1?
disk management factor - the default is 400 (Proxy Console #63) but Craig's Proxy.cfg sets it to 4000. Can someone tell me what this does and why it should be set to 4000 instead of 400?
thanks,
dan

Originally Posted by Craig Johnson
In article <[email protected]>, Dchunt wrote:
> [Object Cache]
> dirsBasedOnVolumeSize = 0
> cacheVolumeOnTradiitonal = 1
> purgeVolumeAgressiveMode = 0
> CacheNormalUsage = 85
> CacheNormalUsageValue = -1
> CacheHighUsage = 92
> CacheHighUsageValue = -1
> number of cache directories = 256
> cut thru no CLH length = 51200
> disk management factor = 400
> max hot unreferenced time = 1800
> nax hot nodes = 7000
> size cahce hash table = 262144
>
> I mis-spoke when I said that you had the 'disk management factor' set
> to 4000 in your proxy.cfg. It is not in there.
OK - this is not something that is in proxy.cfg at all. These are
settings in NWADMN32/iManager. For instance, the max hot nodes @ 7000
is a default value that is too low for busy servers. (Recommended is
50000). This sounds like you have not configured the server per the
proxy tuning tid, or my BMgr books.
> It is another
> Proxy.cfg from one of our servers I was looking at. I was hoping to
> find out what its use was, not to mention what the use was for the
> other parameters in this section.
Find the parameters in NWADMN32 (or iMan in BM 3.9) and check the help
there. Also see the proxy tuning tid.
>
> Also, doesn't seem strange that the default for "cut thru no CLH
> length" is 51200 but in TID 3988333 it is set to 0? That's a pretty
> big differernce! This is also mentioned in TID 10063926, FWIW.
>
It seems odd at the moment - I've not really looked into it. I know
that when the proxy.cfg setting came out, it fixed a lot of problem
sites at the time. I've left it at the setting which worked for the
time.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to Craig Johnson Consulting - BorderManager, NetWare, and More ***
Got it, Craig. I did forget to update some of the settings for the Proxy Cache in iManager. I'll leave the cut thru no CLH length at 0 for now.
Dan

BM 3.9 Block source and proxy.cfg

Hi All,
With BM 3.8 I used to block some internal computers from browsing by adding a deny access rule. I am trying to get the same rule put in using Imanager on bm 3.9 and it doesn't work. Is anyone else doing this. I add an access rule that has 2 conditions(I want to add one with just one condition for computer name but it won't let me), the first is the source hostname starts with and I put in the computer/dns name I then have to put in a codition for origin server port and I list port 80(I have tried 443 and 8080 also) I select deny access and the computer can still connect.
I can easily block urls and I figured it would be just as easy to block internal computers from going out, does anyone know of an easier way to block computers, I don't use filters at the moment.
Also I was going to use the proxy.cfg file from Craig Johnson but I am not sure if those settings are applicable to bm 3.9
Thanks for any help, has anyone found bm 3.9 to be better than the other versions?
Mike

In article <469B4EB3.2D81.003B.0@nospam_cancercare.mb.ca>, Mike Gerolami wrote:
> can easily block urls and I figured it would be just as easy to block internal computers from going out,
does anyone know of an easier way to block computers, I don't use filters at the moment.
>
Can you block dest=any url, source=pc IP address?
> Also I was going to use the proxy.cfg file from Craig Johnson but I am not sure if those settings are
applicable to bm 3.9
Yes, they are.
>
> Thanks for any help, has anyone found bm 3.9 to be better than the other versions?
Aside from bug fixes to come, and some new VPN features, there is not a great deal of difference in how BMgr
works. Most of the change was in getting rid of NWADMN32, so you can administer BMgr without needing
windows, or client32. There is one useful bug fix in there now, for sure: proxy unloads reliably now.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Default proxy.cfg

I may have a potential problem at a customer site, the customer running
BM3.9 with proxy enabled. They also have Citrix servers which using
proxy authentication. We used Craig's proxy.cfg and modified it to fit
the customers enviroment and it has been running fine since then.
The other day I was going through the customer enviroment and found
that the proxy.cfg only contained about 20 rows (default one perhaps).
When checking at the server console there were still configuration
settings for terminal servers. So my question is does the server save
the configuration settings and load them if proxy.cfg should be
"zeroed"?
Today the server was rebooted and still all seems to be working witout
the settings in proxy.cfg.
My next question is if it's possible to make a new proxy.cfg from the
actual settings on the running server?
//FCA68

In article <DSRZk.5386$[email protected]>, Fca68 wrote:
> So my question is does the server save
> the configuration settings and load them if proxy.cfg should be
> "zeroed"?
>
If you have no proxy.cfg and load BMgr, I think it does create a raw
.cfg file with a few settings in it.
> Today the server was rebooted and still all seems to be working witout
> the settings in proxy.cfg.
A BMgr server will run without all the extra settings in proxy.cfg.
(Late version BMgrs with patches probably have many of those settings as
defaults now, but not all). But there are definitely some non-default
settings in the proxy.cfg from my web site, and I still recommend using
it.
>
> My next question is if it's possible to make a new proxy.cfg from the
> actual settings on the running server?
>
Well, yes I think it will create a bare minimum one if there is no
proxy.cfg at all, but that does you no particular good. You can only
change those settings by putting entries into the proxy.cfg file, so
saving the proxy would normally only get you just what you started with
when you loaded proxy.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Proxy plugin - Debug parameter values

Up until a few months ago the proxy plugin documentation for WLS 8.1 included multiple values that the Debug parameter could be set to (e.g ALL to see just about everything, ones to see just headers etc). Now it only seems to have True|False. http://e-docs.bea.com/wls/docs81/plugins/plugin_params.html#1154491
Is there a reason this was changed? The old way was much more flexibile.
Has this been changed for the latest SP?
I am holding out some hope that maybe the documentation is incorrect.... Debug=ALL still works for 8.1 sp4

all the options seem to be there and working.
we are using DEBUG=ERR, since ALL crashes linux when the log grows to 2GB!

Gonzalo - What proxy parameters are valid?

Gonzalo or anyone else that knows for sure, can you tell me what proxy.cfg parameters are valid for NBM 3.9 SP1? Can I assume that if a parameter doesn't show up in the Proxy Console Screen 63, then it is not valid for 3.9 SP1?
For instance, in TID 3988333 (which is supposed to apply for NBM 3.9 at least), it mentions the 'AckWithNoDataOnSYN' parameter as follows:
AckWithNoDataOnSYN=1
// Browser gets 504 gateway timeout error accessing web server through proxy, because Proxy use TCP connections to the origin server piggyback the final ACK from the 3 way TCP handshake, with the HTTP GET request. Which deny by some type of origin web server.
//Set to 1 to prevent the problem, Also applied updated TCPIP stack. (default=0)
However, regardless of whether you set this parameter to 0 or 1, it does not show up on Proxy Console 63. Can I assume then that the fix for the problem this addresses has been encorporated into the code and therefore this parameter is no longer needed in 3.9 SP1?
IgnoreDuplicateChill is another one. In the above TID, it says:
IgnoreDuplicateChill=1 (0 to disable) (Default=1)
//Prevents many abends. Enabled by default in PXY012 build and later.
But this parameter also doesn't show up in Proxy Console Screen 63 regardless of whether it is set to 0 or 1. So has the fix been incorporated into the code and this parameter is irrelevant?
The reason this is important to understand has to do with troubleshooting. If you put in a parameter and you don't see it on Proxy Console Screen 63, then is that becuase you mis-typed the parameter or because it is not a valid parameter for this version of BorderManager?
Any thoughts?
Dan

In article <[email protected]>, Dchunt wrote:
> However, regardless of whether you set this parameter to 0 or 1, it
> does not show up on Proxy Console 63. Can I assume then that the fix
> for the problem this addresses has been encorporated into the code and
> therefore this parameter is no longer needed in 3.9 SP1?
>
I can't speak for Gonzalo on this, but I'm guessing that the answer is
'probably'. I worry that a setting which is important didn't make it
into the screen for some reason, and that perhaps it still works. (I
doubt it though - that screen is pretty new, and I think support put it
in there to see all the settings that matter. But it might be that
newer settings don't show up, if the code for that screen isn't checked
against later patches. )
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Only display first form URL in formsweb.cfg . mutiple URL does not work

Hi Friends,
I have 4 form application with 4 URL.
app. server as 10g in window 2003.
URL like as:
http://salerpt.com/forms/frmservlet?config=emis-srmenu
fmx file Location as C:\OraMid\forms\salerpt-Forms fmx name as srmenu.fmx in same directory
fmb file location as C:\OraMid\forms\salerpt-Forms_source fmx name as srmenu.fmb in same directory
# Single Sign-On OID configuration parameter
oracle_home=C:\OraMid
in formweb.cfg file
baseHTMLjinitiator=basejini.htm
workingDirector : workingDirectory= blank. but C:\OraMid\forms\salerpt-Forms right now
# Forms runtime argument: which form module to run
##form=test.fmx
## i moved bottom section of form section in here and before
##line as Forms runtime argument: database connection details
comment two line
#jinit_exename=jinit.exe
#jinit_mimetype=application/x-jinit-applet;version=1.3.1.22
I create 4 sections as
form=srmenu.fmx
width=1200
height=700
pageTitle=Sale Information System (SIS)
form=regsale.fmx
form=salefinincial.fmx
form=rptinfo.fmx
However it only display first srmenu form interface that i put in( 4 different URL. only display first URL)
It seems that one formsweb.cfg, it doesn not support multip form setting application.
I have 4 small forms application with 4 URL for one formsweb.cfg.
What should I need to do? I think that i miss some set up in configuration.
I am waiting for your help!
JIm

Hi Bgrant,
Please review my formsweb,cfg.
Thanks
I am looking for your help.
# $Id: formsweb.cfg 15-apr-2005.13:17:30 pkuhn Exp $
# formsweb.cfg defines parameter values used by the FormsServlet (frmservlet)
# This section defines the Default settings. Any of them may be overridden in the
# following Named Configuration sections. If they are not overridden, then the
# values here will be used.
# The default settings comprise two types of parameters: System parameters,
# which cannot be overridden in the URL, and User Parameters, which can.
# Parameters which are not marked as System parameters are User parameters.
# SYSTEM PARAMETERS
# These have fixed names and give information required by the Forms
# Servlet in order to function. They cannot be specified in the URL query
# string. But they can be overridden in a named configuration (see below).
# Some parameters specify file names: if the full path is not given,
# they are assumed to be in the same directory as this file. If a path
# is given, then it should be a physical path, not a URL.
# USER PARAMETERS
# These match variables (e.g. %form%) in the baseHTML file. Their values
# may be overridden by specifying them in the URL query string
# (e.g. "http://myhost.mydomain.com/forms/frmservlet?form=myform&width=700")
# or by overriding them in a specific, named configuration (see below)
[default]
# System parameter: default base HTML file
baseHTML=base.htm
# System parameter: base HTML file for use with JInitiator client
baseHTMLjinitiator=basejini.htm
# System parameter: base HTML file for use with Sun's Java Plug-In
baseHTMLjpi=basejpi.htm
# System parameter: delimiter for parameters in the base HTML files
HTMLdelimiter=%
# System parameter: working directory for Forms runtime processes
# WorkingDirectory defaults to <oracle_home>/forms if unset.
workingDirectory= C:\OraMid\forms\sales-Forms
# System parameter: file setting environment variables for the Forms runtime processes
envFile=default.env
# Forms runtime argument: whether to escape certain special characters
# in values extracted from the URL for other runtime arguments
escapeparams=true
# Forms runtime argument: which form module to run
#form=test.fmx
[[srmenu]]
form=srmenu.fmx
width=1200
height=700
pageTitle=Sale Management Information System
[[regsale]]
form=regsale.fmx
width=1200
height=1500
pageTitle=Sale Management Information System
[[salefinincial]
form=salefinincial.fmx
width=1200
height=1300
pageTitle=Sale Management Information System
[[rtpinfo]]
form=rptinfo.fmx
width=1200
height=1000
pageTitle=Sale Management Information System
# Forms runtime argument: database connection details
userid=scott/tigerd@oracleapp
# Forms runtime argument: whether to run in debug mode
debug=no
# Forms runtime argument: host for debugging
host=
# Forms runtime argument: port for debugging
port=
# Other Forms runtime arguments: grouped together as one parameter.
# These settings support running and debugging a form from the Builder:
otherparams=buffer_records=%buffer% debug_messages=%debug_messages% array=%array% obr=%obr% query_only=%query_only% quiet=%quiet% render=%render% record=%record% tracegroup=%tracegroup% log=%log% term=%term%
# Sub argument for otherparams
buffer=no
# Sub argument for otherparams
debug_messages=no
# Sub argument for otherparams
array=no
# Sub argument for otherparams
obr=no
# Sub argument for otherparams
query_only=no
# Sub argument for otherparams
quiet=yes
# Sub argument for otherparams
render=no
# Sub argument for otherparams
record=
# Sub argument for otherparams
tracegroup=
# Sub argument for otherparams
log=
# Sub argument for otherparams
term=
# HTML page title
pageTitle=Oracle Application Server Forms Services
# HTML attributes for the BODY tag
HTMLbodyAttrs=
# HTML to add before the form
HTMLbeforeForm=
# HTML to add after the form
HTMLafterForm=
# Forms applet parameter: URL path to Forms ListenerServlet
serverURL=/forms/lservlet
# Forms applet parameter
codebase=/forms/java
# Forms applet parameter
imageBase=DocumentBase
# Forms applet parameter
#width=750
width=1024
# Forms applet parameter
#height=600
height=768
# Forms applet parameter
separateFrame=false
# Forms applet parameter
splashScreen=
# Forms applet parameter
background=
# Forms applet parameter
lookAndFeel=Oracle
# Forms applet parameter
colorScheme=teal
# Forms applet parameter
logo=
# Forms applet parameter
restrictedURLparams=HTMLbodyAttrs,HTMLbeforeForm,pageTitle,HTMLafterForm,log,allow_debug,allowNewConnections
# Forms applet parameter
formsMessageListener=
# Forms applet parameter
recordFileName=
# Forms applet parameter
serverApp=default
# Forms applet archive setting for JInitiator
archive_jini=frmall_jinit.jar
# Forms applet archive setting for other clients (Sun Java Plugin, Appletviewer, etc)
archive=frmall.jar
# Number of times client should retry if a network failure occurs. You should
# only change this after reading the documentation.
networkRetries=0
# Page displayed to Netscape users to allow them to download Oracle JInitiator.
# Oracle JInitiator is used with Windows clients.
# If you create your own page, you should set this parameter to point to it.
jinit_download_page=/forms/jinitiator/us/jinit_download.htm
# Parameter related to the version of JInitiator
jinit_classid=clsid:CAFECAFE-0013-0001-0022-ABCDEFABCDEF
# Parameter related to the version of JInitiator
#jinit_exename=jinit.exe
#Version=1,3,1,22
# Parameter related to the version of JInitiator
#jinit_mimetype=application/x-jinit-applet;version=1.3.1.22
# Page displayed to users to allow them to download Sun's Java Plugin.
# Sun's Java Plugin is typically used for non-Windows clients.
# (NOTE: you should check this page and possibly change the settings)
jpi_download_page=http://java.sun.com/products/archive/j2se/1.4.2_06/index.html
# Parameter related to the version of the Java Plugin
jpi_classid=clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA
# Parameter related to the version of the Java Plugin
jpi_codebase=http://java.sun.com/products/plugin/autodl/jinstall-1_4_2-windows-i586.cab#Version=1,4,2,06
# Parameter related to the version of the Java Plugin
jpi_mimetype=application/x-java-applet;jpi-version=1.4.2_06
# EM config parameter
# Set this to "1" to enable Enterprise Manager to track Forms processes
em_mode=1
# Single Sign-On OID configuration parameter
oid_formsid=formsApp_sales.com_0Axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
# Single Sign-On OID configuration parameter
oracle_home=C:\OraMid
# Single Sign-On OID configuration parameter
formsid_group_dn=cn=Logical Application Group, orclApplicationCommonName=formsApp_sales.com_0A4911717Fxxxxxxxxxx, cn=forms, cn=Products, cn=OracleContext
# Single Sign-On OID configuration parameter: indicates whether we allow
# dynamic resource creation if the resource is not yet created in the OID.
ssoDynamicResourceCreate=true
# Single Sign-On parameter: URL to redirect to if ssoDynamicResourceCreate=false
ssoErrorUrl=
# Single Sign-On parameter: Cancel URL for the dynamic resource creation DAS page.
ssoCancelUrl=
# Single Sign-On parameter: indicates whether the url is protected in which
# case mod_osso will be given control for authentication or continue in
# the FormsServlet if not. It is false by default. Set it to true in an
# application-specific section to enable Single Sign-On for that application.
ssoMode=false
# The parameter allow_debug determines whether debugging is permitted.
# Administrators should set allow_debug to "true" if servlet
# debugging is required, or to provide access to the Forms Trace Xlate utility.
# Otherwise these activities will not be allowed (for security reasons).
allow_debug=false
# Parameter which determines whether new Forms sessions are allowed.
# This is also read by the Forms EM Overview page to show the
# current Forms status.
allowNewConnections=true
# EndUserMonitoring
# EndUserMonitoringEnabled parameter
# Indicates whether EUM/Chronos integration is enabled
EndUserMonitoringEnabled=
# EndUserMonitoringURL
# indicates where to record EUM/Chronos data
EndUserMonitoringURL=
# Example Named Configuration Section
# Example 1: configuration to run forms in a separate browser window with
# "generic" look and feel (include "config=sepwin" in the URL)
# You may define your own specific, named configurations (sets of parameters)
# by adding special sections as illustrated in the following examples.
# Note that you need only specify the parameters you want to change. The
# default values (defined above) will be used for all other parameters.
# Use of a specific configuration can be requested by including the text
# "config=<your_config_name>" in the query string of the URL used to run
# a form. For example, to use the sepwin configuration, your could issue
# a URL like "http://myhost.mydomain.com/forms/frmservlet?config=sepwin".
[sepwin]
separateFrame=False
lookandfeel=Generic
# Example Named Configuration Section
# Example 2: configuration forcing use of the Java Plugin in all cases (even if
# the client browser is on Windows)
[jpi]
baseHTMLJInitiator=basejpi.htm
# Example Named Configuration Section
# Example 3: configuration running the Forms ListenerServlet in debug mode
# (debug messages will be written to the servlet engine's log file).
[debug]
serverURL=/forms/lservlet/debug
# Sample configuration for deploying WebUtil. Note that WebUtil is shipped with
# DS but not AS and is also available for download from OTN.
[webutil]
WebUtilArchive=frmwebutil.jar,jacob.jar
WebUtilLogging=off
WebUtilLoggingDetail=normal
WebUtilErrorMode=Alert
WebUtilDispatchMonitorInterval=5
WebUtilTrustInternal=true
WebUtilMaxTransferSize=16384
baseHTMLjinitiator=webutiljini.htm
baseHTMLjpi=webutiljpi.htm
archive_jini=frmall_jinit.jar
archive=frmall.jar
lookAndFeel=oracle

Acrobat 9 slow to open pdf files through proxy

We are finding that it is very slow to open pdf files from various web sites
though the BorderManager proxy with Acrobat Reader version 9. This is not
the case with earlier versions of Acrobat Reader. We are using
BorderManager 3.8 sp 5. Has anyone else experienced this issue? Is there a
proxy.cfg setting I should be looking to change?
Thanks,
Brad Johnson
__________ Information from ESET NOD32 Antivirus, version of virus signature database 3928 (20090311) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com

In article <AbUtl.4166$[email protected]>, Brad Johnson
wrote:
> Has anyone else experienced this issue? Is there a
> proxy.cfg setting I should be looking to change?
>
I think this was an issue with older versions of BM that was addressed
with a proxy.cfg setting. Try the one from tip #63 at the URL below.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Pb with userid in formsweb.cfg

hi,
OracleApplication Server 10gR2
Patchset 10.1.2.2.0
i have a problem, when i define a section in formsweb.cfg with parameter userid=user/password@orcl , I still receive logon screen.
i receive logon screen also whith this url:
forms/frmservlet?form=form.fmx&userid=user/password@orcl
please i need your help
thank you

I read of a lot of people having trouble with the userid parameter in frmsweb.cfg. If you're already using SSO, then I would recommend instead of using this parameter for credentials, that you use a Resource Access Descriptor (RAD). This stores login information in your Oracle Internet Directory as either shared information, or per user. Demo URL that also covers HowTo
http://www.oracle.com/technology/sample_code/products/forms/viewlets/10g/frmsso/frmsso_viewlet_swf.html
Remember that for URL's, the forward slash "/" and backslash "\" are reserved characters, so the URL you listed should never work.

Forms web.cfg

Dear All,
I have installed developer 10g and when run form the following message available
"No plug in available for this content"
also in OC4J Instance following message appears
config filename "D:\Forms\forms\server\formsweb.cfg"
testmode false
please guide me
Best Regards

sir here is the code for forms web file. Plz guide me where i edit the code
# $Id: formsweb.cfg 15-apr-2005.13:17:30 pkuhn Exp $
# formsweb.cfg defines parameter values used by the FormsServlet (frmservlet)
# This section defines the Default settings. Any of them may be overridden in the
# following Named Configuration sections. If they are not overridden, then the
# values here will be used.
# The default settings comprise two types of parameters: System parameters,
# which cannot be overridden in the URL, and User Parameters, which can.
# Parameters which are not marked as System parameters are User parameters.
# SYSTEM PARAMETERS
# These have fixed names and give information required by the Forms
# Servlet in order to function. They cannot be specified in the URL query
# string. But they can be overridden in a named configuration (see below).
# Some parameters specify file names: if the full path is not given,
# they are assumed to be in the same directory as this file. If a path
# is given, then it should be a physical path, not a URL.
# USER PARAMETERS
# These match variables (e.g. %form%) in the baseHTML file. Their values
# may be overridden by specifying them in the URL query string
# (e.g. "http://myhost.mydomain.com/forms/frmservlet?form=myform&width=700")
# or by overriding them in a specific, named configuration (see below)
[default]
# System parameter: default base HTML file
baseHTML=base.htm
# System parameter: base HTML file for use with JInitiator client
baseHTMLjinitiator=basejini.htm
# System parameter: base HTML file for use with Sun's Java Plug-In
baseHTMLjpi=basejpi.htm
# System parameter: delimiter for parameters in the base HTML files
HTMLdelimiter=%
# System parameter: working directory for Forms runtime processes
# WorkingDirectory defaults to <oracle_home>/forms if unset.
workingDirectory=
# System parameter: file setting environment variables for the Forms runtime processes
envFile=default.env
# Forms runtime argument: whether to escape certain special characters
# in values extracted from the URL for other runtime arguments
escapeparams=true
# Forms runtime argument: which form module to run
form=test.fmx
# Forms runtime argument: database connection details
userid=
# Forms runtime argument: whether to run in debug mode
debug=no
# Forms runtime argument: host for debugging
host=
# Forms runtime argument: port for debugging
port=
# Other Forms runtime arguments: grouped together as one parameter.
# These settings support running and debugging a form from the Builder:
otherparams=buffer_records=%buffer% debug_messages=%debug_messages% array=%array% obr=%obr% query_only=%query_only% quiet=%quiet% render=%render% record=%record% tracegroup=%tracegroup% log=%log% term=%term%
# Sub argument for otherparams
buffer=no
# Sub argument for otherparams
debug_messages=no
# Sub argument for otherparams
array=no
# Sub argument for otherparams
obr=no
# Sub argument for otherparams
query_only=no
# Sub argument for otherparams
quiet=yes
# Sub argument for otherparams
render=no
# Sub argument for otherparams
record=
# Sub argument for otherparams
tracegroup=
# Sub argument for otherparams
log=
# Sub argument for otherparams
term=
# HTML page title
pageTitle=Oracle Application Server Forms Services
# HTML attributes for the BODY tag
HTMLbodyAttrs=
# HTML to add before the form
HTMLbeforeForm=
# HTML to add after the form
HTMLafterForm=
# Forms applet parameter: URL path to Forms ListenerServlet
serverURL=/forms/lservlet
# Forms applet parameter
codebase=/forms/java
# Forms applet parameter
imageBase=DocumentBase
# Forms applet parameter
width=750
# Forms applet parameter
height=600
# Forms applet parameter
separateFrame=true
# Forms applet parameter
splashScreen=
# Forms applet parameter
background=
# Forms applet parameter
lookAndFeel=Oracle
# Forms applet parameter
colorScheme=teal
# Forms applet parameter
logo=
# Forms applet parameter
restrictedURLparams=HTMLbodyAttrs,HTMLbeforeForm,pageTitle,HTMLafterForm,log,allow_debug,allowNewConnections
# Forms applet parameter
formsMessageListener=
# Forms applet parameter
recordFileName=
# Forms applet parameter
serverApp=default
# Forms applet archive setting for JInitiator
archive_jini=frmall_jinit.jar
# Forms applet archive setting for other clients (Sun Java Plugin, Appletviewer, etc)
archive=frmall.jar
# Number of times client should retry if a network failure occurs. You should
# only change this after reading the documentation.
networkRetries=0
# Page displayed to Netscape users to allow them to download Oracle JInitiator.
# Oracle JInitiator is used with Windows clients.
# If you create your own page, you should set this parameter to point to it.
jinit_download_page=/forms/jinitiator/us/jinit_download.htm
# Parameter related to the version of JInitiator
jinit_classid=clsid:CAFECAFE-0013-0001-0022-ABCDEFABCDEF
# Parameter related to the version of JInitiator
jinit_exename=jinit.exe#Version=1,3,1,22
# Parameter related to the version of JInitiator
jinit_mimetype=application/x-jinit-applet;version=1.3.1.22
# Page displayed to users to allow them to download Sun's Java Plugin.
# Sun's Java Plugin is typically used for non-Windows clients.
# (NOTE: you should check this page and possibly change the settings)
jpi_download_page=http://java.sun.com/products/archive/j2se/1.4.2_06/index.html
# Parameter related to the version of the Java Plugin
jpi_classid=clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA
# Parameter related to the version of the Java Plugin
jpi_codebase=http://java.sun.com/products/plugin/autodl/jinstall-1_4_2-windows-i586.cab#Version=1,4,2,06
# Parameter related to the version of the Java Plugin
jpi_mimetype=application/x-java-applet;jpi-version=1.4.2_06
# EM config parameter
# Set this to "1" to enable Enterprise Manager to track Forms processes
em_mode=0
# Single Sign-On OID configuration parameter
oid_formsid=%OID_FORMSID%
# Single Sign-On OID configuration parameter
oracle_home=D:\Forms
# Single Sign-On OID configuration parameter
formsid_group_dn=%GROUP_DN%
# Single Sign-On OID configuration parameter: indicates whether we allow
# dynamic resource creation if the resource is not yet created in the OID.
ssoDynamicResourceCreate=true
# Single Sign-On parameter: URL to redirect to if ssoDynamicResourceCreate=false
ssoErrorUrl=
# Single Sign-On parameter: Cancel URL for the dynamic resource creation DAS page.
ssoCancelUrl=
# Single Sign-On parameter: indicates whether the url is protected in which
# case mod_osso will be given control for authentication or continue in
# the FormsServlet if not. It is false by default. Set it to true in an
# application-specific section to enable Single Sign-On for that application.
ssoMode=false
# The parameter allow_debug determines whether debugging is permitted.
# Administrators should set allow_debug to "true" if servlet
# debugging is required, or to provide access to the Forms Trace Xlate utility.
# Otherwise these activities will not be allowed (for security reasons).
allow_debug=false
# Parameter which determines whether new Forms sessions are allowed.
# This is also read by the Forms EM Overview page to show the
# current Forms status.
allowNewConnections=true
# EndUserMonitoring
# EndUserMonitoringEnabled parameter
# Indicates whether EUM/Chronos integration is enabled
EndUserMonitoringEnabled=
# EndUserMonitoringURL
# indicates where to record EUM/Chronos data
EndUserMonitoringURL=
# Example Named Configuration Section
# Example 1: configuration to run forms in a separate browser window with
# "generic" look and feel (include "config=sepwin" in the URL)
# You may define your own specific, named configurations (sets of parameters)
# by adding special sections as illustrated in the following examples.
# Note that you need only specify the parameters you want to change. The
# default values (defined above) will be used for all other parameters.
# Use of a specific configuration can be requested by including the text
# "config=<your_config_name>" in the query string of the URL used to run
# a form. For example, to use the sepwin configuration, your could issue
# a URL like "http://myhost.mydomain.com/forms/frmservlet?config=sepwin".
[sepwin]
separateFrame=True
lookandfeel=Generic
# Example Named Configuration Section
# Example 2: configuration forcing use of the Java Plugin in all cases (even if
# the client browser is on Windows)
[jpi]
baseHTMLJInitiator=basejpi.htm
# Example Named Configuration Section
# Example 3: configuration running the Forms ListenerServlet in debug mode
# (debug messages will be written to the servlet engine's log file).
[debug]
serverURL=/forms/lservlet/debug
# Sample configuration for deploying WebUtil. Note that WebUtil is shipped with
# DS but not AS and is also available for download from OTN.
[webutil]
WebUtilArchive=frmwebutil.jar,jacob.jar
WebUtilLogging=off
WebUtilLoggingDetail=normal
WebUtilErrorMode=Alert
WebUtilDispatchMonitorInterval=5
WebUtilTrustInternal=true
WebUtilMaxTransferSize=16384
baseHTMLjinitiator=webutiljini.htm
baseHTMLjpi=webutiljpi.htm
archive_jini=frmall_jinit.jar
archive=frmall.jar
lookAndFeel=oracle
Best Regards

Random workstation proxy issue

Haven't been able to figure this one out. Sometimes our workstation will stop accessing the internet. You can ping, and do all of that just fine, but when the proxy address and port are enable in IE8/Firefox, it just sits there loading the page, but never does. If you disable the proxy, then it will begin loading pages so it's proxy settings specific.
This is only for the problem machines. There's 1100+ other stations that use the proxy fine.

Originally Posted by phxazcraig
In article <[email protected]>, Seth turner
04 wrote:
> Well I gave the workstation a different IP and it started working fine.
> Sounds like you were right on the duplicate IP thing.
So that w/s was the only one with an issue?
>
> I checked the nwconfig and it says it has Border Manager 3.8.4.
>
Check tip #1 at the URL below.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to Craig Johnson Consulting - BorderManager, NetWare, and More ***
Just to update....our Border Manager server went down last Monday and ever since then we've had this issue start happening again, but a lot worse. Earlier today, one of the computers labs had ten systems start doing this all at the same time.
We just applied the proxy.cfg settings, and unloaded and loaded the proxy but that had no effect. We are going to run the tuneup.ncf file later on and see if that has any effect.

Proxy Cache/sizing

Looking at our proxy console we see the cache is only holding files for about 30-60 minutes, 30% hits. This figure is the same for two different caching configurations:
proxyserver1:Aging=default, Control HashT=1024, HotNodes=66000, Location=3 12GB Trad.volumes, 512 dirs.
proxyserver2:Aging=7d,6h,20m,7d,7d,0m,30m, Control http=450MB, HashT=256, HotNodes=50000, Location=3 12GB Trad.volumes, 384 dirs.
Any suggestions for better caching on these two very busy servers with 2000-6000 connections, ~500 fills in progress?
Marco

In article <[email protected]>, Marcoba wrote:
> Any suggestions for better caching on these two very busy servers with
> 2000-6000 connections, ~500 fills in progress?
>
The caching you are seeing may be dependent on the maximum hot
unreferenced time (default=30 minutes, Novell recommends upping to 60).
You have to balance that setting against the maximum hot nodes you are
hitting. (You never want to hit that maximum, or the server will really
seem slow). Max hot nodes default=7000 (way to low, Novell recommends
raising to 50,000 and I think the max is 60,000. This is dependent on a
max file lock settings of 100,000, which I have in my tuneup.ncf file in
tip #23 at the URL below).
The cache percent is actually not bad - most of the servers using my
proxy.cfg (tip #63) end up with a cache hit percent in the teens,
because I tell the proxy not to cache sites with cookies. (I've seen
that cause issues with sites that use cookie-based passwords).
You need to balance max hot nodes with max hot unreferenced time, RAM
and sheer speed of disk I/O. The most critical thing I have seen is to
make sure you never hit the max hot nodes. I view the tuning as partly
an exercise for keeping under the maximum. On really busy servers with
fast internet connections I've had to lower the max hot unreferenced
time to have the proxy begin releasing hot nodes earlier so it doesn't
max out.
If you are really busy, you might just consider setting up another proxy
and load-balancing between them.
Craig Johnson
Novell Knowledge Partner
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Proxy.cfg skipAuthForViaHeader parameter

Similar Messages

Maybe you are looking for