IZEA

Showing posts with label Oracle. Show all posts
Showing posts with label Oracle. Show all posts

Thursday, February 6, 2014

Oracle SES Installation & Configuration


Oracle Secure Enterprise Search is a product integrated with PeopleSoft uses PeopleSoft Search Framework to integrate and communicate with PeopleSoft. PeopleSoft Application Version 9.2 onwards, configuring the PeopleSoft Search Framework and Oracle SES is required as Verity is no longer supported from PeopleSoft application versions 9.2.

Prerequisites  - Configure Loopback Adaptor & Disable IPv6:

To check if the Microsoft Loopback Adapter is installed on your computer:  Open a command window and enter - ipconfig /all

If the loopback adapter is installed, its settings are displayed as below.
Ethernet adapter Local Area Connection 2:
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Microsoft Loopback Adapter
        Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.123.123
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 
By default, the IPv6 protocol is enabled on Windows Server 2008. Under some circumstances, this may lead to the failure in starting up the WebLogic Server middle tier. Hence it is suggested to disable certain IPv6 components, except the IPv6 loopback interface, on Windows Server 2008.

SES Installation:

Right-click setup.exe in the ses_11_1_2_2_0_windows64 folder of the extracted files, and then click Run as administrator. The Installation Details page appears as below.
Enter a Search Server Name, Password, Port (Default port: 7777), Administrative password (Password needs to be 8 char with 1 letter and 1 number, and no special chars)


The installer will now install Web logic Server as the web server hosting SES and Oracle Database 11g EE to store the search indexes. After the installer finishes you will be presented with the summary screen containing three URL’s.
  • SES end user search page (the one that looks like Google)
  • SES admin console
  • Web logic admin console
At the completion of the install you get a window that displays some URL’s copy them off to keep.To get URL àIn cmd window, navigate to SES_HOME, give ‘searchctl.bat status’ command.


Web Logic Administration Console URL:  http://AMAZONA-K7L3KNU:7777/console

SES Configuration

Start the SES admin console and login with the password you supplied during SES installation http://AMAZONA-K7L3KNU:7777/search/admin/index.jsp


Username: eqsys (default)                          Password: < Administrative password>

Choose tab Global Settings and then click on Federation Trusted Entities.
This Entity Name and password are configured for inbound connections to SES and will be configured on the PeopleSoft side.


Enter an Entity name and provide a password. This does not need to be the password you supplied during installation of SES, but note this password; you will need to supply it in PeopleSoft later on.

The Identity Plug-in and Authentication Attribute options are left blank for this configuration.

Click Add and go back on the Global Settings tab, choose the link Identity Management Setup.
Select Plug-in PeopleSoft from the list and click on the Activate button.

The plug-in that you activate is responsible for all authentication and validation activity in Oracle SES.


On the next screen enter the PeopleSoft Integration Broker endpoint and userid and password of the default local node.


The User ID and Password here is a PeopleSoft user that has the ‘Search Framework Administrator’ role or permissions lists assigned.

Click Finish and go back to the Global Setting tab choose the link Query Configuration.


Change the timeout settings as shown above from the default values.
Add AUTO_CHARSET_DETECTION to $ORACLE_HOME/search/data/config/crawler.dat to enable Character set auto detection.  This is important to properly handle Unicode files and pages that may be indexed.  So I added the following lines to the end of the crawler.dat file
# enable automatic character set detection
AUTO_CHARSET_DETECTION

IB setup for Search Framework

  1. You need to have setup your Integration Gateway and load the connectors
  2. You should define your Gateway Default App Server and PeopleSoft Nodes in the Gateway Setup properties.
  3. On the Advanced Properties Page for the Gateway Setup you should define a secureFileKeystorePasswd
  4. You Local Node should be active and when if you ping it, it should come back with Success
  5. PUBSUB processes should be running on your application server domain
  6. Verify that your Service Configuration is correct.
  • Navigate to PeopleTools ->  Integration Broker ->  Configuration ->  Service Configuration
  • Click Setup Target Locations
  • Confirm the Web Services Target Location references the correct URL for your system.
7.             Configure Content RI and Portal URI text specified on the portal tab for the default Local Node you are working with. 

This is required, and you may get an error building your search index without it. 
You should also verify that the Service Operations needed for SES integration exist in your system. ADMINSERVICE and ORACLESEARCHSERVICE should both exist as Services.
  
Setting up PeopleSoft for Integration with SES

