Oracle 11G R2 字段启用培训实验室 - 快速入门指南说明书

OIG 11G R2 Field Enablement Training
Lab1 - Getting Started Guide
Disclaimer: The Virtual Machine Image and other software are provided for use only during the workshop. Please note that you are responsible for deleting them from your computers before you leave. If you would like to try out any of the Oracle products, you may download them from the Oracle Technology Network (/technology/index.html) or the Oracle E-Delivery WebSite ()
Table of Contents
OIG 11G R2 Field Enablement Training (1)
Getting Started Guide (1)
1. Introduction (5)
1.1 VM Specs (5)
1.2 Installed Software (5)
1.3 System Requirements to run the VM (5)
1.4 General Instructions (5)
2. VM accessibility (5)
3. Database Details (7)
3.1 Installation Directory (7)
3.2 Details (7)
3.3 General Users (7)
3.4 Specific Users (7)
3.5 Startup and Shutdown (7)
4. Weblogic Details (8)
4.1 Installation Directory (8)
4.2 Details (8)
4.3 Weblogic URLs (8)
4.4 Startup and Shutdown (8)
5. Oracle Identity Manager (OIM) Details (9)
5.1 Installation Directory (9)
5.2 Details (9)
5.3 URLs (9)
5.4 Startup and Shutdown (9)
6. SOA Details (10)
6.1 Installation Directory (10)
6.2 Details (10)
6.3 URLs (10)
6.4 Startup and Shutdown (10)
7. Oracle Universal Directory (OUD) Details (11)
7.1 Installation Directory (11)
7.2 Details (11)
7.3 Startup and Shutdown (11)
8. Miscellaneous Items (12)
8.1 Tomcat Server (12)
8.2 HR Application (12)
8.3 BI Publisher (12)
8.4 JES (12)
8.5 Thunderbird Client (12)
8.6 JDeveloper (12)
8.7 SQL Developer (12)
8.8 LDAP Browser (Apache Directory Studio) (13)
9. Installing OIM Customization Installer Extension on JDeveloper (14)
9.2 Using OIM Customization Installer Extension for OIM Plugins (19)
9.3 Verification of plug-in deployment / undeployment from JDeveloper (21)
Appendix – Tips (33)
Changing the UI (33)
Issue with Connection pools: (33)
Appendix – Running the VM in a no network situation (34)
To Disable DNS (34)
To Enable DNS (34)
1. Introduction
A virtual machine with the following specifications is provided to the Training attendees.
1.1 VM Specs
Operating System: Oracle Enterprise Linux 5.5
Host Name:
1.2 Installed Software
1.Oracle Identity Manager 11g R2 PS2 11.1.
2.2.0
2.Oracle Weblogic Server 11g 10.
3.6.0
3.Oracle Unified Directory 11g 11.1.2.0
4.Oracle Database 11g Enterprise Edition 11.2.0.1.0
5.Sun JDK 1.
6.0_31
6.JES
7.Thunderbird Client
1.3 System Requirements to run the VM
1.Download and install the VirtualBox. We will be using Virtual Box to run the image.
2. A 64-bit host operating system
3. A laptop/server with at least 16gb of free memory, 100gb free disk space
4.The image is distributed with Bridged networking and DHCP enabled
1.4 General Instructions
1.For all the passwords, for every known account or installation, Oracle123 has been used.
2.All the necessary Environment variables are set for OIA, OIM, Oracle Database and ODSEE.
3.The RIGHT CTRL key is the HOME key for the virtual machine.
4.Pressing RIGHT CTRL + G resizes the VM window as per desktop display settings.
5.Pressing RIGHT CTRL + F takes the VM into full screen mode. To return to your laptop view,
press RIGHT CTRL + F again.
6.For all the browser based activity, it is suggested to refer the URLs from the physical machine us-
ing the IP Address of the virtual machine.
7.Or set the IP Address to the hostname in your /etc/hosts file.
8.Remove any IP Settings for the VM Net or VBox Adapters. They can be found in the Networking
and Sharing Center on window.
2. VM accessibility
Use the below credentials to login to the VM operating system.
All the exercises and any other activity on the VM have to be executed using the above login credentials only.
In case the super user access it required then use the below credentials.
3. Database Details
3.1 Installation Directory
/app/db/product/11.2.0/dbhome_1
3.2 Details
Database details
SID: orcl
3.3 General Users
The default credentials are as below.
Login: sys as sysdba
Password: Oracle123
3.4 Specific Users
A user for the OIM database tables has been created. The credentials are as below.
Login: DEV_OIM
Password: Oracle123
Login: DEV_MDS
Password: Oracle123
A user for the SOA database tables has been created. The credentials are as below.
Login: DEV_SOAINFRA
Password: Oracle123
A user for the OPSS database tables has been created. The credentials are as below.
Login: DEV_OPSS
Password: Oracle123
3.5 Startup and Shutdown
The database starts up along with the booting of the VM. Just in case, the startup script is placed on the Desktop in Startup_Scripts.
Name: startDB.sh
Double click on the script and allow it to run in terminal.
The respective shutdown script is placed on the Desktop in Stop_Scripts.
4. Weblogic Details
4.1 Installation Directory
/app/Middleware/wlserver_10.3
4.2 Details
WLS credentials
Login: weblogic
Password: Oracle123
4.3 Weblogic URLs
Weblogic: :7001/console
Enterprise Manager: :7001/em
OES – APM: :7001/apm
4.4 Startup and Shutdown
The startup script is placed on the Desktop in Startup_Scripts. Name: startAdmin.sh
Double click on the script and allow it to run in terminal.
The respective shutdown script is placed on the Desktop in Stop_Scripts.
5. Oracle Identity Manager (OIM) Details
5.1 Installation Directory
/app/Middleware/Oracle_IDM1
5.2 Details
To login to OIM console, you may use the below credentials.
Login: ADMIN
Password: Oracle123
To login to Design Console, you may use the below credentials.
Login: XELSYSADM
Password: Oracle123
5.3 URLs
HTTP URL:
:14000/identity
:14000/sysadmin
HTTPS URL:
https://:14001/identity
https://:14001/sysadmin
5.4 Startup and Shutdown
5.4.1 OIM Managed Server
The startup script is placed on the Desktop in Startup_Scripts.
Name: startOIM.sh
Double click on the script and allow it to run in terminal.
The respective shutdown script is placed on the Desktop in Stop_Scripts.
5.4.2 Design Console
The startup script is placed on the Desktop in Startup_Scripts.
Name: launchDesignConsole.sh
Double click on the script and allow it to run in terminal.
Just exit design console UI. There is no requirement for a stop script for this.
6. SOA Details
6.1 Installation Directory
/app/Middleware/Oracle_SOA1
6.2 Details
To login to the SOA utilities, use the below credentials.
Login: WEBLOGIC
Password: Oracle123
6.3 URLs
:8001/soa/composer/
:8001/integration/worklistapp
6.4 Startup and Shutdown
The startup script is placed on the Desktop in Startup_Scripts. Name: startSOA.sh
Double click on the script and allow it to run in terminal
The respective shutdown script is placed on the Desktop in Stop_Scripts.
7. Oracle Universal Directory (OUD) Details
7.1 Installation Directory
/app/oud
7.2 Details
Ldap port: 2389
Admin port: 5444
Credentials: "cn=Directory Manager" / Oracle123
OUD Oracle home: /app/oud/OracleUnifiedDirectory
OUD instance: /app/oud/asinst_1
DN: dc=example,dc=com
7.3 Startup and Shutdown
OUD starts automatically upon booting the VM. The startup script is placed on the Desktop in Startup_Scripts.
Name: startOUD.sh
Double click on the script and allow it to run in terminal
The respective shutdown script is placed on the Desktop in Stop_Scripts.
8. Miscellaneous Items
8.1 Tomcat Server
Tomcat server is installed in /app and boots along with the VM. This helps in loading the launcher page which shows the URLs of the all installed applications.
:8080
8.2 HR Application
A HR application is installed. This application may be used to simulate onboarding of users via HR appli-cation. To start the application OIM Managed Server has to be booted.
:14000/hr
8.3 BI Publisher
BI publisher can be started by invoking the below startup script.
startBIP.sh
:9704/xmlpserver
8.4 JES
The Java Email Server starts along with the VM.
8.5 Thunderbird Client
The thunderbird client can be accessed by clicking on the Thunderbird icon on the top panel in the VM. It has two accounts configured.
*******************
************************* Danny is the manager for most of the users in the exercises.
8.6 JDeveloper
The startup script is placed on the Desktop in Startup_Scripts.
Name: launchJDEV.sh
JDeveloper Home: /apps/Middleware-jdev/jdeveloper
Double click on the script and allow it to run in terminal.
Just exit Jdeveloper UI. There is no requirement for a stop script for this.
8.7 SQL Developer
The startup script is placed on the Desktop in Startup_Scripts.
Name: launchSQLDeveloper.sh
Double click on the script and allow it to run in terminal.
Just exit SQL Developer UI. There is no requirement for a stop script for this.
8.8 LDAP Browser (Apache Directory Studio)
The startup script is placed on the Desktop in Startup_Scripts.
Name: launchApacheStudio.sh
Double click on the script and allow it to run in terminal.
Just exit Apache Directory Studio UI. There is no requirement for a stop script for this.
8.9 Software
The software needed for some of the labs like connector server etc.. is in /app/software directory
8.10 Lab Sample Files
The supporting files for the labs are in /app/dummydata directory
The support files for web services connector is in /app/assets directory
9. Installing OIM Customization Installer Extension on JDeveloper
Before using OIM Customization Installer, JDeveloper 11.1.1.x should be installed on the system, which has been done already on the VM.
For any customization that has to be deployed using this framework, below folder structure should be followed to package its source as it should show up in the JDeveloper IDE. The package of all the cus-tomization artifacts that will be used in this training course, already follow this recommended structure.
Please note that the above folder structure is mandatory. A directory can be left empty, but should not be missed out from the folder structure.
Install OIM Customization Installer Extension on JDeveloper
1.Open the JDeveloper utility.
2.Click OK on the options screen.
3.Select Help Check for Updates.
4.Select Install from Local File from the wizard.
5.Browse (directory location /app/software/customizationinstaller/R2PS2) and select the oim-
customization-installer.zip package and click Next.
6.Click on Finish.
7.Restart JDeveloper; you are automatically prompted for it.
Reinstall OIM Customization Installer Extension on JDeveloper
Note: JDEVELOPER-HOME = /apps/Middleware-jdev/jdeveloper
Manually delete all the files from the {JDEVELOPER-HOME}/jdev/extensions folder (See the screenshots below).
{JDEVELOPER-HOME}/jdev/extensions/OIMCustomizationInstaller.jar (JAR file to be deleted)
{JDEVELOPER-HOME}/jdev/extensions/oracle.ide.lcm (Folder to be deleted)
Other backup files such as OIMCustomizationInstaller.jar.backup may also be deleted. However it is not necessary that you delete them.
To Install/Reinstall OIM Customization Installer, the process of reinstallation of JDeveloper is similar as installation. If plug-in is already installed then JDeveloper will show below screen.
Java Project Build Path settings in JDeveloper
Please make sure you have added all required jar files for your plug-in java project in JDeveloper.
1.Select desired project and right click on Project Properties.
2.Select Libraries and Classpath and click on Add JAR/Directory.
3.Browse and add required JAR from local disk.
9.2 Using OIM Customization Installer Extension for OIM Plugins
1.After restart, “OIM customization installer” Menu will be displayed under “Tools”.
2.Select OIM customization installer Configure.
3.Provide the below values.
4.After saving the configuration details, user can verify connection using Test Connection button.
5.Before trying to deploy any project, please make sure you have added the dependent JAR files in
the project classpath and have good package folder structure in place.
6.If you wish that these dependent JAR files should also be moved to OIM, then copy these files to
[PROJECT-CONTEXT]/lib folder.
7.To perform single click deployment of implemented plug-in in JDeveloper, navigate to Tools →
OIM customization installer → Deploy
8.If the deployment is successful, a success dialog will be shown.
9.If the deployment fails, a failure dialog will be shown.
10.If a plug-in is not already installed, it will show up an error window.
11.To perform single click undeployment of deployed plug-in,
12.“Tools” -> “OIM customization installer”-> “undeploy”
13.If the undeployment is successful, a success dialog will be shown.
14.If the deployment fails, a failure dialog will be shown.
9.3 Verification of plug-in deployment / undeployment from JDeveloper Creating Database Connection in JDeveloper
1.Open JDeveloper and select File → New.
2.Select General → Connection →Database connection.
3.Fill all required information to create OIM Database.
4.Verify connection status to OIM Database using Test Connection.
5.Open Resource Palette to navigate the created database connection.
6.You can see created database connection in Resource Palette
7.Create Database connection to MDS and verify using Test Connection
8.You can verify database connection under Resource Palette.
Creating SOA- MDS Connection
1.Select File New from the File menu in JDeveloper window.
2.Create SOA-MDS Connection. [This option will be available only if the Oracle SOA Composite Edi-
tor extension is installed on JDdeveloper. This can be downloaded from Oracle SOA Composite Editor].
3.SOA-MDS connection is nothing but a user-friendly interface to view MDS database details. All
the metadata files that have been imported in MDS can be viewed easily in a hierarchical tree structure.
4.Create SOA –MDS connection.
5.Please make sure you have selected Connection to MDS database and MDS partition as oim.
6.You can view all uploaded Metadata files using SOA-MDS connection in hierarchical tree struc-
ture.
Verification of deployed plug-in
1.Verify plug-in table in OIM DB
2.Open database navigator.
3.Open SQL worksheet
in plugin.xml while deployment.
5.You can verify the ID of plug-in in result query.
6.The same id was provided in plugin.xml.
7.Verify SOA-MDS partition.
8.Verification of undeployed plug-in
9.Verify plug-in table in OIM DB
10.Verify SOA-MDS partition.
Appendix – Tips
Changing the UI
The OIM Self service console shown in the VM is not the OOB UI. To show different launch pages do the following.
1.Login to Sysadmin console.
2.Click on System Configuration under System Management.
3.Search for a property by name Homepage for Self Service Console.
e the below values according to requirements.
Issue with Connection pools:
Before starting OIM/SOA, can you verify that you can connect to the OIM and SOA database via SQL De-veloper from the Developer Tools on the Desktop? The connections are already configured.
Usually, this problem occurs when you change the networking and DNS is no longer configured correct-ly. You can disable DNS by editing /etc/nsswitch.conf and commenting out the files dns entry as follows:
# jwalsh: Disable DNS if needed by commenting the file dns entry, and uncommenting the files entry hosts: files
#hosts: files dns
After doing this, you should reboot the image.
Appendix – Running the VM in a no network situation
By default, the image is shipped with DNS enabled assuming operation on a connected network such as at home, OSC, or DSS. Disabling DNS is required for operation on disconnected networks, such as on an airplane or in a customer environment. If you are working off-network / host-only mode, you should disable DNS to prevent networking issues. You should disable DNS in the /etc/nsswitch.conf per the notes below.
To Disable DNS
• Open a Terminal Window in the image
• $ sudo vi /etc/nsswitch.conf (Switch the comments as noted in the file)
To Enable DNS
• Switch the comments above. Reboot the image, and restart all services.。