This article is a collection of useful notes on a variety of topics related to configuration of Oracle Forms and Reports Services 12c. You can find them here. If you choose a software-only installation, you can initiate the configuration steps using the following command. This is also useful if your configuration phase fails and you want to rerun it after making the necessary changes to fix the issues. The basic WebLogic environment variable settings are described in the installation guides, but the following list accounts for most of the scenarios you are likely to come across on the server, including forms compilation from the command line.
Remember to adjust the paths to suit your installation. The paths below assume you've installed using the same paths I used in my installation guides. It's worth setting both as many documents don't follow my preference. Many of the 12c Forms and Reports Services configuration files are the same as those in 11gR2, but their locations differ. A fuller list of configuration files can be seen here. The "formsweb. Typically, each separate environment will have it's own section in the "formsweb.
You only need to specify a value in a Named Configuration if it differs from that in the default configuration. For example, a named configuration might be simple, like the following. A very useful entry is the "envFile" parameter, that can associate an environment file with a named configuration. Any custom environment files should be derived from the "default.
An Oracle Forms Services application from prior releases that includes a Reports Server cluster name will fail to bind to the Reports Server cluster it references. This avoids the necessity to change the cluster name in all Oracle Forms Services applications.
Using WEB. In this case, the request is submitted to rwservlet. For example:. The cookie element specifies an expiration time and encryption key for cookies, which save encrypted user names and passwords on the client-side when users first authenticate themselves. When the server receives a cookie from the client, the server compares the time saved in the cookie with the current system time. If the time difference is longer than the number of minutes defined in cookieexpire , the server rejects the cookie and returns to the client the authentication form along with an error message.
Users must re-authenticate to run the report. The encryption key to be used to encrypt the user name and password of the database and system authentication cookies. The defaultcharset sub-element of rwservlet is defined in rwservlet. This ensures that rwservlet uses the required encoding when decoding the parameter name and value. The webcommandaccess element specifies access permission for rwservlet keywords Web commands for a non-secure server.
For L2 Web command access, you do not need to pass the authid. The allowhtmltags sub-element of rwservlet is defined in rwservlet. The helpurl sub-element of rwservlet is defined in rwservlet. The rwservlet HELP keyword Web command displays either the default help file, or the help file specified by the helpurl element.
The imageurl sub-element of rwservlet is defined in rwservlet. The imageurl element specifies the location of reports' dynamically generated images. It ensures that dynamically generated images, such as charts, will be viewable only by the person who runs the report. JSPs, and other report types, that run through rwservlet automatically have this protection. The reloadkeymap sub-element of rwservlet is defined in rwservlet. The reloadkeymap element specifies whether the key map file cgicmd.
This is useful if you frequently make changes to the map file and want the process of loading your changes to be automatic. This section also includes samples of the default configuration files that are installed on the system. Some default values such as locations and paths may vary. The location of these files in Windows is similar. The configuration file formsweb. For more information on editing the files, refer to Section 4. The configuration file default.
The web. Typically, each separate environment will have it's own section in the "formsweb. You only need to specify a value in a Named Configuration if it differs from that in the default configuration. For example, a named configuration might be simple, like the following. A very useful entry is the "envFile" parameter, that can associate an environment file with a named configuration. Any custom environment files should be derived from the "default.
Changes to this file to not require a restart of any components. The changes can be done directly to the file, or through Enterprise Manager. The "default. All custom environment files should be derived from this file. You can see and example of the "default.
Environment variables specified in an ". If an environment variable is not defined in the ". Changes to these ". Forms, menus and libraries are compiled using the frmcmp.
Running the command without any parameters displays the usage information.
0コメント