First thing you need to do, is to assign the Search Framework roles (Search Administrator, Search Developer, Search Server) to the user that is assigned to the default locale node.
Verify that required permission lists (PTPT3100, PTPT3200, and PTPT3300) are present on role PeopleSoft User.

Now navigate to Main menu –> PeopleTools –> Search FrameWork –> Administration –> Search Instance and create a Search Instance.
  • Enter the SES server and port
  • Enter the SES admin password you supplied during installation of SES (eqsys/welcome1)
  • Enter the Federation Trusted Entity and the password you created earlier in SES (PS/PS)
  • Enter the call back URL (endpoint of Integration Broker) and the userid and password of the default locale node

Verifying PeopleSoft and SES Connectivity

Now navigate to Main menu –> PeopleTools –> Search FrameWork –> Utilities –> Diagnostics


Click Step 1: Ping Test.  This should also work if your previous tests worked.  Once the Ping Test comes back it should make Step 2: Deploy an active link. You should be able to continue through to Step 4: Search and everything should work.

Create & Deploy Search Indexes

Now you have successfully completed the installation and configuration of the integration between SES and PeopleSoft.  You now have to ‘create search collections in PeopleSoft ‘and ‘feed these collections to SES’.  PeopleSoft Search Framework uses PSQuery and Connected Query as search collections.

Some search collections have already been supplied with the Feature Pack (Eg: HCM 9.1 FP2). If not you will have to create a Query and create a Search Index with the Query as input and then choose which Query fields should be indexed as keywords.

Search definitions are created and maintained in PeopleSoft.   Once the definition is deployed, we run the Application Engine PTSF_GENFEED via the Schedule Search Index page.  This AE will create a special SES feed in PeopleSoft and schedule the SES crawler to crawl the feed.

Navigate to Main menu –> PeopleTools –> Search FrameWork –> Administration –> Deploy/Delete Object.  Scroll to the bottom of the list of Search Definitions and select PTPORTALREGISTRY and click deploy.  Once successfully deployed the Deploy Status column will say Deployed. Next we build the index data (the feed) and tell SES to crawl the data.  In order to do this we run the Schedule Search Index job as previously mentioned.

Navigate to PeopleTools –> Search Framework –> Administration –> Schedule Search Index. Create a run control for each search index you want to publish to SES. Select PTPORTALREGISTRY as the search definition and select Full index for the Indexing type.  If you use the lookup it will only return deployed search definitions.  I left Language Option on Base Language as I only have one language available.  Click Run.

You can then schedule this and check process monitor to verify it completed successfully. This is to keep SES and PeopleSoft in sync. Once the job is completed, login to SES and go to the Sources tab of the Home tab.  You should see your search source, and then click the schedules tab; you should see that the index build was schedule for a one time run.
In the 9.2 applications certain functions won’t work until you’ve deployed the Search Definition and built the Index. It will throw an error like below screenshot.


Enable Global Search & Keyword Component Search

Now you have seeded SES with PeopleSoft data. You now need to enable the search feature in PeopleSoft. This can be done on two places.

To enable Global Search navigate to Main menu –> PeopleTools –> Portal –> General Settings and check Display global search in header. This will enable the embedded search in the portal banner. Make sure users have search indexes assigned through permission lists; otherwise they will not be able to run searches. 


This is a new tab in the Permission lists page in People Tools 8.52.
To enable Keyword search on Component Search pages, open the search index by navigating to PeopleTools –> Search FrameWork –> Designer –> Search Definition and on the last tab select the components where you want to add the Keyword search. This will change your search page with a new tab enabling Keyword Search.

I have replicated this post @ http://www.citagus.com/citagus/blog/oracle-ses-installation-configuration/

Wednesday, July 17, 2013

Oracle Upgrade from Oracle10g to Oracle11g


Below are the steps to Upgrade the Oracle database from 10.2.0.3.0 to 11.2.0.1.0:

Step 1) Installing Oracle 11g Home:

Install 11g database as a separate ORACLE_HOME in parallel to 10g Oracle Home.

Example my 10g Oracle Home is: D:\oracle10g\product\10.2.0\db_1, then my 11g Oracle Home is: E:\oracle\product\11.2.0\ db_1

Step 2) Pre-Upgrade Utility:

In 11g Home you installed, go to $ORACLE_HOME\rdbms\admin and copy the file 'utlu112i.sql' to some temp location (C:\temp).

Then login to the 10g oracle database AS SYSDBA and run 'utlu112i.sql' you copied to temp folder.

