Archivos de configuración de la red Oracle

En este documento vamos ver los posibles archivos existentes de configuración de la red de oracle, dependiendo de la configuración que se utilice se pueden configurar unos archivos u otros. Vamos a ver la configuración de los siguientes archivos: # listener.ora # tnsnames.ora # sqlnet.ora # names.ora # ldap.ora

1. listener.ora
Archivo ubicado en el servidor de base de datos. Es el archivo de configuración del listener de la base de datos. Este archivo tendrá que estar ubicado en $ORACLE_HOME/network/admin/listener.ora. El comando para gestionar el listener es lsnrctl. Este ejecutable lo podemos encontrar en $ORACLE_HOME/bin/lsnrctl.

Ejemplo de configuración del listener.ora: LISTENER9 = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = = 2484)) ) ) ) SID_LIST_LISTENER9 = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = orasite) (ORACLE_HOME = /oracle9/product/9.2.0) (SID_NAME = orasite) ) )

Parámetros del archivo: HOST: Dirección ip del servidor de base de datos PORT: Puerto de escucha de la base de datos ( por defecto suele ser el 1521 ) CLOBAL_DB_NAME: Nombre de la base de datos ORACLE_HOME: Directorio de instalación de ORACLE ( ORACLE_HOME ) SID_NAME: SID de la base de datos ( muchas veces coincide con el GLOBAL_DB_NAME )

orasite. tnsnames.ora Archivo ubicado en los clientes. * Servicios de base de datos * Parámetros de control utilizados por el listener.4.PREFERRED_SERVERS = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = onames. contiene los nombres de servicio de red.DIRECTORY_PATH= (ONAMES.Este archivo incluye: * Direcciones de protocolo en las que acepta solicitudes de conexión.ora: CNNORASITE = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 193. sqlnet.TNSNAMES) .220)(PORT = 2484)) ) (CONNECT_DATA = (SERVICE_NAME = orasite) ) ) Parámetros del archivo: HOST: Dirección ip del servidor con el cual queremos conectar PORT: Puerto donde escucha la base de datos SERVICE_NAME: Nombre del servicio de base de datos al que queremos conectar DESCRIPTOR DE CONEXION: En este caso el descriptor para conectarnos es CNNORASITE Podemos comprobar si la conexión es correcta mediante el comando TNSPING $TNSPING nb_descriptor_de_red = 1640)) ) NAMES. (Ver seguridad del listener) 2.ora Archivo ubicado en el cliente y en servidores de base de datos Ejemplo de configuración del sqlnet.ora: NAMES. asignados a descriptores a través de los cuales se nos permite acceder Ejemplo de configuración del tnsnames.

DIRECTORY_PATH: Orden de archivos a mirar para resolver el descriptor de servicio 4. es una archivo configurado para que en un principio resuelva resuelva por ONAMES y en segundo lugar por TNSNAMES. Esta configuración busca primero el descriptor en ONAMES y si no existe busca la configuración de conexión en el TNSNAMES.PREFERRED_SERVERS: Indica la dirección del servidor ONAMES junto con su puerto NAMES. .Parámetros del archivo: Este ejemplo de archivo sqlnet. NAMES. ldap.ora Archivo ubicado en el servidor de base de datos y en el cliente configurados para que funcionen como gestión centralizada.ora Archivo ubicado en el servidor de ORACLE NAMES. Este archivo incluye la ubicación y la información de dominio y los parámetros de configuración opcionales para un servidor de ORACLE NAMES 5. Contiene los parámetros necesarios para acceder al servidor de directorios. names.

