This action might not be possible to undo. Are you sure you want to continue?
and they can interact among themselves too. Grid Computing Architecture (GCA) and Enterprise Information Architecture (EIA). For me it is 'XE'.oracle. and also made a note of the difficulties faced at each step. as I practically carried out the necessary steps for the installation. SOA. Oracle Fusion Middleware. The Oracle Database 10g XE can be downloaded from the URL provided below: http://www. Loopback adapter. Oracle Fusion Middleware is based on the three emerging trends in the field of information technology. Java Access Bridge. This Oracle database is required because the installation of Oracle SOA Suite requires some schemas to be already present in a database. Following and during the installation. Services. . and comes handy for use by developers and DBAs. WebLogic. so that they can be reused in developing composite applications and complex business processes as and when required. In depth discussion and administrative concepts of SOA. As more and more businesses move towards a service oriented architecture in which.Keywords: Oracle SOA Suite. and the service name.ora and tnsnames. The installation of SOA Suite requires an Oracle database already up and running.html The installation of Oracle Database 10g Express Edition (XE) is very simple. these information can also be extracted from the listener. as ample documentation regarding these are already available. It is exactly like an infrastructure grid.ora files present in the app\oracle\product\10. it is meant to be a unit of work which is a part of a complex business process). Service Oriented Architecture. 11gR1. and “Applications” exposed as “Services” are present whose services can be tapped whenever required. which acts as the metadata repository for the SOA suite components. However for this installation. it is necessary to note down some information like the database listener port. A mere knowledge of the presence of the required “Service” is enough. They are loose coupled. without being considered about where these “Services” actually reside. Generally the service name is same as that of the database name. It is for reference purpose.com/technology/software/products/database/xe/index. These are.2. WebLogic Server. Service Oriented Architecture (SOA). the “Services” are aware or the presence of other “Services”. This can be rather considered as an “Application Grid” where loosely coupled “Services” (by “Services”. XE. Any Oracle database can be used. This article is mainly concerned with Oracle SOA (Service Oriented Architecture) Suite 11gR1 installation on Microsoft Windows XP. Oracle Database and Oracle Fusion Middleware are not being dealt here. Repository Creation Utility. and thereby providing flexibility and agility to the entire system. These will be required in the later stages of the installation process. The default database listener port is always 1521. I used Oracle Database 10g Express Edition which is a small footprint database based on the 10g R2 code. RCU. service pack 3 platform.0\server\NETWORK\ADMIN directory under Oracle Home. Oracle Database 10g Express Edition. This is the first and the most important prerequisite. Absence of one “Service” does not affect another “Service”. just that the “infrastructures” like printers and other such hardware components are replaced here by “Services” which are nothing but a software component/implementation. If not noted during the installation. and provides complete set of infrastructure required for designing. deploying and managing SOA composites. Microsoft Windows XP. Oracle SOA Suite is a middleware component of Oracle Fusion Middleware. but they are not dependent on each other for their operation. instead of recoding every time whenever there is a change in business processes/policies. the database name. most preferably Oracle Database 10g or 11g. as I also include the steps to overcome these problems as a part of this documentation. “Services” are built instead of “Applications” and these “Services” are exposed. That is.
This connects to the database as a SYSDBA. So.bat batch file. MDS and ORASDPM are required by both SOA Suite and BAM (Business Activity Monitoring). The Oracle SOA Suite requires some default schemas to be present in the database which acts as the metadata repository for the SOA Suite components. SOAINFRA. At least I did not get it along with the distribution which I downloaded from the Oracle Technology Network (OTN). and ORABAM. An user with SYSDBA privilege is required because it is only the user with SYSDBA privilege who is allowed to create schemas in a database. Execute the rcu.html To create the above mentioned schemas. make sure that the database is up before continuing. try logging into the database by using the following statement from the DOS command prompt: SQLPLUS “/AS SYSDBA” after navigating to the appropriate Oracle Home. This can be done by ALTER USER SYS IDENTIFIED BY <new_password>. These schemas cannot be created using CREATE USER SQL statement. To create these schemas.ora and tnsnames.oracle.com/technology/software/products/middleware/htdocs/111110_fmw. I had to download it separately from the following location: http://www. After the information has been provided. SOAINFRA is required by SOA Suite and ORABAM by Oracle BAM. This provides a GUI where it asks for the following information: Database Type Host Name (for me it is localhost since I am installing it in my laptop) Port (the DB listener port. Expand the “SOA Infrastructure” component to find SOAINFRA. and ORABAM. The schemas required are MDS. because these schemas are not just schemas. So. Again. Here it is required to specify the schemas which are to be created in the database. unzip the RCU distribution and navigate to the rcuHome/BIN directory from the DOS command prompt. in case you do not remember the default one. but they are supposed to contain a large number of database objects (tables and views) build into them for storing the information.ora. For me. Of these. the schema names become . The default prefix is DEV. ORASDPM. A prefix automatically gets attached to the schema names. perticularly while using RCU. Default is 1521) Service Name (check listener. one requires a RCU (Repository Creation Utility). This RCU does not come along with the SOA suite distribution. it is XE) Username (User with DBA or SYSDBA privilege) Password (SYS password) Role (SYSDBA) These are the database connection details which are required by the RCU to connect to the specified database and create the repository for Oracle SOA Suite and Oracle BAM. ORASDPM. as has been mentioned before. One thing that can be done is to change the password for the SYS user. the RCU asks for the repository components.After the database installation is over. vital for the SOA Suite components operation. and lets you make any administrative modification. The SYS password will again be required in later stages of the installation process.
it will always look for the SPFILE first. Don't do anything to the RCU GUI. and if found. If the PFILE is not mentioned. where DBNAME is the database name. Let it be as it is because the repository creation can be continued from this point onwards. For that. which in my case is “xe”. the database has to be started up using the parameter file (PFILE) so that the parameters defined there take immediate effect. making a SPFILE makes sure that the database can be started up even without the PFILE present anywhere. it is necessary to recreate the SPFILE so that the changes take effect in the SPFILE as well. After that. Open this file using a text editor. SHUTDOWN IMMEDIATE. Let the database create the SPFILE in its default location with the default name so that it can easily track it the next time it is bounced. it then goes on to search for the PFILE (init<DBNAME>. once the issue with the PROCESSES parameter is resolved.DEV_SOAINFRA etc. At one point. One more schema is required. or if it has a different name. it is necessary to change the PROCESSES initialization parameter for the database. In case the PFILE (init<DBNAME>. first create a init<DBNAME>. and make a new entry as PROCESSES=200 (if the entry is already not present) in exactly the same manner as the rest of the parameters. For me. but it will search for it only in the default location where it is supposed to reside. This can be done by issuing the following statement at the SQL command prompt CREATE PFILE= '<PATH>' FROM SPFILE. which actual is 40. it will never look for the PFILE. CREATE SPFILE FROM PFILE='<PATH>. while running the RCU. for the initialization parameters. so that the next time when the database is bounced. This will create the PFILE at the path name specified. After the SPFILE creation.ora). This can be found by expanding the “Oracle AS Repository Components”. This happens with Oracle Database 10g XE. In fact. there was a '*. No location for the SPFILE has to be mentioned.ora parameter file. It is a problem with the initialization parameters of the Oracle Database 10g XE where the parameter PROCESSES have a value set to 40. Next. To overcome the problem shown by the RCU error message. which is the Metadata Services or MDS. If the SPFILE is not found. This is done using the following command. shutdown the database using the following command.' before every parameter and so I also preserved while I made the PROCESSES parameter entry. STARTUP PFILE= '<PATH>' Now. So. it is not necessary to specify the PFILE location. it takes the initialization parameters from the server parameter file by default. bounce the database again so that it makes use of the SPFILE to start . SPFILE is created in a similar manner as the PFILE.ora) is located somewhere else. Oracle Database will not be able to detect the file. an error message is displayed which shows that the number of processes expected is 200. creation of the SPFILE is always preferred because whenever a database is started by using the command STARTUP.
properties file to the jre/lib directory of the corresponding JDKs. It may ask for the system to be rebooted. there is no need to run the config.com/technology/software/products/ias/htdocs/wls_main. the installation location is C:\Program Files\Java Access Bridge. Unzip the zip file and execute the wls1031_win32. it may not be possible to bring up the database. at one point it may show an error message that the database is not supported.rather than the PFILE. For my system. To modify the SPFILE. It should not give any error now. After the installation is over. it should not be touched.dll.html I however downloaded the software from Oracle SAC. This is required only when the installation is to . and in case there is no PFILE. The next step involves creating a loopback adapter. While running the RCU. Opening a SPFILE with a text editor can corrupt the file. always create a PFILE and then recreate the SPFILE back as stated above. In fact. it showed two jdk folders under Middleware home. JavaAccessBridge. namely jdk160_05 and jdk106_11. Finally. go back to C:\Program Files\Java Access Bridge\ installerFiles and copy the WindowsAccessBridge.1) can be downloaded from OTN via the following link: http://www. The next step in the SOA Suite installation process is to install an Oracle WebLogic Server. This is required for Windows systems only and not required for Unix/Linux. which is an Oracle software repository for internal use accessible to Oracle employees. For my system. Clicking next goes on to create the necessary tablespaces (a default and a temporary) for the specified schemas.cmd. The Java Access Bridge can be downloaded from the following location: http://java.sun. go to the installation location. The next step is to install a Java Access Bridge.dll to the jre/bin directory of the JDK directory or directories. the SPFILE should never be modified. After the installation is over.dll. Oracle WebLogic Server 11gR1 (10. as is usually done after the WebLogic server installation to create and configure domains.exe file.oracle. Go to the installerFiles location. Go for a custom installation. After the changes.3. continue with the RCU. SHUTDOWN IMMEDIATE STARTUP A point to be noted is that. Copy the accessbridge.jsp Install the Java Access Bridge by clicking the executable downloaded. and JAWTAccessBridge. copy the accessibility.jar from this location to the jre/lib/ext directory of the corresponding JDKs installed under the Middleware home where the Oracle WebLogic server was installed. One can easily check the tablespaces created by connecting to the database as SYSDBA and then checking the V$TABLESPACE table.jar and jaccess-1_4.com/javase/technologies/accessibility/accessbridge/index. Then. Just ignore the message and continue with the repository creation process.
DOMAIN_NAME HOST_NAME For my installation. The next screen asks for selecting the products which are to be supported. Select TCP/IP and provide an IP address. Select properties. 192. The pathname of that JDK can be provided. The SOA home directory.3\common\bin directory is run. It is mandatory to do so. If the Oracle WebLogic server installs a JDK. Select manufacturer as Microsoft. The setup. Select Network Adapter. this is the step where the SOA Suite installation is integrated with the WebLogic server installation done previously. This will show all the network connections. The location should be provided in a way such that <location_provided>\bin has the executable java. I navigated to this folder and ran the config. as the WebLogic server installation installed two JDKs. that is where SOA is to be installed has to reside under the Middleware home where we installed the Oracle WebLogic server. not the one provided by the WebLogic server installation. go to the desktop. I continued with the default one provided by the installer. present under the <MIDDLEWARE_HOME>\wlserver_10. For my installation. the location was C:\ORA_SOA\MIDDLEWARE\jdk160_11 or infact. This starts the Configuration Wizard. I gave 192.cmd script corresponding to the WebLogic server installation.cmd.cmd script. Till now. The options include SOA suite.be made on a DHCP system.com idc.exe.domainname to see if the IP is accessible. the WebLogic server installation did not come into picture than .hyd. Oracle_SOA1. This options will not be provided when the config. it is time to configure the WebLogic server domains.0. After unzipping the distribution. EM. Note down this IP address as it will be required later. and Network Adapter as Microsoft Network Adapter. I specified it as. Any name of the SOA home will do. And go on clicking next. Then select “Yes. Using the DOS command prompt. After installing the loopback adapter.255. BAM and JRF.e. Then.88. I carried out this step for my system as it was necessary. Go to the command prompt and ping the hostname. For this.exe executable present under the Disk1 folder.cmd.88. Select the connection that corresponds to the Microsoft Loopback adapter and select properties.cmd script was C:\ORA_SOA\MIDDLEWARE\Oracle_SOA1\common\bin\config. go to C:\WINDOWS\system32\drivers\etc and open the hosts file. Select next. Else it is not required. Make a entry there just after the localhost line as shown below IP_ADDRESS HOST_NAME. go to the control panel and click add hardware. present under the <SOA_HOME>/common/bin directory.168. In fact. For me. the location of this config. i. This will install the loopback adapter. The SOA home should be under the Middleware home.255. just that it should be under the Middleware home.168. I could have also provided the path of the JDK as C:\ORA_SOA\MIDDLEWARE\jdk160_05.83 and the network mask as 255. begin the installation using the setup. and right click on the network places.hyd Save it and restart the computer. Go for creating a new WebLogic server domain and click next.exe will open a command prompt asking for the JDK/JRE location. After the SOA suite installation is over. This has to be done by running the config. Then select “Add a new hardware” at the bottom of the list.oracle. I have connected the hardware”.83 idc.
select one schema at a time. It shows that it uses a thin JDBC client. it was “xe”. connect to the database as SYSDBA. setting it to any value using the following command: ALTER USER <schema_name> IDENTIFIED BY <new_password>. de-selecting others. and by running the Configuration Wizard. If not deselected.oracle. EM. As you proceed. While testing the connection. The listener port is 1521. Provide the host name as the one which you configured at the time of the loopback adapter installation.hyd. I used the following command: telnet idc. It provided all information about the database connectivity. the host name. BAM and JRF) and continue. DEV_ORABAM for BAM schema DEV_SOAINFRA for SOA infrastructure DEV_ORASDPM for User messaging service DEV_MDS for OWSM MDS schema DEV_MDS for SOA MDS schema Click next to test the connections. the managed servers. Provide values only for those fields which are required. clusters and machines. Provide the DB name or service name in the DBMS/Service field. refer the WebLogic server documentation. move back to the previous screen. you have to provide the Schema owner name and the corresponding passwords.hyd. Of these. and change the password. make the required corrections and test again. to check if the port 8877 is free on my system. Provide the domain name. refer to the WebLogic server documentation. SOA suite requires an application sever. In case you have forgotten the passwords for the schemas. For me. Configure the Admin server.com 8877 . For details of of these domain configurations.com. I configured the Admin Server. Just modify the listener port. which is the default port and was the listener port for my database. There is no need to modify the Vendor name and driver type. The thin client is what is required. In case connections fail for any schema. the mode will be asked for. have a look at the JDBC connection URL. The schema owner names corresponding to the schemas. the values entered for the schema owner and schema password will be made common for all the schemas. the application server (which is the WebLogic server for SOA Suite 11gR1) is provided to it. The next screen will ask for the details of the database connection. just go to the command prompt and telnet the host with the port number. Next. For changing the schema names and to provide the passwords. For example. the DB listener port number and the service name. For further details of the the modes. Select all the products (SOA.oracle. For going to the next schema. de-select the previous one for which you just made the entry and select the new one for which entries are to be provided. for my case were. I provided it as idc. The next step asks for the configuration options. and the schemas which were created using the RCU. Continue with the development mode. To check if a port is currently being used.just providing the Middleware home where the SOA home resides. Verify the location of the domain and the applications. and fill the fields corresponding to schema owner and schema password under the driver field.
it means that the port is free and can be used. including the Admin server to the machine just configured.hyd. The syntax for this command is startManagedWebLogic.cmd <managed_server_name> <admin_console_url> For me. The bam_server1 managed server hosts the Oracle BAM.oracle.com:7001 The username and password required will be the ones provided during the domain creation using SOA suite configuration wizard.com:7001/em The managed servers were still found to be in the shutdown state.cmd. and for the node manager listen port.88. which I configured during the loopback adapter installation.The command window has to remain open as long as the Admin server is running. This will kill the Admin server as well. Next comes the node manager configuration. I could access the Admin console can be accessed from the following URL: http://idc. Finally.168. start the Admin server.83. The installation and configuration of Oracle SOA Suite 11g is done. present under the <MIDDLEWARE_HOME>\user_projects\domains\<DOMAIN_NAME> folder. Again specify the port numbers and proceed. (Please refer to WebLogic server installation guide for further details about the installation process) Two managed servers are created. These are bam_server1 and soa_server1. The listen address can be configured to the IP address of the host (machine) in which the node manager resides. The Admin server can be started by executing startWebLogic. from separate command prompt windows. Assign all the servers. it is 192.oracle. startManagedWebLogic.oracle. while the soa_server1 managed server hosts the Oracle SOA Suite.hyd. This process has to be repeated for each of the individual managed servers.com:7001/console The Enterprise Manager Fusion Middleware Control console could be accessed from the following URL: http://idc.If no connection is established and the connection fails. Do not close down the command window.hyd. These could be brought up by using startManagedWebLogic.cmd bam_server1 http://idc.cmd. create the domain. it was. while the default is 5556 as the port 5556 was not available to me for use. I took it to be default as 6001. To launch the Admin Server URL. . For me. You may configure a cluster if you want. present in the <MIDDLEWARE_HOME>\user_projects\domains\<DOMAIN_NAME>\bin folder. first. It was not free.
The DMS application were accessible through the following URLs. it was bam_server1.com:9001/OracleBAM where. After it is up. To check Oracle B2B.com:7001/dms http://idc.oracle.hyd.com:8001/b2b where.oracle. provided in the configuration wizard.oracle. Oracle BAM was accessible at the following URL: http://idc. 9001 was the listen port for the managed server bam_server1. provided at the time of SOA configuration. the managed server hosting Oracle BAM has to be brought up.hyd. for the Admin server. 8001 was the port number of the soa_server_1 managed server. . it is necessary to bring the soa_server1 managed server up. In my case. bam_server1 and soa_server1 managed servers respectively: http://idc.oracle.hyd.To access Oracle BAM.com:8001/dms That makes the installation complete. The URL for accessing Oracle B2B for my installation was: http://idc.hyd.com:9001/dms http://idc.oracle.hyd.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.