--This script provides information about databases to be upgraded to 11.2.

Step 3) Finding the Version of existing time zone files:

SQL> select * from v$timezone_file;

SQL> SELECT CASE COUNT (DISTINCT(tzname))
WHEN 183 then 1
WHEN 355 then 1
WHEN 347 then 1
WHEN 377 then 2
WHEN 186 then case COUNT (tzname) WHEN 636 then 2 WHEN 626 then 3 ELSE 0 end
WHEN 185 then 3
WHEN 386 then 3
WHEN 387 then case COUNT (tzname) WHEN 1438 then 3 ELSE 0 end
WHEN 391 then case COUNT(tzname) WHEN 1457 then 4 ELSE 0 end
WHEN 392 then case COUNT(tzname) WHEN 1458 then 4 ELSE 0 end
WHEN 188 then case COUNT(tzname) WHEN 637 then 4 ELSE 0 end
WHEN 189 then case COUNT(tzname) WHEN 638 then 4 ELSE 0 end
ELSE 0 end VERSION
FROM v$timezone_names;


If the output is 4, then it is well and good and it requires no additional steps.

If the output of this is < 4 then prior to upgrade we need to apply the Timezone patch.

SQL> select banner from v$version;


It gives DB version and accordingly you have to find the patch at Metalink. Download the zipped patch and unzip it in temp folder (C:\temp).

Step 4) Applying Timezone patch:

Copy the files from location: C:\temp\patch_file\files\oracore\zoneinfo and paste it to existing Oracle 10g location “D:\oracle10g\oracore\zoneinfo”. Make sure to keep backup of existing folder so that you could revert if any problem occurs.

Bounce the database and check the TIMEZONE version again. Again run the 'utlu112i.sql' and by now, the timezone file version should be upgraded.

Step 5) Gather Dictionary stats:

You may have found some warning messages in the output of 'utlu112i.sql' execution. Please do execute the below scripts to avoid those warnings.

Connect as SYS user,

SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;

SQL> EXEC DBMS_STATS.GATHER_SCHEMA_STATS ('SYS');

SQL> EXEC DBMS_STATS.GATHER_SCHEMA_STATS (‘SYSMAN’);  (if OEM in use)

After executing the above recommended steps, run the pre-upgrade utility 'utlu112i.sql' once again to make sure, you don’t get any critical warnings.

Step 6) Starting Upgrade:

Copy the PFILE from 10g home to 11g home. In the copied PFILE, change the COMAPATIBLE parameter from '10.2.0.3' to '11.2.0.1'.

Delete the old listener service (10g) & create a new one using ORADIM utility.

Set the environment variables as in the below example.

SET ORACLE_HOME=C:\oracle11g\product\11.2.0\dbhome_1
SET PATH=C:\oracle11g\product\11.2.0\dbhome_1\bin:$PATH
SET TNS_ADMIN=C:\oracle11g\product\11.2.0\dbhome_1\NETWORK\ADMIN
SET ORACLE_SID=FIN89COP

Connect as SYS user,

sqlplus “/ as sysdba” –> will be connected to idle instance

SQL> startup upgrade;

ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.

Then run the Catalog Upgrade ‘catupgrd.sql’ located in $ORACLE_HOME\RDBMS\admin.

SQL> @catupgrd.sql

--This script is to be used for upgrading a 9.2, 10.1 or 10.2 database to the new release.  This script provides a direct upgrade path from these releases to the new Oracle release.

Once the upgrades finishes, it will shut down the database automatically.

Step 7) Post-Upgrade Steps:

Login again as SYS and start the database in normal mode. 

SQL> STARTUP;

Check the dba_registry for the components and its status.

SQL> select comp_name,version, status from dba_registry;


Run utlu111s.sql to display the results of the upgrade:

SQL> @?/RDBMS/admin/utlu111s.sql


Run catuppst.sql, located in the ORACLE_HOME/rdbms/admin directory, to perform upgrade actions that do not require the database to be in UPGRADE mode:

SQL> @?/RDBMS/admin/catuppst.sql

Check if there are any invalid objects in the upgraded database.

SQL> select count (*) from dba_objects where status = ‘INVALID’;

If the invalid objects exist, run utlrp.sql to recompile.

SQL> @?/RDBMS/admin/utlrp.sql

SQL> select count (*) from dba_objects where status = ‘INVALID’;

This completes the upgrade.

Now the Pfile would be in 10g format. Shutdown the database, change the Pfile structure to 11g and bring it up.