Oracle WebCenter Portal 11g Developer Workshop Lab 00 Preparing the Environment Page 1 of 10
Overview For this workshop, you will use the Oracle WebCenter Portal Jump Start Kit, which is a utility that automates the installation and configuration process for WebCenter Portal 11.1.1.8. You will also need to download and install JDeveloper 11.1.1.7 to develop Portal components. To interact with WebCenter Content and Site Studio, you will need to install the Desktop Integration Suite and the Site Studio Designer applications. To develop mobile applications, you will need JDeveloper 12c and the SDK for your mobile operating system. Finally, you will need to do some basic configuration to get your environment ready for the labs. The goal of this lab is to prepare the Portal instance for the labs of this workshop. The basic preparation steps are: 1. Download and Install the required software 2. Unzip and prepare the JDeveloper project 3. Create the OraHealth folder and subfolders in Content Server 4. Copy the lab files to the OraHealth folder 5. Create the Database objects IMPORTANT: This workshop is based on the WebCenter Portal Jump Start Kit (JSK), which is only available for Linux64 environments. If you have an existing Portal installation, or if you plan to install WebCenter Portal in another operating system, you can still run the labs, since this workshop has no other pre-requisites. Just make sure to check the port numbers and connection names to avoid issues during the labs. REQUIREMENTS: In order to install the JSK, a Linux environment is required. It s recommended to have 10GBs of RAM to run the JSK. SERVER URL: During the labs, there will be several references to the Portal URL. The http://server/... standard will be used, so you will need to replace this address with your server s URL. Page 2 of 10
Instructions Preparing the Portal Environment Please download and install the required software listed below. Oracle WebCenter Portal Jump Start Kit The Jump Start Kit includes all software products required to install WebCenter Portal, and scripts to automate installation and configuration. Go to the following link and download all required software: http://www.oracle.com/technetwork/middleware/webcenter/portal/downloads/default-2184086.html Make sure to read the instructions on how to setup and install it. Make sure you can access the Portal from your desktop. There will be 3 types of development in this workshop: developing assets for WebCenter Portal, creating Site Studio definitions and developing a Mobile application. To be able to go through all of these exercises, you need to install the following products on your desktop: Oracle JDeveloper 11.1.1.7 http://www.oracle.com/technetwork/developer-tools/jdev/downloads/jdeveloper11117-1917330.html Oracle WebCenter Portal Extension for JDeveloper 11.1.1.7 Can be installed through the Help -> Check for Updates menu in JDeveloper, or offline through this URL: http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/156082.xml If you already have JDeveloper and the extension installed, make sure to check for updates, because Portal 11.1.1.8 requires the latest version of the extension. Oracle Site Studio Designer 11.1.1.8 Can be installed by accessing Content Server (http://server:7777/cs/) and going to the My Content Server -> My Downloads link (PS: This software is only available for Windows). Desktop Integration Suite 11.1.1.8 Page 3 of 10
It can be downloaded from the same link as the Site Studio Designer (above). PS: To create a connection with the Content Server, use the following URL: http://server:16200/_dav/cs/idcplg/webdav Oracle JDeveloper 12c (12.1.3.0.0) This version is required to develop applications with Mobile Application. http://www.oracle.com/technetwork/developer-tools/jdev/downloads/index.html Oracle MAF Extension for JDeveloper 12.1.3.0.0 Can be installed through the Help -> Check for Updates menu in JDeveloper. Make sure to install the Mobile Application Framework and the Mobile Application Framework JDeveloper Patch extensions. Android SDK / ios SDK In order to deploy and test your mobile application, you will need to have an Android or ios mobile device and the SDK already configured in your desktop. Follow the instructions in these pages to prepare your environment for mobile development: ios: http://docs.oracle.com/cd/e53569_01/tutorials/tut_jdev_maf_setup/tut_jdev_maf_setup.html Android: http://docs.oracle.com/cd/e53569_01/tutorials/tut_jdev_maf_setup/tut_jdev_maf_setup_2.html If you don t have an Android/iOS mobile device, you will need to use an emulator to test your application. Follow the instructions in the links above to set it up. Preparing the Portal Extension Project Download the DesignWebCenterSpaces_11.1.1.8.0.zip file from the link below and unzip it to a folder on your desktop. IMPORTANT: make sure the path has no spaces in it (like c:\portal\designwebcenterspaces); otherwise you could run into errors while running the projects. Follow the instructions in the page to setup JDev for Portal development: http://docs.oracle.com/cd/e29542_01/webcenter.1111/e27739/jpsdg_wcsres.htm#jps DG14429 Preparing the Database Page 4 of 10
1. First we need to unlock and configure the HR user in the database. If you don t have SQL Developer, you can use JDeveloper for these steps. Create a connection to the system schema. 2. Once the connection is created, right-click on it and select Open SQL Worksheet. Page 5 of 10
3. Execute the following command to enable the HR account: o alter user hr identified by hr account unlock; 4. With the HR user unlocked, you can now create a connection to it. Page 6 of 10
5. Now you will create the database tables and other constraints that will be used by the portlet. The following diagram displays the tables and their relationship: Page 7 of 10
6. You can find the scripts to create the tables in the lab_assets/scripts folder. Execute the scripts in the following order: o All seq_* files (6 files) o Doctor.sql o Patient.sql o Consultation.sql o Medication.sql o Problem.sql o Vital.sql Preparing the Content Server 7. Login to Content Server (http://server:7777/cs/) as weblogic. 8. Expand Browse Content and click on Contribution Folders. 9. In the New Item menu, select New Folder. 10. Set the name as OraHealth and the Security Group as Public. PS: Pay attention to the upper case characters (O and H). This can make a difference. Page 8 of 10
11. Click on Save to create the folder. Open this folder. 12. Create 4 new folders inside the OraHealth folder, all with Security Group Public: o css o images o js o wikidocs 13. Inside the images folder, create 2 more folders, also Public: o doctors o patients 14. Upload all files in the folders located in the lab_assets/orahealth folder to their corresponding folders in the Content Server. o The best way to do it is through Windows Explorer (just copy and paste the files into the folder using the Desktop Integration Suite application for Windows Explorer). Page 9 of 10
Oracle WebCenter Portal 11g Developer Workshop LAB 00 Preparing the Environment September, 2014 Author: Denis Abrantes Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 oracle.com Copyright 2014, Oracle. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle, JD Edwards, PeopleSoft, Fatwire and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Page 10 of 10