The following is the Oracle certified supported configurations. If you decide to use the Sun JRE. you will need to install the appropriate version as the Forms Builder ships configured to a specific version of the Sun JRE.0. but this document is not intended to help you with FMw configuration.3. The information in this document could be adapted to Oracle Forms 9i. There are two Java Runtimes (JREs) supported by Forms Builder. .2_06).2 and it is no longer available for download. the Forms Debugger utility.22. this document targets the following Oracle Developer Suite (Forms/Reports) versions: 10g R1 (9. Oracle Forms 10g R2 (10.6. but I do not currently have access to this version of Forms so there is no guarantee that these methods will work for Forms 9i. Therefore. Background If you have used Oracle Forms long enough. Configuration is simply to install the Oracle Jinitiator (make sure you install the right version because each Forms version defaults to different version.4. fewer developers are familiar with setting up the OC4J environment variables which enable you to run a form from the Forms Builder.pll] and Forms Object Libraries [.1. Most likely. this document is NOT all inclusive – meaning it is not a full reference to all setup options available.x). “It is always better to reuse then to recreate!” Disclaimer First and foremost.4.x).0.0).x.2) defaults to using Oracle Jinitiator 1.2.0.olb]).Forms: How to Configure Forms Builder to run forms locally Introduction I wrote this document because so many people in the Oracle Technology Network (OTN) Forms Forum have asked “How do I run a form from the Forms Builder?” or “I just installed Forms 10g and all I get is a blank browser window when I run a form.2.1.2. Secondly.Lastly. The first relates to Forms Builder and the second relates to the OC4J Forms Servlet. it is just a little harder to do now and requires some configuration setup on your workstation to make it work. Most forms developers will be familiar with configuring the Forms Builder as this involves setting up key environment/registry variables so the Forms Builder can find libraries (PL/SQL libraries [. This is a very generic description of what OC4J is and what it does. again. These two program items are the “Start OC4J Instance” and “Stop OC4J Instance. but it will suffice for the purpose of this document. With the advent of Forms 9i – when Oracle made Forms web deployed only – many developers thought the ability to run a form from the Forms Builder was lost. this article assumes you have successfully installed the Oracle Developer Suite (ODS) 10g R2 (10. If you need to use features that are not listed in this document. This document focuses on setup for the Microsoft Windows Operating System and Internet Explorer and Mozilla Firefox browsers. This document is meant only to get you up and running. Oracle has included two new program items (among others) in Oracle Developer Suite Program group of the installed Oracle Developer Suite 10g.” After I responded to numerous posts (always writing the instructions from scratch) I decided to write this document. you will likely be installing the latest version of the Sun JRE which is Java 6 (1. For example. Oracle Forms 10g R2 (10. However. If you install the version found in your Oracle DevSuite home directory (\%DEV_SUITE_HOME%\jinit) you should be OK. Let’s get started… There are two parts to configuring Forms Builder to run forms. This was a very nice feature that enabled you to perform incremental development and testing.1. By default. As they say. Forms 10g use the OC4J Forms Servlet to emulate a Forms Service web process on your workstation that allows you to “serve” a web form from the Forms Builder. Many of the concepts apply to the Oracle Fusion Middleware (FMw) 11g suite (Forms and Reports).2 update 6 (1.2. you will have to update the default settings as you likely do have the Sun JRE installer for 1. This is not true. Forms Builder is configured to use the Oracle Jinitiator and in most cases this should be sufficient for your needs.4.4. not to mention the Forms Runtime Diagnostics (FRD). Oracle Jinitiator and the Oracle (Sun) Java Runtime Environment (Sun JRE). Which JRE you use is also dependent on your Operating System (OS) version and your Internet Browser version.” Both are critical to the running of forms from the Forms Builder.1. In order to run a form from the Forms Builder.1. If you have not already installed the ODS then you will need to do this before you can proceed. you will remember the day when you could run a Form locally from the Forms Builder with the Forms Runtime.x.x. For example. please refer to the appropriate Oracle document available at the Oracle Technology Network (OTN).x) and 10g R2 (10.2) defaults to Sun JRE version 1.

olb]). enough background.22+ 1.28 1.5+ Java Runtime Jinitiator 1.ora and SQLNET. This variable is mandatory if you use attached libraries or subclassed objects.5.6. b.olb) and object referenced from a Forms Template file (template.ora files. This saves you having to modify the “formsweb.x+ 1. Example: FORMS_PATH=C:\DevSuiteHome10g\cgenf61\admin. In my Forms_Dev directory. if I am working on different projects.3.0_06+ 1. This document will describe both methods of setting these variables.6. object libraries (.2_06+ 1.0_16+ NS Sun JRE 1.OS Windows Internet Explorer version 5 version 6 version 7 version 8 FireFox 3. scroll through and find the FORMS_PATH string variable and double-click or rightclick and select “Modify” to edit the variable.6.3.4.”. This document will be focused into three sections: Forms Builder config.3. Windows Registry 1. I have a Forms_Lib directory where I store all of my referenced items such as. TNS_ADMIN is used by Forms Builder to find your TNSNAMES.1. OC4J with Jinitiator.pll) and subclassed objects (such as items from a Template. Note: I have found that I can include a wildcard reference in the FORMS_PATH. Navigate to the appropriate Oracle Home • HKEY_LOCAL_MACHINE • SOFTWARE • Oracle • HEY_DevSuiteHome10g 3.pll). and OC4J with Sun JRE. This variable is optional. Open the Windows Registry Editor (regedit. Alright. a. It‟s time to get the heart of this document. DO NOT delete the existing value.4. Add directory information by separating it with semicolons “.exe or reged32. This is a design time error only and does not affect runtime.C:\Forms_Dev\*.1. FORMS_PATH: In the Key listing. These variables can be set in either the Windows Registry (Windows XP) through the Windows System Environment Variables.1.1+ 1. You can also include your Forms working directory in this variable and Forms runtime will be able to find your compiled Forms binaries when you run a form from the Forms Builder.exe) 2. This variable is optional. This allows me organize all of my Forms development into a single directory. FORMS_BUILDER_CLASSPATH is used by Forms Builder to record the location of any Java Pluggable Components or Java Beans that are implemented in a form. attached libraries (.fmb or Object Library [. Additionally.0_16+ + = indicates a higher version can be used NS = Not Supported This list is an abbreviated list.0_16+ 1.fmb). Forms Builder Configuration Forms Builder is dependent on the following variables (there are others.cfg” file to include a configuration for each form you develop (I‟ll include a brief discussion of custom configurations at the end of this document). This variable is handy if you have multiple Oracle Homes installed because it allows you to share a single set of TNS configuration files. but these are the most important): • FORMS_PATH • FORMS_BUILDER_CLASSPATH • TNS_ADMIN FORMS_PATH is used by Forms Builder to record the location of attached libraries (. For a complete list – review the appropriate Oracle Certification Matrix document on OTN. but you will receive a Forms Builder error during design time indicating that Forms Builder can‟t find the implemented Java source. but if you have multiple Oracle homes you will have to maintain separate copies of the TNS files for each Oracle home. I can .

This will create an empty string entry. right-click somewhere and New => String Value from the context menu b. For example. They are: FORMS_PATH and CLASSPATH. Variable Value = full path to your working and library directories iii.cfg is broke up into separate defined configurations. FORMSWEB. c. Click on the Environment Variables button towards the bottom. a.CFG These file can be found in the \%DEV_SUITE_HOME%\forms\server directory. a.ENV • FORMSWEB. 4. . Click on the Advanced tab. Variable Name = FORMS_PATH ii. (Start Menu => Control Panel => System) 2. 5. Open the editor for the string and enter the full path to your TNS configuration files. If more than one person uses the workstation.jar file listing by separating each entry with a semicolon. These files are: • DEFAULT. the „Default” configuration is listed as: [default]. Eg: C:\DevSuiteHome10g\NETWORK\Admin Windows Environment Variables 1. You will need to list the full path. OC4J Servlet setup The OC4J Servlet setup is a bit more complex in that all of the variables are stored one of two files. I recommend you add the FORMS_PATH variable to the set of User Variables rather than add it to the list of System Variables. I‟ll list Sun JRE first and Jinitiator second.cfg – This file contains the parameter values used by the Forms Servlet. The formsweb. a. Each configuration is named and can be identified by the name in square brackets.create a subdirectory for each project. I strongly recommend you make a back up copy of the original file before you modify these files. This file is where the bulk of changes are needed the enable running a form from the Forms Builder. 5.env – This file is used to set Forms runtime environment parameters. Open the System Properties control panel applet. Again – DO NOT delete any existing values b. in this parameter listing. DEFAULT. Add to the exiting directory and . Click on the New button and enter the Variable Name and Variable Value i. This allows each user to set their own preferences. There are two types of parameters: SYSTEM and USER defined. This is the configuration that is used unless it is overridden through the URL query string. you will have to create this entry in each of the Oracle Homes. TNS_ADMIN: This entry does not exist. The Developer Suite installation does not include the OEM so modifications must be made manually with a text editor. Note: These files should only be modified on the application server using the Oracle Enterprise Manager (OEM). Configuration will be separated by Java Runtime used. The FORMS_PATH needs to have the same directories listed as stated above for the equivalent Registry or Environment variable. I will not list all of the parameters as there are too many. You do not have to worry about the default value of this variable in the registry as this environment variable augments the registry. that Oracle has retired the Jinitiator and no longer supports its use. Refer to the Application Server Forms Services Deployment Guide (see references) for a complete listing of all parameters and more detailed information. FORMS_BUILDER_CLASSPATH: find the existing entry for this key and open the key editor. to include the file name. There are only two parameters that I have had to modify to enable running a form from the Forms Builder. System parameters are static in that they can not be overridden at run time. User parameters have an entry in the baseHTML file and can be overridden in the URL query string. This completes the Forms Builder setup. In the key listing. Do the same thing for the FORMS_BUILDER_CLASSPATH and TNS_ADMIN variables. 4. This parameter has a maximum character length of 256 characters. The CLASSPATH only need to be modified if you implement a PJC or Java Bean in your form. Bear in mind. 3. jpi_classid=clsid:CAFEEFAC-0016-0000-FFFF-ABCDEFFEDCBA # Parameter related to the version of the Java Plugin # Original setting #jpi_codebase=http://java.2.htm Parameter related to the version of JInitiator .0 jpi_codebase=http://java.6. # (NOTE: you should check this page and possibly change the settings) # Original setting #jpi_download_page=http://java.0 jpi_mimetype=application/x-java-applet. # Page displayed to users to allow them to download Sun's Java Plugin.6.06 # New – specific to JRE 1.0_22 jpi_classid=clsid:CAFEEFAC-0016-0000-0022-ABCDEFFEDCBA # Optional – Generic to any version of JRE 1.jpi-version=1. Conventions used: Settings listed in Green are code comments Settings listed in Blue are original settings Settings listed in Red are recommend changes Settings listed in Purple are optional changes Sun JRE Modify the following settings to use a JRE version different from the default if 1. you should set this parameter to point to # New – points to the generic ( non-version specific) JRE download web site jpi_download_page=http://www.6.0 Oracle Jinitiator Modify the following settings to use a Jinitiator version different from the default if 1.26. Oracle JInitiator is used with Windows clients.0.0/jinstall-6-windowsi586.6.sun.0_22 # Optional – Generic to JRE 1.0_22 jpi_mimetype=application/x-java-applet.sun.6.sun.1. There are no optional settings for Jinitiator. The following JRE changes instruct the Forms Runtime to use the JRE version 1.htm Oracle Forms is hardwired (so to speak) to use the Oracle Jinitiator. # System parameter: base HTML file for use with JInitiator client # baseHTMLjinitiator=basejini. # Sun's Java Plugin is typically used for non-Windows clients.4.6.4. If you create your own page.4.jpi-version=1. Therefore.0. to instruct the Forms Runtime to use the JRE without passing a URL query string # # # # # Page displayed to Netscape users to allow them to download Oracle JInitiator.4.6.htm baseHTMLjinitiator=basejpi. The following settings are all found in the [default] configuration section.6.3.2_06/index.0_22).6. it is recommended you change the “baseHTMLinitiator” parameter to point to the Java Plug-In (JPI) html file.2.6.0 update 22 (1. jinit_download_page=/forms/jinitiator/us/jinit_download.22 # Optional – Generic to JRE‟ll list later in the document how you can override a User parameter or specify a custom configuration later in the document.6. I find this to be the easier solution. html # Parameter related to the version of the Java Plugin # Original setting #jpi_classid=clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA # This setting is specific to JRE 1.0_22 jpi_codebase=http://java. Note the difference between these two You could also expand the existing [jpi] section and instruct the Forms runtime to use this configuration in the URL.0 # Parameter related to the version of the Java Plugin # Original Setting #jpi_mimetype=application/ # New – specific to JRE 1.

3. Passing this additional parameter.env and added the following variable: FORMS_TRACE_DIR=C:\DevSuiteHome10g\NETWORK\log References: . [my_frd] otherparams=record=collect log=my_frd. Custom configurations will use all of the variables in the [default] section and then override any you specify in your custom configuration. While this works fine for demo‟s. Always add additionally configurations to the end of the file. simply add “config=jpi” to the default URL query string.cfg file and scroll to the bottom of the file. you could pass the JPI configuration in the URL query string. To do this.28 # Parameter related to the version of JInitiator # jinit_mimetype=application/x-jinit-applet.env form=<YOUR_FORM_NAME_HERE.Oracle® Application Server Forms Services Deployment Guide – 10g Release 2(10.txt envFile=my_frd. To create a custom configuration.Oracle® Application Server Certification Information .1. there are times when it is good to create a configuration for a specific form. Then I simply add the parameter to the url to enable FRD (?config=my_frd).April 30.exe#Version=1.cfg file as this is a more permanent change.env) as well. alternatively.1) Oracle Forms & Reports 11g R2 : Installation Overview and Key Points .3.version=1.1.cfg to add a configuration for each form included in the demo. I prefer to make the change in the formsweb. For example.28 Default URL Query String and parameters The default URL query string used by the Forms Builder is: http://myhost.fmb> To create a specific environment file.26 jinit_mimetype=application/x-jinit-applet.mydomain. The following is based on my reference to use Forms Runtime Diagnostics (FRD).How Do the Jinitiator and JPI Parameters Work In a Forms Configuration (ID 444105. The configuration listed below also uses a configuration specific environment file (default.3.Using the Java Plug-in (JRE/JPI) with Oracle Forms (ID 794710. I simply copied the default. Custom Configurations If you have installed the Oracle Demo‟s you will find that Oracle modifies the formsweb.3.1.2) (B14032-03 – Feb 2006) . it is a real pain in everyday development to add a configuration section for each form you work on (which is why I edit all of my forms in a directory that is in my FORMS_PATH).1.env to my_frd.1. the default URL would look like: http://myhost.26 jinit_exename=jinit. if I want to run a form with the Forms Runtime Diagnostics (FRD) enabled. 2010) .2) (B25703-62 . I have created a configuration that enables this.1) With reference to the aforementioned JPI change for the “baseHTMLjinitiator=” parameter. open the formsweb.jinit_classid=clsid:CAFECAFE-0013-0001-0026-ABCDEFABCDEF jinit_classid=clsid:CAFECAFE-0013-0001-0028-ABCDEFABCDEF # Parameter related to the version of JInitiator # However. However.mydomain.1.10 g Release 2 (10.version=1.

OAM or OSSO can be used to integrate Forms & Reports for Single Sign-On.This post covers high level overview of Forms & Reports 11g R2 installation  Installation Document of 11g R2 (11. Use this option for Development Type installation.2) 3. More on OAM 11g in my book at Amazon 6. You also don’t get an option to integrate Forms & Reports with Identity Management Components (OID. OAM 10g or 11g).1 Install & Configure – You can install and configure forms & reports at same time using installer 3.2 Configure for Development – In this option you configure Forms & Reports but without OHS and Enterprise Manager . Forms & Reports in deployment mode will create a) WebLogic Domain with Admin Sever and two managed servers (WLS_FORMS & .1. Installation Type – You can install Forms & Reports in two type 3. Configuration Type – You can configure forms & reports in two ways 4.2 Oracle Reports a) Reports Builder – required for development and compilation of reports b) Reports Server – run-time server used to deploy reports application and execution of reports 2.1 Oracle Forms a) Forms Builder – required for development and compilation of forms b) Forms Server – run-time server used to deploy forms application and execution of forms 1. Oracle Forms & Reports consists of 1. OAM 10g or 11g).sh (bat) 4. Integrating Forms & Reports with IDM – You can integrate Forms & Reports with OID 11g (for other LDAP types and version check Certification Matrix ). 5. Latest release (as of April 2012) of Oracle Forms & Reports is 11g R2 (11.0) Forms & Reports is available here 1.1. You later configure forms & reports by running $ORACLE_HOME/bin/config.2 Install Software – Do Not Configure – You can install just forms & reports software and do not configure them via installer.1 Configure for Deployment – In this option you configure Forms & Reports and also configure Oracle HTTP Server (OHS) including Enterprise Manager. In this configuration you also get option to integrate Forms & Reports with Identity Management Components (OID. 4.2. Use this option for Production Type installation.

3.5). If yes what additional configuration is required and if not why not ? Leave your answer under comments . ORACLE_INSTANCE or DOMAIN_HOME here ) 8. You must install Forms & Reports Software under Middleware Home (MW_HOME) created during WebLogic Installation. this will create Middleware Home (More on MW_HOME. This step will create ORACLE_HOME for forms & reports. Use runInstaller (for Unix) and setup. 9. OAM can be configured in OPEN. You can integrate Oracle Identity Management components (OID & OAM) at configuration stage (select configuration type Deployment. SIMPLE or CERT mode (more in my book here ) then you must register OAM Agents manually from Forms & Reports node 11.WLS_REPORTS) more on WebLogic domain here b) Oracle Instance managed by OPMN with Forms. EM. select OHS and select Application Identity Store & Access Control) Note: You can integrate Forms & Reports with Oracle IDM (OID & OAM) later as well using steps mentioned here 10. Reports. To check Forms use http://host:port/forms/frmservlet and for Report http://host:port/reports/rwservlet where port is a) For deployment mode port os OHS listen port or WebLogic Managed server listen port of respective servers b) For development mode port is WebLogic Admin Server port Here is little quiz for readers – Is it possible to install Forms on one server and reports on different server. You will need to install WebLogic Software (10. and OHS 7.exe (for windows) to install forms & report from Disk1 of software. ORACLE_HOME.

Sign up to vote on this title
UsefulNot useful