Start two tomcat server instances in one machine

Here I am explaining how we can start two tomcat server instances in a single machine. Here I have configured tomcat instances for windows operating system, and edit the corresponding .sh files instead of .bat files for linux operating system.


To start two tomcat server instances in one machine, we need to edit the following configuration files.

1. Edit server.xml, tomcatfolder/conf/server.xml and edit the following entries,

<Server port="8005" shutdown="SHUTDOWN">

Change 8005 to another port number, say 9005

<Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
Change 8080 to another port, 8081

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />
change 8009 to another port, say 9009

2. Edit Server listener port. Default it is 8000

catalina.bat, tomcatfolder/bin/catalina.bat and edit the following entry

set JPDA_ADDRESS=8000

Change 8000 to 9000

startup.bat, tomcatfolder/bin/startup.bat and edit the following entry

set JPDA_ADDRESS=8000

Change 8000 to 9000

Now start both the tomcat servers one by one.

(13)Permission denied: make_sock: could not bind to address [::]:80

After installing and configuring the Apache on Linux, we may get this error while starting the Apache server.

To solve this, please check your user which logged with Linux  Permission denied means the current user does not have authority for this function. Root user can only bind with lower port addresses. Please login with root user and start the Apache server.

To know more about apace server installation and configuration, please follow my previous blogs.

Installation

Configuration

Webcenter Content integration with Webcenter Portal Spaces 11.1.1.6

