ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzatz_5.4.0.1/51/admin/refprop.htm

96 lines
6.1 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
<title>Properties files</title>
</head>
<BODY>
<!-- Java sync-link -->
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
<h3><a name="refprop"></a>Properties files</h3>
<p>Each instance of WebSphere Application Server - Express contains several properties files. The files in the properties directory for an instance are not managed by the administrative repository and file replication services. The properties files are located in the /QIBM/UserData/WebASE51/ASE/<em>instance</em>/properties directory, where <em>instance</em> is the name of your instance.</p>
<ul>
<!-- <li><p>cachespec.sample.xml<br>
This is a sample dynamic cache file.</p></li> -->
<li><p>client.policy<br>
The client.policy file is a default policy file shared by all of the WebSphere client containers and applets on a node.</p></li>
<li><p>client_types.xml<br>
The client_types.xml file provides client type detection support for servlets extending PageListServlet. Using the configuration data in the client_types.xml file, servlets can determine the language type that calling clients require for the response.</p></li>
<li><p>converter.properties<br>
The converter.properties file is used by the Web container to map an unsupported character set to a supported character set.</p></li>
<li><p>encoding.properties<br>
The encoding.properties file is used by the Web container to map the language identifier to a character set.. This file is used only if the Web container determines the locale for a request using the Accept-Language HTTP header. </p></li>
<li><p>ffdcRun.properties<br>
Properties file used to specify settings for the WebSphere Application Server - Express First Failure Data Capture (FFDC) diagnostic engine. This file should only be changed when working with IBM Service personnel to do problem determination.</p></li>
<li><p>ffdcStart.properties<br>
Properties file used to specify settings for starting the WebSphere Application Server - Express First Failure Data Capture (FFDC) diagnostic engine. This file should only be changed when working with IBM Service personnel to do problem determination.</p></li>
<li><p>ffdcStop.properties<br>
Properties file used to specify settings for stopping the WebSphere Application Server - Express First Failure Data Capture (FFDC) diagnostic engine. This file should only be changed when working with IBM Service personnel to do problem determination.</p></li>
<li><p>implfactory.properties<br>
File for specifying implementation classes for WebSphere Application Server - Express runtime factories. This file should only be modified under the direction of IBM Service personnel.</p></li>
<li><p>java.security<br>
The java.security file is used to specify various security properties for use by the java.security classes. WebSphere Application Server - Express uses this file instead of the java.security file located in the /QIBM/ProdData/Java400/jdk13/lib/security directory. If you wish to add security properties for your WebSphere Application Server - Express instance, you should modify this file in the properties directory for your instance.</p></li>
<li><p>jmx.properties<br>
This is a configuration file that controls logging within the JMX environment. This file should only be modified under the direction of IBM Service personnel.</p></li>
<li><p>samples.properties<br>
This file provides a list of the samples that are installed on your application server.</p></li>
<li><p>sas.client.props<br>
The sas.client.props file contains the configuration settings for authentication between a Java client and a server.</p></li>
<li><p>sas.server.props<br>
In WebSphere Application Server versions 4.0 and earlier, this file contained configuration settings for all application servers in an instance. In WebSphere Application Server - Express, these properties are specified in the security.xml file. The sas.server.props file maps the values from previous versions to the XML values specified in the current version's security.xml file.</p></li>
<li><p>sas.stdclient.properties<br>
This file contains the default configuration settings for a secure Java client that requires a userid and password via standard input from the command line.</p></li>
<li><p>sas.tools.properties<br>
This file contains the default configuration settings for a secure Java client that requires a userid and password via standard input from the command line.</p></li>
<li><p>server.policy<br>
The server.policy file is a default policy file shared by all of the application servers on a node. The permissions in this file only pertain to the WebSphere Application Server - Express runtime code.</p></li>
<li><p>soap.client.props<br>
This file contains configuration settings for authentication between a SOAP client and a server.</p></li>
<li><p>sslbitsizes.properties<br>
This file contains properties associating SSL cipher suites to their bit sizes. </p></li>
<li><p>TraceSettings.properties<br>
The TraceSettings.properties file is used to specify trace settings for client applications.</p></li>
<li><p>was.policy<br>
Sometimes an application requires additional authentication information that is not specified in the app.policy file. The additional information is specified in the was.policy file.</p></li>
<li><p>wsadmin.properties<br>
Contains properties used by the <a href="wsa.htm">wsadmin command line administration tool</a>.</p></li>
<li><p>wsjaas.conf<br>
Contains configuration settings for the Java Authentication and Authorization Service (JAAS).</p></li>
<li><p>wsjaas_client.conf<br>
Contains configuration settings for the Java Authentication and Authorization Service (JAAS) for client applications.</p></li>
<li><p>wsserver.key<br>
Contains example configuration settings for allowing an application server to log on and access resources on a secure z/OS server.</p></li>
</ul>
</body>
</html>