Oracle WebLogic ServerのRESTfulサーバー構成管理インタフェース

コピー{
    "type":"object",
    "properties":{
        "JSPCompilerBackwardsCompatible":{
            "default":false,
            "type":"boolean",
            "description":"<p>Global property to determine the behavior of the JSP compiler. When this property set to \"true\", the JSP compiler throws a translation error for JSPs that do not conform to the JSP2.0 specification. This property exists for backward compatibility.</p>"
        },
        "WAPEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Indicates whether the session ID should include JVM information. (Checking this box may be necessary when using URL rewriting with WAP devices that limit the size of the URL to 128 characters, and may also affect the use of replicated sessions in a cluster.) When this box is selected, the default size of the URL will be set at 52 characters, and it will not contain any special characters.</p>"
        },
        "XPoweredByHeaderLevel":{
            "default":"NONE",
            "enum":[
                "NONE",
                "SHORT",
                "MEDIUM",
                "FULL"
            ],
            "type":"string",
            "description":"<p> WebLogic Server uses the X-Powered-By HTTP header, as recommended by the Servlet 3.1 specification, to publish its implementation information.</p><p></p><p> Following are the options: </p><ul><li><p>\"NONE\" (default):  X-Powered-By header will not be sent </p></li><li><p>\"SHORT\":           \"Servlet/3.1 JSP/2.3\"  </p></li><li><p>\"MEDIUM\":          \"Servlet/3.1 JSP/2.3 (WebLogic/12.2)\" </p></li><li><p>\"FULL\":            \"Servlet/3.1 JSP/2.3 (WebLogic/12.2 JDK/1.8)\" </p></li></ul>"
        },
        "allowAllRoles":{
            "x-weblogic-secureDefault":false,
            "default":false,
            "type":"boolean",
            "description":"<p>In the security-constraints elements defined in a web application's web.xml deployment descriptor, the auth-constraint element indicates the user roles that should be permitted access to this resource collection. Here role-name = \"*\" is a compact syntax for indicating all roles in the Web application. In previous releases, role-name = \"*\" was treated as all users/roles defined in the realm.</p><p>This parameter is a backward-compatibility switch to restore old behavior. Default behavior is one required by the specification, meaning all roles defined in the web application.</p><p>If set, the value defined in weblogic.xml (container-descriptor -> allow-all-roles) takes precedence (if set) over this value. </p><p><h5>Constraints</h5></p><ul><li>secure default : false</li></ul>"
        },
        "authCookieEnabled":{
            "x-weblogic-secureDefault":true,
            "default":true,
            "type":"boolean",
            "description":"<p>Specifies whether the AuthCookie feature is enabled or not.</p><p><h5>Constraints</h5></p><ul><li>secure default : true</li></ul>"
        },
        "changeSessionIDOnAuthentication":{
            "default":true,
            "type":"boolean",
            "description":"<p>Global property to determine if we need to generate a new SessionID after authentication. When this property is set to \"false\", the previous sessionID will be retained even after authorization. </p>"
        },
        "clientCertProxyEnabled":{
            "x-weblogic-secureDefault":false,
            "default":false,
            "type":"boolean",
            "description":"<p>Specifies whether or not to honor the WL-Proxy-Client-Cert header coming with the request. </p><p><h5>Constraints</h5></p><ul><li>secure default : false</li></ul>"
        },
        "dynamicallyCreated":{
            "readOnly":true,
            "default":false,
            "type":"boolean",
            "description":"<p>Return whether the MBean was created dynamically or is persisted to config.xml</p>"
        },
        "filterDispatchedRequestsEnabled":{
            "x-weblogic-secureDefault":false,
            "default":false,
            "type":"boolean",
            "description":"<p> Indicates whether or not to apply filters to dispatched requests. This is a backward compatibility flag. Until version 8.1, WebLogic Server applied ServletFilters (if configured for the web application) on request dispatches (and includes/forwards). Servlet 2.4 has introduced the \"Dispatcher\" element to make this behavior explicit. The default value is Dispatcher=REQUEST. In order to be compliant with the Java EE specification, the default value for FilterDispatchedRequestsEnabled is false beginning with WebLogic Server 9.0. Note that if you are using old descriptors (meaning web.xml does not have version=2.4), then WebLogic Server automatically uses FilterDispatchedRequestsEnabled = true for the web applications, unless filter-dispatched-requests-enabled is explicitly set to false in weblogic.xml. This means that old applications will work fine without any modification. Additionally, during migration of old domains to the 9.0 domain, the migration plug-in automatically sets this flag to true. </p><p><h5>Constraints</h5></p><ul><li>secure default : false</li></ul>"
        },
        "httpTraceSupportEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p> Returns the value of HttpTraceSupportEnabled. </p>"
        },
        "id":{
            "readOnly":true,
            "type":"integer",
            "format":"int64",
            "description":"<p>Return the unique id of this MBean instance</p>"
        },
        "jaxRsMonitoringDefaultBehavior":{
            "default":true,
            "type":"boolean",
            "description":"<p> Global property to determine the behavior of monitoring in JAX-RS applications. When the property is set to <code>true</code> (or not set) the monitoring is turned on (if not overridden by properties set directly in application). If the property is set to <code>false</code> the monitoring for all JAX-RS applications is disabled. </p>"
        },
        "maxPostSize":{
            "default":-1,
            "type":"integer",
            "format":"int32",
            "description":"<p>The maximum post size this server allows for reading HTTP POST data in a servlet request. A value less than 0 indicates an unlimited size.</p>"
        },
        "maxPostTimeSecs":{
            "default":-1,
            "type":"integer",
            "format":"int32",
            "description":"<p>Maximum post time (in seconds) for reading HTTP POST data in a servlet request. MaxPostTime < 0 means unlimited</p>"
        },
        "maxRequestParameterCount":{
            "default":10000,
            "type":"integer",
            "format":"int32",
            "description":"<p>The maximum request parameter count this server allows for reading maximum HTTP POST parameters count in a servlet request.</p><p></p><p>Gets the maxRequestParameterCount attribute of the WebServerMBean object.</p>"
        },
        "mimeMappingFile":{
            "default":"./config/mimemappings.properties",
            "type":"string",
            "description":"<p>Returns the name of the file containing mime-mappings for the domain.</p><p>The Format of the file should be: extension=mime-type </p><p> For Example:</p><p>htm=text/html</p><p>gif=image/gif</p><p>jpg=image/jpeg</p><p></p><p>If this file does not exist, WebLogic Server uses an implicit mime-mapping set of mappings defined in weblogic.utils.http.HttpConstants (DEFAULT_MIME_MAPPINGS). To remove a mapping defined in implicit map, set it to blank. </p>"
        },
        "name":{
            "readOnly":true,
            "x-weblogic-legalNull":true,
            "type":"string",
            "description":"<p>The user-specified name of this MBean instance.</p><p>This name is included as one of the key properties in the MBean's <code>javax.management.ObjectName</code></p><p><code>Name=<i>user-specified-name</i></code></p><p><h5>Constraints</h5></p><ul><li>legal null</li></ul>"
        },
        "notes":{
            "type":"string",
            "description":"<p>Optional information that you can include to describe this configuration.</p><p>WebLogic Server saves this note in the domain's configuration file (<code>config.xml</code>) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <code>&lt;</code>. Carriage returns/line feeds are preserved.</p><p>Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.</p>"
        },
        "optimisticSerialization":{
            "default":false,
            "type":"boolean",
            "description":"<p> When OptimisticSerialization is turned on, WebLogic Server does not serialize-deserialize context and request attributes upon getAttribute(name) when a request gets dispatched across servlet contexts. This means you will need to make sure that the attributes common to web applications are scoped to a common parent classloader (they are application-scoped) or placed in the system classpath if the two web applications do not belong to the same application. When OptimisticSerialization is turned off (which is the default), WebLogic Server does serialize-deserialize context and request attributes upon getAttribute(name) to avoid the possibility of ClassCastExceptions. The value of OptimisticSerialization can also be overridden for specific web applications by setting the optimistic-serialization value in weblogic.xml. </p>"
        },
        "overloadProtectionEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>This parameter is used to enable overload protection in the web application container against low memory conditions. When a low memory situation occurs, new session creation attempts will result in weblogic.servlet.SessionCreationException. The application code needs to catch this exception and take proper action. Alternatively appropriate error-pages can be configured in web.xml against weblogic.servlet.SessionCreationException. This check is performed only on memory and replicated sessions. </p>"
        },
        "p3PHeaderValue":{
            "type":"string",
            "description":"<p> Returns the P3P header value that will be sent with all responses for HTTP requests (if non-null). The value of this header points to the location of the policy reference file for the website.</p><p></p><p>Alternatively, a servlet filter can be used to set the P3P header.</p>"
        },
        "postTimeoutSecs":{
            "x-weblogic-secureDefault":30,
            "default":30,
            "minimum":0,
            "maximum":120,
            "type":"integer",
            "format":"int32",
            "description":"<p>The amount of time this server waits between receiving chunks of data in an HTTP POST data before it times out. (This is used to prevent denial-of-service attacks that attempt to overload the server with POST data.)</p><p><h5>Constraints</h5></p><ul><li>secure default : 30</li></ul>"
        },
        "reloginEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Beginning with the 9.0 release, the FORM/BASIC authentication behavior has been modified to conform strictly to the Java EE Specification. If a user has logged-in but does not have privileges to access a resource, the 403 (FORBIDDEN) page will be returned. Turn this flag on to enable the old behavior, which was to return the user to the login form.</p>"
        },
        "retainOriginalURL":{
            "default":false,
            "type":"boolean",
            "description":"<p> The retain-original-url property is used in FORM based authentication scenarios. When this property is set to true, after a successful authentication, WebLogic Server will redirect back to the web resource (page/servlet) retaining the protocol (http/https) used to access the protected resource in the original request. If set to false (which is the default value), WebLogic Server will redirect back to the protected resource using the current protocol. The retain-original-url value can also be specified at per web application level in weblogic.xml. The value in weblogic.xml, if specified, overrides the domain level value.</p>"
        },
        "rtexprvalueJspParamName":{
            "default":false,
            "type":"boolean",
            "description":"<p>Global property which determines the behavior of the JSP compiler when a jsp:param attribute \"name\" has a request time value. Without this property set to \"true\", the JSP compiler throws an error for a JSP using a request time value for the \"name\" attribute as mandated by the JSP 2.0 specification. This property exists for backward compatibility.</p>"
        },
        "servletAuthenticationFormURL":{
            "default":true,
            "type":"boolean",
            "description":"<p> ServletAuthenticationFormURL is used for backward compatibility with previous releases of Weblogic Server. If ServletAuthenticationFormURL is set to true (default), then ServletAuthentication.getTargetURLForFormAuthentication() and HttpSession.getAttribute(AuthFilter.TARGET_URL) will return the URL of the protected target resource. If set to false, the above APIs will return the URI of the protected target resource. By default, the value is set to true.(new method added in 9.0.0.1) </p>"
        },
        "servletReloadCheckSecs":{
            "default":1,
            "x-weblogic-productionDefault":-1,
            "type":"integer",
            "format":"int32",
            "description":"<p><h5>Constraints</h5></p><ul><li>production mode default : -1</li></ul>"
        },
        "showArchivedRealPathEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Global property to determine the behavior of getRealPath() for archived web applications. When this property is set to \"true\", getRealPath() will return the canonical path of the resource files. </p>"
        },
        "tags":{
            "title":"Items",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"<p>Return all tags on this Configuration MBean</p>"
        },
        "type":{
            "readOnly":true,
            "x-weblogic-unharvestable":true,
            "type":"string",
            "description":"<p>Returns the type of the MBean.</p><p><h5>Constraints</h5></p><ul><li>unharvestable</li></ul>"
        },
        "weblogicPluginEnabled":{
            "x-weblogic-secureDefault":false,
            "default":false,
            "type":"boolean",
            "description":"<p>Specifies whether or not the proprietary <code>WL-Proxy-Client-IP</code> header should be honored. (This is needed only when WebLogic Server plug-ins are configured.)</p><p><h5>Constraints</h5></p><ul><li>secure default : false</li></ul>"
        },
        "workContextPropagationEnabled":{
            "default":true,
            "type":"boolean",
            "description":"<p>Indicates whether or not WorkContextPropagation is enabled. By default, it is turned on. There is a little overhead involved in propagating WorkContexts. Therefore, if you don't want WorkContext propagation, turn this value off in production environments. </p>"
        }
    },
    "description":""
}