Before integrating the webcenter content and webcenter portal, login webcenter content (http://<hostname>:<port>/cs).

If it is the first time access, please provide the intradoc port (4444) and ipfilter (allows remote access) details.

Go to 'Administration' --> 'Admin Server'

This will open in a new window.The main problem for this error is folders_g is not enabled and Framework folders might have enabled. But for creating a connection with webcenter portal framework or with webcenter spaces, we need
folders_g, then only we will get Contribution folder.

Select 'Folders' radio button, uncheck 'Framework Folders' checkbox. Then select 'Integration' radio button and check 'Webcenter Configure' checkbox.

After that goto top of the page and click on 'advanced component manager',

come to the enabled feature session, select Framework folders and disable it.
Come to the disabled feature session, select folders_g in the list and enable it.

Update the details.
This is prompting us to restart the content server for activating the changes. We will restart the server after the below changes.

Otherwise (if you had already accessed the page and if you forgot to provide the details), you can edit the intradoc port an in em console.
Login em console(http://<hostname>:7001/em)
Go to 'Webcenter' --> 'Content' --> 'Content Server' --> 'Oracle Webcenter Content - content server (UCM_server1)' and click on it.

Click on the 'Content Server' drop down, and click 'Configuration'.Provide the relevant details on each field. In IP Address filter, provide webcenter portal machine ip address also.
Apply the changes.

Go to 'Webcenter' --> 'Portal' --> 'Spaces' --> 'webcenter(11.1.1.4.0)(WC_Spaces) and click on it.
Go to 'Webcenter portl' dropdown box --> 'Settings' -->'Service Configuration'
Click on 'Content Repository' --> 'Add' and check the below entries for filling the details,

Connection name : Name for the integration. Provide any meaningful name.
Repository Type : Oracle Content Server
Active Connection - check the checkbox

Content Administrator - weblogic
Root Folder - /Webcenter1
Application name - WC1

RIDC Socket Type : Socket
Server host : Webcenter content runing host name
Server port : Intradoc Port number (Generally -  4444)

Webcenter Context root - cs
Administrator username - sysadmin

test the connection and apply the changes.

After this stop webcenter spaces and webcenter content managed servers and start webcenter content and then webcenter spaces managed servers.

Login webcenter spaces and check the document services for seeing the content integration.

Oracle database environment variables

Login with root user.

Open /etc/profile
     
        #vi /etc/profile

Add the following lines in profile before exporting the PATH environment variable. This will set the oracle database environment variables.


export ORACLE_HOME=/u01/app/oracle/product/11.2.0/xe
export ORACLE_SID=XE
export NLS_LANG=`$ORACLE_HOME/bin/nls_lang.sh`
export PATH=$ORACLE_HOME/bin:$PATH

VirtualBox webcenter Image - Introduction

Oracle VirtualBox session 2

In this session, I would like to explain how we can create a fully fledged Oracle webcenter vitualbox image.

For the Virtualbox introduction details, please cover my previous blog before get into this :)  since this is a series of session and it is advisable to follow from beginning.

Now we have installed Virtualbox on my windows 7 machine and I want a working environment for Oracle webcenter portal. 

Now we are going to create the virtualbox image for oracle webcenter portal and it requires the following set of components.

1. Operating system – Linux

a. Flavor – Oracle Enterprise Linux

b. Version – 6

c. Address bit – 64 bit

2. Database – Oracle

a. Flavor – Express Edition

b. Version – 11g

3. Oracle Fusion Middleware Repository Creation Utility 11g (11.1.1.6.0) for Linux x86

For loading the database schema for the oracle webcenter suite products.\

4. Oracle WebLogic Server 11gR1

Application server

5. Oracle WebCenter Portal 11g Patch Set 5

Webcenter Portal contains portal framework, spaces, discussion server, portlet and pagelets.

6. Oracle WebCenter Content 11g

Universal content management, re branded to webcenter content

7. Oracle JDeveloper 11g and Oracle Application Development Framework 11g (11.1.1.6.0)

                          Framework for developing adf, portal framework applications and customizing fmw products.

   

    After installing the Oracle virtualbox, we need to set preferences. Otherwise our images will store in ‘C:\Users\gireesh\VirtualBox VMs’ folder. To keep the machines in our directory, please set the Default machine folder.

We will continue this session and will create and configure a fully fledged webcenter portal image. 

    

VirtualBox - An Introduction.

Oracle VirtualBox session 1

I will cover these information in different sessions as I am configuring a full fledged webcenter virtualbox image. In this session I will cover the basic features of virtualbox, virtualization and virtualbox installation.

Here I would like to discuss about Oracle virtualbox, its features and how virtualbox can support us. Before get into the virtuabox introduction, we will download and install the virtualbox software into our machine.

I have downloaded VirtualBox-4.2.6-82870-Win.exe from https://www.virtualbox.org/wiki/Downloads website and started installing the virtual box in my machine.

Please follow the below screenshots for more clarification.

 

 Virtualbox installation is over and I am starting the virtual box.

Let us explore the features and functionality of virtual box.

Virtual box is a software for supporting cross platform virtualization. Now what is virtualization ?

Previously we were installing sotwares on the physical machine and once our work was done we used to uninstall the softwares and install another set of softwares for next work. This was a very time consuming process and multiple works cannot be done simultaneously. To avoid these issues, industry released a new term ‘virtualization’.

Using virtualization concepts, we can create a virtual images on the physical machine and that will utilize or extend the physical machine resources. And we can create images with any operating system and any set of softwares. While working with virtual box, it would be advisable to know the following terms because we always use those terms for communication.

Host Machine – It’s the physical machine.

Host operating system (Host OS) – The operating system running in the physical machine.

Guest Machine/Virtual Machine – It’s the virtual box image

Guest OS – The operating system running in the virtual box image.

Guest additions – It is special software designed for guest os to improve the performance and providing additional functionality.

Import Virtual Machine – The virtual machine or image is already developed by some at different lace and if we want to use that machine here, we need to import the virtual machine files with existing configuration or settings.

Export Virtual Machine – The virtual image we have developed for other people. While exporting, the image will keep all the settings and configurations as such.

Display username in wsrp portlet that integrated in webcenter portal

We need to display the security context logged in username in portlet , that is integrated with webcenter portal application. The portlet application does not have security context initialized, so it should pick it from the portal security.

We have two application for this exercise.

1. Create a portlet application.

We have multiple ways to create a WSRP portlet application.
Example :

1. Create Fusion middleware application, create adf taskflow and convert it to portlet entry
2. Create 'Webcenter Portal - Portlet producer application

Here I am following  second approach, since most of us know the first approach well.

After creating the webcenter portlet producer application, create a JSR286 portlet and select jspx for view.

Edit the view.jspx with the following entries,

<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
          xmlns:f="http://java.sun.com/jsf/core"
          xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
  <jsp:directive.page contentType="text/html;charset=windows-1252"/>

  <f:view>
    <af:document>
      <af:form>
      <af:panelGroupLayout id="pgl1" layout="vertical">
     
        <af:outputText value="username is" id="ot3"/>
        <af:outputText value="#{securityContext.userName}" id="ot4"/>
        </af:panelGroupLayout>
      </af:form>
    </af:document>
  </f:view>
</jsp:root>


Open portlet.xml, and add the container runtime options as 'com.oracle.portlet.useWsrpUserContextForUserAuthenticationInfo' and value is 'true'

Now we can deploy the application and will go to the second application.

If you want to know how to develop a portlet producer application step by step, click here

2. Create a Portal application

Create a webcenter portal framework application and create an authenticated page. Create a WSRP producer in application resources connection and register with the
abover portlets wsdl.

Run the application, and login with application server user and you can see that the portlet is displaying the logged in username.

Download the source projects from here 

ADF ViewObject Query customization using a binding variable

Click Here

ADF code for retrieving currently logged in user

Click Here