Configuration file descriptions
Look up a configuration file by its name, to find details about the syntax and usage of the file.
The server configuration interfaces are documented separately. You can also search for configuration files descriptions using keywords.
Subtopics
app.policy file permissions
Java™ 2 security uses several policy files to determine the granted permissions for each Java program. The union of the permissions that are contained in these following files is applied to the WebSphere® Application Server enterprise application. This union determines the granted permissions.Applet client security requirements
When code is loaded, it is assigned permissions based on the security policy in effect. This policy specifies the permissions that are available for code from various locations. You can initialize this policy from an external policy file.cacheinstances.properties file
Use the information in this document as a reference of the names, values, and explanations that you can use in the cacheinstances.properties file.cachespec.xml file
The cache parses the cachespec.xml file when the server starts, and extracts a set of configuration parameters from each cache-entry element. Every time a new servlet or other cacheable object initializes, the cache attempts to match each of the cache-entry elements to find the configuration information for that object.Contexts and Dependency Injection custom properties
WebSphere Application Server traditional Contexts and Dependency Injection (CDI) implementation is based on OpenWebBeans, which is configurable through the openwebbeans.properties file.client.policy file permissions
Java 2 security uses several policy files to determine the granted permission for each Java program.Client application Java Network Launcher Protocol deployment descriptor file
The deployment descriptor file is the main Java Network Launcher Protocol (JNLP) descriptor file for the client application.Common Base Event structure
A Common Base Event is a common structure for an event. It defines common fields, the values that these fields can take, and the exact meanings of these values for an event.Configuration document descriptions
Most configuration documents have XML content. The table describes the documents and states whether you can edit them using an administrative tool or must edit them directly.Embeddable EJB container configuration properties
Use the following configuration properties for the embeddable Enterprise JavaBeans (EJB) container.filter.policy file permissions
Java 2 security uses several policy files to determine the granted permission for each Java program. Java 2 security policy filtering is only in effect when Java 2 security is enabled.groups.props file
The following example illustrates the format for the groups.props file.ibm-webservicesclient-bnd.xmi assembly properties for JAX applications
The ibm-webservicesclient-bnd.xmi deployment descriptor file contains information for the web services run time that is WebSphere product-specific. This deployment descriptor file is used with Java API for XML-based web services.java.policy file permissions
Java 2 security uses several policy files to determine the granted permission for each Java program.Java 2 security policy files
The Java 2 Platform, Enterprise Edition (J2EE) Version 1.3 and later specifications have a well-defined programming model of responsibilities between the container providers and the application code. Using Java 2 security manager to help enforce this programming model is recommended. Certain operations are not supported in the application code because such operations interfere with the behavior and operation of the containers. The Java 2 security manager is used in the product to enforce responsibilities of the container and the application code.JAX-RPC web services enabled module - deployment descriptor settings (ibm-webservices-bnd.xmi file)
The ibm-webservices-bnd.xmi file is a deployment descriptor for a Java API for XML-based RPC (JAX-RPC) web services-enabled web module or an Enterprise JavaBeans (EJB) module. This file contains information for the web services run time that is required by WebSphere Application Server..JNLP descriptor file for a Java EE Application client application
The deployment descriptor file is the main Java Network Launcher Protocol (JNLP) descriptor file for the client application.JNLP descriptor file for a Thin Application client application
The deployment descriptor file is the main Java Network Launcher Protocol (JNLP) descriptor file for the client application. If it is a Thin Application client application, then the launcher class uses the current JVM from the Application Clients run-time dependency and invokes the Thin Application client application main method.library.policy file permissions
Java 2 security uses several policy files to determine the granted permission for each Java program.Logger.properties file
Use the Logger.properties file to set logger attributes for your component.Logger.properties file for configuring logger settings
Use the Logger.properties file to set logger attributes for specific loggers.Lotus Domino file locations and troubleshooting tips
Lotus® Domino® Server is one of the Web servers that WebSphere Application Server supports. You must be aware of configuration file locations and other useful tips related to using Lotus Domino.OAuth MBeans
You can manage an OAuth configuration by using MBean programming.plugin.xml file
A plug-in is described in an XML manifest file, called plugin.xml, which is part of the plug-in deployment files. The manifest file tells the portal application’s runtime what it needs to know to register and activate the plug-in. The manifest file essentially serves as the contract between the pluggable component and the portal application’s runtime. Although the WebSphere Application Server plugin.xml closely follows the one provided for the Eclipse workbench, it does diverge from the Eclipse workbench in several places.plugin-cfg.xml file
The plugin-cfg.xml file contains configuration information that determines how the web server plug-in forwards requests.Product library, directories, subsystem, job queue, job description, and output queues
An IBM® i platform uses different configurations than installations of WebSphere Application Server on other platforms.rrdSecurity.props file
Remote request dispatcher (RRD) supports LTPA and security attribute propagation for Web Services Security (WS-Security). You can enable token propagation in the <was_install>/profiles/<profileName>/properties/rrdSecurity.props file.SAML Issuer Config Properties
When creating a new self-issued SAML token, you can specify configuration properties to control how the token is configured. The configuration properties are name/value pairs that describe provider-side information such as the issuer location, and the keystore and trust store file paths.server.policy file permissions
Java 2 security uses several policy files to determine the granted permission for each Java program.SMF record type 120: overview
Information resulting from the SMF data gathering process for WebSphere Application Server for z/OS® is held in SMF record type 120.SOAP connector and Inter-Process Communications connector properties files
Use the soap.client.props file to set properties for the SOAP connector and the ipc.client.props file to set properties for the Inter-Process Communications (IPC) connector. Most of the properties in the ipc.client.props file have corresponding properties in the soap.client.props file.spi.policy file permissions
Java 2 security uses several policy files to determine the granted permission for each Java program.ssl.client.props client configuration file
Use the ssl.client.props file to configure Secure Sockets Layer (SSL) for clients. In previous releases of WebSphere Application Server, SSL properties were specified in the sas.client.props or soap.client.props files or as system properties. By consolidating the configurations, WebSphere Application Server enables you to manage security in a manner that is comparable to server-side configuration management. You can configure the ssl.client.props file with multiple SSL configurations.The client_types.xml file
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.The Kerberos configuration file
The Kerberos configuration properties, krb5.ini or krb5.conf files, must be configured on every WebSphere Application Server instance in a cell in order to use the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) trust association interceptor (TAI) for WebSphere Application Server.Timeout conditions: analyzing diagnostic data
The following guidelines provide instructions for finding diagnostic data in an SVC dump that can help you determine what timeout condition occurred.Timeout values: guidelines for altering timeout values
This file lists common timer variables and tools for monitoring these timeout conditionsTransaction class mapping file entries
Transaction class mapping file entries indicate the workload management (WLM) goal for each class of client work. Each client transaction is dispatched in its own WLM enclave in a servant region process, and is managed according to the goals specified for its service class.users.props file
This example presents the format for the users.props file.web.xml file
The web.xml file provides configuration and deployment information for the web components that comprise a web application.Web container configuration for JavaServer Pages static file access
Web server configuration file
Use this page to view or modify the contents of the Web server configuration file in your web browser. To view this administrative console page click Servers > Server Types > Web Servers > web_server_name. Under Additional Properties, click Configuration File.Web server plug-in custom properties
If you are using a web server plug-in, you can add one or more of the following custom properties to the configuration settings for that plug-in.wsif.properties file - Initial contents
The Web Services Invocation Framework (WSIF) properties are stored in the com.ibm.ws.runtime.jar file, in a properties file named wsif.properties. You might have to modify the contents of this file, for example to change the default SOAP provider, so for reference here is a copy of the "as shipped" contents of the wsif.properties file.ws-security.xml file - Default configuration for WebSphere Application Server, Network Deployment
For JAX-RPC applications, WebSphere Application Server, Network Deployment installation uses the ws-security.xml file to define the default binding information for Web Services Security for an entire cell.


File name: welc_ref_adm_file.html