- 浏览: 406107 次
- 性别:
- 来自: 郑州
文章分类
最新评论
-
yan789654100:
先谢谢了,去研究一下
Java网络围棋游戏源码含大厅,仿QQ游戏 -
dan0773:
火狐里面用不了
梅花雨日历控件源码,及应用实例 -
左手边:
挺好的不错
Velocity教程 -
liuxuejin:
既然是教程,连个例子都没有!顶多是个笔记而已
Velocity教程 -
sky_pearl:
泪奔……求大厅代码!!!
Java网络围棋游戏源码含大厅,仿QQ游戏
WAS 5.1 部署应用容器属性配置
引用地址:http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//topic/com.ibm.websphere.base.doc/info/aes/ae/uweb_custom_settings.html
Web container custom properties
Use this page to configure arbitrary name-value pairs of data, where the name is a property key and the value is a string value that you can use to set internal system configuration properties. Defining a new property enables you to configure a setting beyond that which is available in the administrative console.
To view this administrative console page, click Servers > Application servers > server_name > Web container settings > Web container > Custom properties.
To specify Web container custom properties:
- In the administrative console click Servers > Application Servers > server_name > Web Container settings > Web Container
- Under Additional Properties select Custom Properties.
- On the Custom Properties page, click New.
- On the settings page, enter the name of the custom property that you want to configure in the Name field and the value that you want to set it to in the Value field.
- Click Apply or OK.
- Click Save on the console task bar to save your configuration changes.
- Restart the server.
HTTP Transport custom properties can also be set at the Web container level. See HTTP transport custom properties for a description of these properties.
Data type | String |
Data type | String |
Global settings for internal servlets
Web application archive (WAR) files that are packaged using third-party tools cannot specify behavior for the services that are exposed by the Web container internal servlets. You can globally enable and disable internal servlets for all Web applications at the Web container level by creating name-value pairs such as:
Name | Value |
fileServingEnabled | true |
directoryBrowsingEnabled | true |
serveServletsByClassnameEnabled | true |
Settings that are defined in an assembly tool take precedence over the global settings that are set through the custom properties at the Web container level.
Web application deployment extensions continue to hold configuration information for the services that are provided by the internal servlets, and take precedence over the global settings that are set through the custom properties at the Web container level.
Disallow the use of the serving servlets by class name
When the serveServletsByClassnameEnabled property is enabled, it is possible to access servlets directly, resulting in a possible security exposure. Define the following custom property to disallow the use of the serveServletsByClassnameEnabled property across the entire application server level.
Name | Value |
com.ibm.ws.webcontainer.disallowserveservletsbyclassname | true |
Defining classes that cannot be served by class name
The com.ibm.ws.webcontainer.donotservebyclassname custom property specifies a list of classes that cannot be served by the class name.
Name | Value |
com.ibm.ws.webcontainer.donotservebyclassname | A semi-colon delimited list of classes to be completely disallowed from being served by class name. |
UTF-8 encoded URLs
The UTF-8 encoded URL feature, which provides UTF-8 encoded Uniform Resource Locators (URLs) to support the double-byte characters in URLs is enabled by default. You can prevent the Web container from explicitly decoding URLs in UTF-8 and have them use the ISO-8859 standard as per the current HTTP specification by using the following name-value pair:
Name | Value |
DecodeUrlAsUTF8 | false |
Global configuration of servlet listeners
The servlet specification supports applications registering listeners for servlet-related events on an individual application basis through the web.xml descriptor. However, using the listeners custom property, a server can listen to servlet events across Web applications. To implement global listening, a listener is registered at the Web container level and is propagated to all of the installed and new Web applications. This global behavior of internal servlet listeners is controlled by the listeners custom property by using the following name-value pair format:
Name | Value |
listeners | listener_class |
The values for this property is a string specifying a comma separated list of listener classes. The listener supplied must implement standard listener classes from the Java Servlet API or IBM listener extension classes.
Binary Large Object (BLOB) data type for Oracle databases
The UseOracleBLOB custom property creates the HTTP session database table using the Binary Large Object (BLOB) data type for the medium column. This property increases performance of persistent sessions when Oracle databases are used. Due to an Oracle restriction, BLOB support requires use of the Oracle's oci database driver for more than 4000 bytes of data. You must also ensure that a new sessions table is created before the server is restarted by dropping your old sessions table or by changing the datasource definition to reference a database that does not contain a sessions table. To create a sessions table using the BLOB data type, use the following name-vaule pair:
Name | Value |
UseOracleBLOB | true |
Detecting Session Data Crossover
The DebugSessionCrossover custom property enables code to perform additional checks to verify that only the session associated with the request is accessed or referenced. Messages are logged if any discrepancies are detected. To enable session data crossover detection, use the following name-value pair:
Name | Value |
DebugSessionCrossover | true |
See article, Problems creating or using HTTP sessions, for additional information.
ForceSessionInvalidationMultiple
The ForceSessionInvalidationMultiple custom property indicates whether the session manager should wait indefinitely for a request to complete before attempting to invalidate the session, or should attempt to invalidate a session after the specified time limit has elapsed. The default value for this property is 1.
- If you specify 0 (zero) for this custom property, the session manager waits indefinitely until a request is complete before attempting to invalidate the session.
If your requests normally are not bound by a response time limit, you should specify 0 for this property.
- If you specify a positive integer, such as 1, 2, or 3, for this custom property, even if a session is not known to have completed, the session manager attempts to invalidate the session, if the indicated time period since the last access occurred has elapsed. This time period is the result of multiplying the value specified for this property and the value specified for the Session Timeout property. For example, if you specify 2 minutes for the Session Timeout property and 2 for the ForceSessionInvalidationMultiple property, the session manager will attempt to invalidate the session after 4 minutes.
If you want to invalidate your sessions after a certain amount of time has elapsed, specify the appropriate positive integer for this property.
Name | Value |
ForceSessionInvalidationMultiple | 1 |
HTTPS requests with an SSL offloader
The custom property httpsIndicatorHeader manages HTTPS requests that are forwarded to an application server from an SSL offloader that is used in front of WebSphere Application Server. When an HTTPS request is received by a SSL offloader it is redirected over HTTP to an application server using WebSphere Application Server. The SSL offloader adds a header indicating the original request was over HTTP. The httpsIndicatorHeader property specifies the header name added by the SSL box. The application server checks this indicator to determine if SSL is required. If it determines the request is SSL over HTTP, an HTTPS scheme is chosen.
Name | Value |
httpsIndicatorHeader | Request header key name |
HttpSessionIdReuse
The custom property HttpSessionIdReuse determines whether the session manager can use the session ID sent from a browser to preserve session data across Web applications that are running in an environment that is not configured for session persistence. In a multi-JVM environment that is not configured for session persistence setting this property to true enables the session manager to use the same session information for all of a user's requests even if the Web applications that are handling these requests are governed by different JVMs. The default value for this property is false. To enable the session manager ton use the session ID sent from a browser to preserve session data across Web applications that are running in an environment that is not configured for session persistence, use the following name-value pair:
Name | Value |
HttpSessionIdReuse | true |
Optimizing web services client to Web container communication
To improve performance, there is an optimized communication path between a Web services client application and a Web container that are located in the same application server process. Requests from the Web services client that are normally sent to the Web container using a network connection are delivered directly to the Web container using an optimized local path. The local path is available because the Web services client application and the Web container are running in the same process. This optimized communication path is disabled by default. Before enabling this property, make sure that wild cards are not specified for the Web container ports. Use specific ports for the web container when the optimized communication path is enabled. To enable the optimized communication path, use the following name-value pair:
Name | Value |
enableInProcessConnections | true |
Returning the port number from the request host header first
The getServerPort method relies on the getVirtualPort method of the channel, which returns a port number in the following order:
- Port number from the request URL
- Port number from the request host header
trusthostheaderport = true com.ibm.ws.webcontainer.extractHostHeaderPort = true
Or you can set these properties as Web container custom properties in the administrative console using the following two sets of name-value pairs:
Name | Value |
com.ibm.ws.webcontainer.extractHostHeaderPort | true |
trusthostheaderport | true |
发表评论
-
Extjs 验证使用
2012-08-10 10:16 953/** * 用户表单面板 */ Ext.def ... -
使用ext的store.load 之后然后使用store.getCount 值为零解决办法
2012-07-13 09:12 1172使用ext的store.load(),之后然后使用store. ... -
什么样的cms系统算是强大
2012-07-10 17:41 954现在建站的cms系统层出不穷。从简单的到功能复杂的。从功 ... -
OpenCV背景去除的几种方法(转)
2012-07-02 10:15 8544OpenCV背景去除的几种方法 1、肤色侦测法 肤 ... -
error: command 'mt.exe' failed with exit status 31
2012-06-18 17:39 2374python setup.py build_ext -i ... -
MyBatis 3 + Spring3 多数据源配置
2012-02-27 14:50 1347详细内容地址: 终于把 MyBatis 3 和 Sp ... -
Google Earth 开发示例(Hello World)
2011-04-13 17:06 1592Google Earth Hello World 示例 &l ... -
DB2 分页查询方法,查询top N 条记录
2011-01-13 18:50 27101. db2分页查询sql select * f ... -
Birt 中的通过Script加入调试输出SQL语句代码
2010-11-18 15:54 1364用Brit制作报表时可通过在Script脚本中加入以下代码输出 ... -
TSM - Creating an include-exclude list (optional)
2010-06-09 11:00 1522Creating an include-exclude l ... -
TSM - Configuring the Web client
2010-06-09 10:51 892Configuring the Web client The ... -
Linux下 Tsm 服务器、客户端安装配置全过程
2010-05-17 10:06 1716系统环境:LINUX AS5 存储:IBM DS400 ... -
安装DB2补丁步骤
2009-10-27 17:30 17281. 通过运行 su - root ... -
WAS 6.0.2.9 部署应用使用过滤器问题解决办法
2009-08-05 16:07 1403支撑环境: IBM WebSphere Application ... -
MyEclipse5.5GA配置Websphere V6.1 全过程(详细版)
2009-07-16 13:32 1248转载自:http://blog.chinaunix.net/u ... -
WebSphere Application Server 6.0.2.9 配置 SqlServer 2000 SP2时出错问题解决
2009-07-15 12:56 1757WebSphere Application Server 6. ... -
Struts JSR168 Portlet using the ITIM API
2009-06-02 19:29 953Leveraging the IBM Tivoli Ident ... -
ITIM API
2009-06-02 19:22 910ITIM API http://publib.boulder ... -
打开IBM WebSphere Portal trace 收集
2009-05-26 10:37 1394Collecting login-specific infor ... -
解决HP-UX 11iv3 nfs 共享时无法写文件问题方法
2009-05-14 17:21 1895解决在两台HP小机上用SAM 配置的NFS 共享之后,moun ...
相关推荐
本文主要是讲述在redhat linux下安装websphere5.1,其中用截图方式描述了主要的配置过程。
WAS 5.1 ND安装手册pdf ,格式,欢迎下载
was部署应用方法
关于NC应用was部署失败的处理 关于NC应用was部署失败的处理 关于NC应用was部署失败的处理
was应用服务器部署、调优、JNDI配置、应用平台部署;IHS部署
was集群部署方案及安装配置手册
was 服务器 部署应用的方法,步骤,详细文字配图片,亲测可用
was应用服务器项目部署,步骤详细含图片
IBM WAS 自动部署脚本,方便实现无人值守部署J2EE应用
was6.1 上部署Web应用程序详解(图) 1、 数据库连接池配置 通过WebSphere配置数据库连接池一共需要三项: 1.配置连接驱动,在这里叫:JDBC提供程序; 2.配置数据库连接池,在这里叫:配置数据源; 3.配置数据库登录帐号...
WAS最新版本was9集群部署,使用IHS转发请求,文档详细有截图,有命令,基于Linux + WAS8.5安装、部署过程 _WIN7 64位系统安装部署文档 。+ WAS9 集群 & IBM HTTP Server 9 部署文档
在IBM WAS ND产品中,管理配置数据都存储在 XML 文件中。单元保留了它每个节点中每台服务器的主配置文件。同时每个节点和服务器也有其自己的本地配置文件。如果服务器已经属于单元,则对于本地节点或服务器配置文件...
该文档用于解决在websphere application server 服务部署程序过程中会出现jar包冲突问题
was8.5 部署cxf demo
WAS_7.0之分布式平台安装配置与应用部署
该文档为was7.0版本详细的服务器安装配置及应用服务包部署指导以及简单的日志定位排错指导。
文档包含was的详细部署步骤和一些技术手册,主要用于was的部署
自己手写的文档,需要的可以下载一下。was的安装和部署以及一些可能遇到的问题.doc
网上找这个WebSphere(was)中间件或者应用服务器的相关资料还是挺少的。这里是一份关于was如何配置https证书,实现https访问的教程。
NC-was集群部署,主要是用友NC系统的IBMwas集群的安装部署文档