end-to-end installation of fmw11g

8/6/2019 End-To-End Installation of FMW11g

1/60

End-to-end installation of WebCenter and BPM 11g (64-bit)Posted on September 20, 2010by Mark Nelson

In this post we will present a complete end-to-end i nstallation and configuration of Oracle BPM 11.1.1.3, including

Oracle WebCenter 11.1.1.3 for the Process Portal, Spaces and Composer features, on the Oracle Enterpr ise Linux

5.4 64-bi t operating system, wi th Oracle Database 11.2.0.1.

The system used in this post is a vir tual machine running on Oracle VM 2.2. The guest has 8 cores, 24GB of

memory, 160GB of disk and 18GB of swap space. I t i s runni ng Oracle Enterpr ise Linux Release 5 Update 4.

Everything is 64-bit (unless otherwise stated).

I f you want to complete thi s installati on on a single machine, you are going to want to have at least 12GB of

memory and 4 cores. Otherwise it may be a lit tle bit slow. You could also install the vari ous components on

different machines, and in fact you probably would in a real production installation.

This post wi ll help you set up everything you need to get started with BPM, including the runt ime environment for

business processes, the web-based Process Composer which allows business users to edit their processes, the

workli st that allows business users to process tasks, and dashboard reporti ng.

I t wi ll also guide you through confi gurati on of the Process Portal feature, which provides a whole stack of social

BPM capabilit ies, including the abili ty for end users to create self-service collaboration spaces to share

information around processes and process instances.

Note: I t is possible to use BPM without t he Process Portal feature. I f you were to do that, you could leave out

about two thirds of the steps in this post!

Preparation

We created an operating system user and group, both called oracle, which wi ll be used as our normal users to

install and run the software.

Before we start t he actual installation, we have a couple of housekeeping tasks to take care of. The virtual machine

is confi gured wit h a stati c IP address and hostname, and the DNS servers are configured. This can be done using

the system-config-network command, and by updating the/etc/ hosts file to include a line for t he static IP

address and hostname you have chosen.

The virtual machine is also configured to use the Oracle Unbreakable Linux Network so that we can easil y install

updates and packages as required. You need to be an Oracle Enterprise Linux customer to use thi s facili ty. I f you

are not, you will need to download and install the packages individually, or use some other package management

application to do thi s.

In order to install the Oracle Database, we need to meet a number of prerequisit es. Almost all of thesecan be

handled with one simple command. Note that throughout th is post, commands that are shown with a # prompt

must be issued as root.

Page1 of 60End-to-end installation of WebCenter and BPM 11g (64-bit) | RedStack

5/23/2011http://redstack.wordpress.com/2010/09/20/end-to-end-installation-of-webcenter-and-bpm-...


2/60

# yum i nst al l or a cl e- v al i dat ed

At the time of writ ing, two packages are missing, so you will also need to install them manually, using the

following commands:

# yum i nst al l l i bai o- d ev el

# yum i nst a l l uni xODBC- devel

Install Database

Now we are ready to install the Oracle Database. In this post, we are using Oracle Database 11.2.0.1 Enterpr ise

Edit ion (also known as 11g Release 2).

First, we will create directory to install the database into, and give our oracle user access to this directory.

# mkdi r / u01

# chown or ac l e: orac l e / u01

Now we can run the installation program

or ac l e$ . / r u nI ns t a l l er

The installation program wil l launch and we need to step through a number of screens. Firstly, you can provide

your Oracle Support details if you want to get automatic securi ty updates from Oracle. If not, just uncheck the box

and click on theNext button.

You wil l be asked to confirm that you do not want the securit y updates. Cli ck onYes.




3/60

On the next screen we select what we want to do, leaveCreate and configure a database selected and click on

Next.

For our installati on, we are going to use a Server Class database. You can choose Desktop Class if you want

to, everything wil l still work, but our choice here wil l give us some more flexibili ty. Cli ck on Next.

In this case, we will j ust run a single instance of the database, not a cluster. Cli ck on Next.

We are going to want to change some of our sett ings from the default s, li ke our database character set for

example, so wewant t o choose Advanced I nstall here and cli ck on Next.




4/60

Click Next to choose English as the language to install. (Feel fr ee to install in your own language.)

We will use the Enterprise Edition of the Oracle Database in t his example. Any of the database editions willwork, so choose the one that you are licensed for, then click on Next.

Now we need to specify where we want to install the database. We put ours in /u01 the directory we created

earlier. The Softwar e Location wil l be automaticall y determined based on the Oracle Base you specify. Click

on Next.

As this is our fir st i nstallation, we need to create our inventory. This may not happen in your environment, if

you have installed other Oracle products previously. Here we just need to provide the location for t he inventory.

We put i t in our home dir ectory, as shown below. Click on Next to continue.




5/60

Wow! A lot of questi ons here! We are almost done. Next, we need to decide what kind of database we want. We

are going to use the General Purpose / Transaction Processing option and click on Next.

Now we need to define ourGlobal database name and Oracle Service Identifi er ( SID) . Here we are just

going to use obpm for both of t hese. I f you have a number of Oracle database instances in your environment

already, your Database Administrators may have some standards for these, which you might want to comply wi th.

They are pretty hard t o change later! Enter whatever values you wil l use, and cli ck on Next.

Now we get to memory and character sets. We defini tely want to make some changes here. By default , the

database wil l take around 40% of the physical memory. This is a lot of memory for us to give up, and given our

workload, it is not really necessary. We set our database to use only 1,024 MB of memory as shown below. This

wil l be more than enough for our intended usage. I f you are installi ng a production envir onment, you wil l

probably want more you should check the documentation for recommendations. Dont click on Nextjust yet.

We also need to make some changes on the Character sets tab.




6/60

Change the sett ing to Use Unicode (AL32U TF8) . We need this character set to support the data that our other

products wil l want to keep in the database. Now click on Next to continue.

In this example, we are not using Grid Control, so just take the default opt ion here to Use Database Contr ol

for database management. Feel free to turn on email noti fications if you wish. Click on Next to continue,

Now we need to tell the installer where we want to keep our database fi les. In our case we are just going to use the

File System , nothing fancy. Leave that selected and provide a location to keep the fi les. We

used /u01/oradata as shown below. Cli ck on Next.




7/60

I ts a good idea to Enable automated backup . You may be happy you did one day! Cli ck on Next .

We used the same password for all of the system accounts. You can do the same, or provide dif ferent passwords

for each account. This wont make any difference to our i nstallation. Complete either the top or bottom part of

this screen and then click on Next. Now, thi s may seem obvious, but you would be surpr ised how often we get

support calls from people who did not bother to remember the passwords! Make sure you remember your

passwords you will need them later.

On the next screen we set the operating system user and group that the database wil l run under. In our

envir onment these are both called oracle. Then click on Next.




8/60

At this point , the installer wi ll check if there are any addit ional packages requir ed. There should not be any, but

depending on our choices in t he installer, there may be. In our case there were two, as shown below. You wil l

need to i nstall these (using yum for example) and then click on Next .

Once all the packages are installed, the installati on summary screen will be displayed. We are finally ready to

actual ly install this database! Cli ck on the Finish button to get started!

As the installation runs, you wil l see the progress windows (below) update to provide you information about what

is happening.

After t he installation phase is completed (i .e. after all the product bi naries have been installed), the Database

Configur ation Assistant wil l r un. This is the part t hat creates your actual database instance.




9/60

When thi s is completed, you will get a final screen showing you detail s of what was done. You are probably going

to want to keep a copy of the information on this screen i f you are not famil iar with the Oracle Database already.

Click on OK when you are ready to go on.

At this point, we need to run a couple of scripts as the root user. Open a terminal windows as root, and run the

indicated scripts. Once these are completed, click on the OK button ton continue.




10/60

Congratulat ions, you now have a shiny new Oracle 11g Release 2 database instal led!

Install WebLogic Server

The next phase of our installation is to install WebLogic Server. Most of the remaining components run on top of

WebLogic Server. In thi s post, we are using the WebLogic Server 10.3.3 installer. You can download this fromedelivery.oracle.com if you have a li cense, or otn.oracle.com if you want t o take up the development li cense

option. Once you have it downloaded and unzipped, invoke runInstaller. After a few moments, the installation

intervi ew wil l appear, as shown below. Click Next to get started.




11/60

On this page, we need to tell t he installer where we will create our new Middleware Home. We used / u02 . The

Middleware Home is the location where all of the product binaries wil l be installed, and addit ionally where we wil l

create our data files as we create (one or more) domains. You will want to make sure you have at least 5GB of free

space in t he Middleware Home. I f you want to put i t on a separate disk, or a RAID group, to improve

performance, you should cancel the installation and go and set t hat up now and mount it on / u02 or wherever

you choose to put your Middleware Home.

Note that you can have more than one Middleware Home on a (vir tual or physical) machine (or operating system

image) and that these can contain dif ferent products and/ or di fferent versions of products.

On the next page you can provide your Oracle Support detail s, or uncheck the box and cli ck on Next as we did.

Choose Typical for your installation type and click on Next. In this example, the typical installation is fine for

what we need.




12/60

Now we need to select the JDK to use. The installer should automatically detect your JDK and l ist i t for easy

selection, as shown below. I f your JDK is not found automatically, or you want to use a different one, click on the

Browse button to locate it . Otherwise, just click on Next.

You can change the product installation directories on thi s screen. We wil l just accept the defaults and click on

Next.




13/60

Now we are presented with the summary, click on Next to start t he installation.

As the installation runs, we can see it s progress.




14/60

When it is completed, uncheck the Run Quickstart option and click on Done to leave the installer. I f we were

just installi ng WebLogic Server, we would go ahead and run the Domain Configurati on tool now. However, we are

also planning to install additional products, so we wil l r un it later on, after those other products are installed.

Run the Repository Creation Uti li ty

Now we wil l set up the necessary schemas in the database to hold data for the various products we are planning to

install. This is done using the Repository Creation Utilit y. Again, you can download this from edli very or

OTN. You want the 11.1.1.3 version, which includes the schemas for Oracle Business Process Management. I t i s

not necessary to run the 11.1.1.2 version fi rst. Note that there is not a Linux 64-bit version of the download. You

can just use the 32-bit version. This tool i s just used dur ing the installation, to create objects in the database, it is

not part of the running system.

After you have downloaded and unzipped it, invoke runInstaller from the rcuHome/bin directory. After a fewmoments, the installation interview will appear. Click on Next to get started.

Select the option to Create the database schemas and click on Next.




15/60

On the next screen, we need to provide details to connect to our database (which we installed earl ier) . Enter the

hostname of your machine, the port number ( the default por t i s 1521), the service name (this is the SID that we

created earlier) , sys as the username and the password that you set duri ng the database installation. The rolewill default to SYSDBA.

At this point, we need to pause to di scuss the Oracle Database Listener. This is a component of t he database that

is responsible for managing incoming connections. When you created the database instance (a few minutes ago)

it also created a set of configuration fi les for the li stener. These are located under the network/admin directory

in the database home and are called listener.ora and tnsnames.ora . I f you have a problem connecting to your

database at thi s step of the installation, and you are confident you have entered all t he information correctly here,

then it could be that you need to update the configuration of your l istener, or perhaps change the information you

provide on this screen to match what is already in the listener configuration.

You can use the command lsnrctl status to view information about the configuration of the listener. This wil l

tell you how many services it i s support ing. Those servi ces are database instances. You should see your

databaseinstance li sted in the output. The listener might also have deri ved a dif ferent hostname than you

expected. You might try localhost or look in the two configuration files menti oned above to find the name or I P

address the listener is using. You wil l need to supply the same information in the H ost name field on this page.

I f you do all of thi s, and sti ll cannot connect, you may need to update your li stener configuration. A quick Google

search on the two configuration fil es should tur n up instructions on how to do that. I f this sti ll does not solve your

problem, post a comment and I wil l wri te a post on that topic.




16/60

Once you get the database details correct, a small dialog box will open and the Repository Creation Ut il ity wil l run

a prerequisites check on your database. After this is completed, click on the OK button to continue.

Note: if you choose to use the Oracle Express Edit ion (XE) database, then you wil l get a warning message at this

point i nforming you that it i s not a supported database for production. You will have to click on Ignore to

continue. I t is perfectly reasonable to use XE as the database in your BPM development envi ronment, but you

should not use it in production.

On the next screen, we need to select which schemas we want t o create. Select all of the schemas in the two

groups called SOA and BPM infr astr uctur e and W ebCenter Suite as shown below. Then click on Next to

continue. Note that there is a prefix at the top of th is page. The default value is DEV . This allows you to use a

single database instance to hold schemas for more than one BPM domain. You would probably only want t o do

this in your BPM environment i f you have a large RAC database environment, or if your database is on an Oracle

Database Machine (Exadata), or i f all of the BPM envir onments are non-pr oduction.




17/60

A dialog box wil l appear as a furt her prerequisite check is completed. Once thi s is done, click on the OK button to

continue.

On the next page, we need to specify the password to use for the schemas. You can specify to use the same

password for al l of them, as we have done here, or specify individual passwords for each schema. Either way,

complete the necessary details and click on Next.




18/60

The next page gives is the opportuni ty to map schemas to tablespaces i f desired. For this example, we wil l just

accept t he defaults. I f you are sett ing up a production environment, you may want t o sit down with your Database

Administrator and do a more thorough mapping. Click on Next to continue.

Click OK in the confi rmation dialog that appears.

Now the Repository Creation Uti li ty wi ll create any tablespaces that do not alr eady exist. This step can take a few

minutes, depending on the speed of your storage. When it is done, click on OK to continue.

Finally, we are presented with a summary of the work to be done. Click on Create to go ahead and create all of

the schemas and load them wi th data.




19/60

You can watch the progress as this task runs. Note that thi s can also take some time if you have slower storage.

When it is complete, a summary wi ll be displayed. Click on Close to fini sh this part of the installation.




20/60

Install ing SOA Sui te 11.1.1.2

Now that our database contains all the necessary defin it ions and data, we are ready to move on to our other

product instal lations. Fir st we wil l install Oracle SOA Suite. You will need to download the 11.1.1.2 installer and

also the 11.1.1.3 patchset installer, which we wil l use a li tt le later on.

Unzip the 11.1.1.2 installer and invoke runInstaller from theDisk1 directory. I t may ask you to enter the

location of your JDK before the installer interview appears on screen. In our example thi s

was/usr/ java/ jdk1.6.0_ 21. Once the installer appears, click on Next to get started.

The installer wi ll run some prerequisite checks. Once these are completed, click on Next.

Now we need to specify the location where we want to install SOA Suite. Note that our M iddleware Home (which

we created earli er) is automaticall y selected for us. Cli ck on Next.




21/60

Now a summary is displayed. Click on Install to start the process.

Again, we can observe progress as the installer r uns.




22/60

Once it is finished, click on Next to continue.

Here we see a summary of what was done. Click on Finish to complete this phase of the installation.




23/60

Install ing the Web Tier

Next we will install the Web Tier. This is required by the Oracle Universal Content Management system (UCM)

which is used to store content i n the WebCenter environment. When we have our business processes running

later on, process part icipants are able to attach documents, comments, have discussions, tag, and collaborate in

other ways around an instance of a process. This content that they create is stored and managed in UCM.

The Web Tier contains a web server, load balancing and caching technologies, but for our purposes, we are just

going to install the web server component.

Again, you wil l need to download the Web Tier 11.1.1.2 installer and 11.1.1.3 patchset installer from edelivery or

OTN. Keep the patchset installer for l ater on. For now, unzip the 11.1.1.2 installer and invoke runInstallerfrom

the Disk1 dir ectory. Again, you may need to provide the JDK location. After a few moments, the installer wi ll

appear, as shown in the image below. Cli ck on Next to get started.

Select the option to I nstall and Configure the software and cli ck on Next.




24/60

Some prerequisite checks wil l r un. When they are complete, click on Next.

We need to specify the installat ion location. Put thi s into the same Middleware Home we have used for WebLogic

Server and SOA Suite. I t should be automatically selected. PressNext to continue.




25/60

On the Configure Components screen, uncheck everything except forOracle H TTP Serverand click on

Next. We are not going to use the Web Cache in our envi ronment and we do not want to associate our web serverwith a WebLogic domain. You might want to use these other options in a production environment, but they would

most l ikely be installed on a dif ferent machine anyway.

On the next screen we need to specify the location for our instance. Go ahead and accept t he defaults here and

click on Next to continue.




26/60

On the next page, we have the opportun ity to set the port numbers to use. The default port number for Web Tier

is 7777. We are going to accept the default in our example. Cli ck on Next to continue.

Again, you can provide your support details if you wish. Click on Next to continue.




27/60

A summary page will be displayed. Click on Install to start the installation.

You can watch the progress as the installer runs, and then the instance is created and started. This step may take

a while to complete as it wil l check that it can successfull y start and stop the instance.




28/60

When the installation i s finished and the configuration has completed, click on Next to continue.

A summary screen is displayed, showing what was done. Click on Finish to leave this part of the installation.




29/60

Installing WebCenter

The next step is to install Oracle WebCenter. This is the component that wil l provide all of the collaboration

services to our BPM envir onment. You wil l need to download both the WebCenter 11.1.1.2 installer and the

WebCenter 11.1.1.3 patchset i nstaller. Again, keep the patchset i nstaller for later on. You also need to download

and unzip t he Oracle Content Management for WebCenter 10.1.3.5.1 installer. Take a note of where you unzip

this.

Unzip t he 11.1.1.2 install er and invoke runInstaller from the Disk1 directory. You may need to specify the JDK

path again. After a few moments, the installer interview wil l appear. Click on Next to get start ed.

A prerequisites check will run. When it is complete, click on Next.




30/60

Again, we will install WebCenter in to the same Middleware Home. Click on Next.

Make sure you leave the option t o I nstall and Configure Oracle Un iversal Content M anagement

selected. Accept the default ports, 4444 and 4440, and enter the web server address as shown. Note that this is

the address of the Web Tier we just installed a few minutes ago, which should be running now, with / ucm on the

end. You should be able to hi t the web server in your browser and get the Oracle Fusion Middleware welcome

page. In thi s example, this would be at http:/ / bpm11g:7777/ . I f you cannot vi ew the homepage, then you need

to stop and go fix that before you continue here. When you are ready, click on Next.




31/60

On thi s screen, we need to provide the database details for UCM to use. The connect str ing is in the format

hostname:port :SI D . Substit ute in the values that you used earl ier when we ran the Repository CreationUtil ity. In our case it is bpm11g:1521:obpm . You also need to provide the schema username, note that thi s

matches the one we created wit h the RCU, note also it has the DEV_prefix that we pointed out earl ier, and

provide the password you set for the schema when we ran RCU. When all of these details are entered, pressNext .

The summary screen is displayed. Click on Install to start the process.




32/60

We can watch the progress as the installer runs.

When it is complete, cli ck on Next to continue.




33/60

Now we need to tell the installer where weunzipped the UCM installation media. Note that you want t o point at

theContentServerdirectory inside the directory where you unzipped the fi le, as shown below. You can click ontheBrowse button to locate this directory. Click on Next when you are ready to conti nue.

The installer wi ll install UCM and configure it for use with WebCenter. You can watch progress.




34/60

When thi s is complete, click on Finish to leave thi s part of the installation.

Install ing the Web Tier PatchSet

Our next step is to run t he patchset installers to upgrade our installation f rom 11.1.1.2 to 11.1.1.3. We start wi th the

Web Tier patchset installer, whi ch we downloaded and unzipped earl ier. Invoke runInstallerfrom theDisk1

directory. You may need to provide the JDK location. When the installer opens, as shown below, click on Next to

get started.




35/60

Point the installer to the location where you installed Web Tier earlier. This should be automatically found for

you. Cli ck on Next.

Provide your Oracle Support details if you wish, then click on Next .




36/60

The summary screen is displayed. Click on Install.

We can watch progress.




37/60

When it is complete, cli ck on Next.

And then click on Finish.




38/60

Install ing the WebCenter 11.1.1.3 PatchSet

Next we will patch WebCenter. Invoke the run I nstaller from theDisk1 directory from your unzipped

WebCenter 11.1.1.3 patchset. Provide the JDK details if necessary. When the installer opens, click on Next to get

started.

Point it to the location where you installed WebCenter. This should have been automatically found. Click on

Next.




39/60

Review the summary page and click on I nstall.

You can watch the progress.




40/60


Cli ck on Finish.




41/60

Install ing the SOA Suite 11.1.1.3 PatchSet

This is a large patch and it adds the BPMN support to SOA Suite, to effectively extend i t to include BPM Suite.

Again, we invoke runInstaller from the Disk1 directory of the SOA Suit e 11.1.1.3 patchset that we installed and

unzipped previously. Provide the JDK details if necessary. When the installer opens, click on Next .

Point the installer to the location where we installed SOA Suite. This should have been automaticall y populatedfor us. Click on Next .




42/60

Review the summary screen and click on Install .

We can observe progress.




43/60


Review the summary and cli ck on Finish.




44/60

Configure the Web Tier to support Oracle UCM

We need to make one small update to the configurati on of the Web Tier to support Oracle Uni versal Content

Management (UCM) which wi ll act as the content server for vari ous content created in our BPM environment.

To complete this configuration, you need to edit the httpd.conf(web server configuration) fil e for the Web Tier.

I t is located here:

/ u02/ Or acl e_WT1/ i ns t ances/ i nst ance1/ conf i g / OHS/ ohs1/ ht t pd. conf

The following line must be added to the end of this fil e:

i nc l ude " / u02/ Or acl e_WC1/ ucm/ dat a/ us er s/ apac he22/ apac he. con f "

This change directs the web server to load up the configuration from UCM. You wil l need to restart the web tier

after making this change. This can be done with t he following commands:

cd / u02/ Or acl e_WT1/ i nst ances / i nst anc e1/ bi n

. / opmnct l shut down

. / opmnct l st ar t al l

Providing there were no errors, the web server should now start up and be accessible at

http:/ / yourserver:7777/ . You should also beable to access UCM at http:/ / yourserver:7777/ ucm. Note

that thi s URL is formed using the information we provided during the WebCenter installation interview. Your

screen should look l ike this:




45/60

Configuring a Domain

Now that we have fin ished installi ng all of the software, we are ready to create our WebLogic Domain. The

domain is essenti ally all of the configuration information needed to actually run the software. We can create as

many domains as we li ke, with different combinations of software in them. In our example, we wil l just create

one. In a real wor ld i nstallation, you would most li kely have separate domains for production, disaster recovery,

training, test, etc.

To create the domain, we use the Fusion M iddleware Configuration Wizard . Invoke config.sh in

your/ u02/ Oracle_SOA1/ common/ bin directory. When the configuration wizard opens, select Create a

new W ebLogic domain and click on Next.

On the Select D omain Source page, we need to select which components we want confi gured in the domain.

Select the components shown in the image below. Pay special attention to the part in br ackets at the end of the

name. There are some components that have very simi lar names. When you have made your selections, press

Next.




46/60

On the next page, we need to specify the name of the domain and the location where it s fi les wil l be stored. You

can go ahead and accept the default s and press Next to continue.

On the next page, we need to provide a password for t he domain administrator (weblogic user). Enter a

password and cli ck on Next.

Next, we specify whether we want the server to run i n Development M ode orProduction M ode, and which

JDK to use. For now, accept the default s and click on Next. We can change this later on, when we are ready.




47/60

Now we need to provide the database connection details. Select all of the Component Schemas listed in the

table by checking the boxes next to each one, then type in the appropr iate values in the fields at the top. The

DBM S/Service field is our SID, we used obpm . The hostname is bpm11g in our case, port 1521. I f you

specified the same password for all schemas when we ran RCU, then you can just t ype that password in here. I f

not, you wi ll need to select each schema one by one and enter i ts password. When you are done, cli ck on Next.

The configuration wizard wi ll check that all of the schemas are accessible. I f there are any errors, you will need to

go back and correct them. When everyt hing is successful , click on Next to go on.

We do not need to do any optional configuration, so just click on Next.




48/60

The summary page is displayed. Click on Create.

We can watch progress.

When it is complete, cli ck on Finish.




49/60

Note that the configuration wizard gives you the Admin Server URL. Take a note of that.

Starting the environment the first time

Now we are ready to start up the environment for the fir st time. We wil l start everything from the command line

so we have easy access to the consoles, and so we can easily star t and stop the servers, as we will need to do this a

few times as we complete the configurati on.

First, we start t he Administrati on Server.

cd / u02/ user_projects/ domains/ base_domain/ bin

./ startWebLogic.sh

The server wil l start up and produce a number of messages. This may take a few minutes the fi rst t ime.

Eventually, a message wil l be displayed informing you that the server is in the RUNNI NG state. Once you see thi s

message, open a browser and point it to:

ht t p: / / your ser ver : 7001/ consol e

The WebLogic Server console wil l be displayed. You can log on using the userweblogic and the password you

specified dur ing the domain creation wizard previously.

You may also like to point your browser at the Enterpr ise Manager URL:

ht t p: / / y our ser ver : 7001/ em




50/60

You can log on using the same details.

When you log in, you will see the Farm status page, which wil l look something like the one below. You may not

have the same servers running as shown in the image, and the menus on the left may be slight ly di fferent for now.

When you start the addi tional servers, your screen should resemble the image quit e closely.

To start the other servers, called the Managed Servers, run the following commands, each one in a separate

shell/ window (you wil l need to set the directory in each shell before executing the other command):

cd / u02/ user _pr oj ect s/ domai ns / base_domai n/ bi n

. / st ar t ManagedWebLogi c. s h soa_ser ver 1

. / st ar t ManagedWebLogi c . sh WLS_Ser vi ces

. / st ar t ManagedWebLogi c. s h WLS_Por t l et

. / st ar t ManagedWebLogi c . sh WLS_Spaces

The first time you start up these managed servers they will t ake a bit longer than usual and you will get some

err ors as we have not configured securit y yet. They wil l each ask you for a user and password (in their

shell/ window) when you start them. You wil l need to enterweblogic and your password. I t is a useful exercise

to start them up and validate they all start successful ly. You wil l know they have started when they each issue the

message about being in RUNNING state.

I f you want t o stop one of these managed servers, you just type a Control-C in it s shell/ window. I t wi ll perform an

orderly shutdown. You must stop all managed servers completely before you shutdown the admin server, and

you must start the admin server completely before you start the managed servers.

Sett ing up boot.propert ies




51/60

We can create a special fi le called boot.properties to provide the user and password to WebLogic so that we

dont have to manually enter them when we start up the servers. This fil e should contain t he following data:

user name=webl ogi c

passwor d=what ev er

Change the password from whateverto the one you chose during domain creation.

Save a copy of this file in each managed servers securi ty directory, i.e.:

/ u02 / user_pr oj ect s / domai ns/ base_domai n /ser ver s / soa_server1 / secur i t y

/ u02/ user_pr oj ect s / domai ns/ base_domai n/ server s/ bam_ser ver1/ secur i t y

/ u02/ user_pr oj ect s / domai ns/ base_domai n/ server s/ WLS_Serv i ces/ secur i t y

/ u02 / user_pr oj ect s / domai ns/ base_domai n /ser ver s / WLS_Por t l e t / secur i t y

/ u02/ user_pr oj ect s / domai ns/ base_domai n/ server s/ WLS_Spaces/ secur i t y

The file must be called boot.properties in each case.

Next t ime you start a managed server, it wil l read the details from this fil e and it wi ll not ask you to enter them. I t

wil l also encrypt the contents of this file. You can veri fy thi s by taking a look at the file after you have restarted the

managed server.

Using the Node Manager

At this point, you may wish to configure the Node Manager so that you can also start and stop servers from the

WebLogic Server console or Enterpr ise Manager. I f you wish to do so, then take a look at this post for the

instructions to enable the Node Manager. Once you havedone that, you can then start just the admin server and

then the node manager from the shell window/ command line. The managed servers can then be managed from

the consoles. To start t he Node Manager, you would use these commands:

c d / u02/ wl s er v er _10. 3/ s er v er / bi n

st ar t NodeManager . sh

Configuring WebCenter

Now we need to configure WebCenter for use wit h the Process Portal. This part gives us access to the new social

BPM features provided in the Oracle BPM 11g product release.

The first step is to register the connection to the content server. Login to the Enterpr ise Manager at

http:/ / yourserver:7001/em using the userweblogic and your password.

In the main navigation tree on the left hand side of the page, navigate to Farm -> WebCenter -> WebCenter

Spaces -> w ebcenter




52/60


53/60

Alternatively, you can see the same in your r ecent documents view in the personal side bar on the left hand side of the screen. The

image below shows the two places where you can validate this.

Next, we want t o set up the discussions server. We will need to configure WS-Securi ty to do this, so we need to create our security

keys first.

Create a dir ectory to hold our keystore:

mkdi r / u02 /keyst o res

In this directory, createa new keystore and a RSA key pair. Note that thi s whole command is entered on one line. I t

is shown here on mult iple lines for ease of reading only. You may need to put t he path to your JDKs bin di rectory

before the keytool command if t hat directory is not in your PATH. You need to add in the appropr iate Common

Name (CN) asshown in bold. Here we have used the full y qualif ied hostname of the WebCenter server, with the

hostname as a cn and each domain name component as a dc. You also need to provide a password for t he key

(keypass) and for the keystore (storepass), as shown.

keyt ool

- genkeypai r

- keyal g RSA

- dname " cn=your ser ver , dc=au, dc=or acl e, dc=com"

- al i as or ak ey

- keypass wel come1

- keys t or e webcent er . j ks

- st or epass wel come1

- v al i di t y 1064

Now we need to create the cert if icates. In this example, we are going to use self signed certi ficates. This issuitable for t est or development systems, but in a production system you may wish to purchase certi ficates from a

trusted external Cert ifi cate Authori ty. Alternatively, you may havealready purchased a signing cert ifi cate and

have your own cert if icate authorit y. In th is case, you will need to get your cert ifi cates signed by the administrator

of the cert if icate authorit y.

The following command is used to create a new certi ficate which we wil l call orakey.




54/60

keyt ool

- ex por t c er t

- v

- al i as or ak ey



- r f c

- f i l e or ak ey . c er

Cer t i f i c at e s t o r e d i n f i l e

Now we import that cert ifi cate into the WebCenter keystore with a new name, webcenter_spaces_ws.

keyt ool

- i mp or t c er t

- al i as webcent er _spaces_ws




Cer t i f i c at e al r eady ex i s t s i n key st or e under al i as

Do y ou s t i l l want t o add i t ? [ no] : y es

Cer t i f i cat e was added t o keys t o re

Now we are ready to copy our keystore, which contains our cert ifi cate, into our domain configuration di rectory,

using a command like this: (again, thi s command should be entered on one line)

cp webcent er. j ks

/ u02/ user_pr oj ect s / domai ns/ boot _domai n/ conf i g/ f mwconf i g/

Next, we will configure our domain to use thi s keystore. In Enterpr ise Manager, navigate

to Farm_boot_domain -> Weblogic Domain -> boot_domain

From the context menu, select Secur it y -> Securi ty Provider Configuration

Scroll down to Keystore, expand it , and click Configure. Deselect (uncheck) the box Configure Keystore M anagement and

click Ok . This wil l make sure that we reset the configuration and remove any old values. Obvisously, since we just installed the

software and created our domain a few moments ago, there wont be any old values, but i f you have to come back and do th is again for

any reason, then you wil l want to fol low th is two step process.




55/60

Now go back to Keystore, and cli ck Configure again, this time check the box Configure Keystor e M anagement and enter the

following information:

Keystore Path = . / webc ent er . j k s

Password = wel come1

Confirm Pwd = wel come1

Signature Key Al ias = or akey

Signature Password = wel come1


Encryption Key Crypt Alias = or akey

Crypt Password = wel come1


Saveyour changes and then stop all managed servers, and then the admin server, then restart t he admin server and then the

managed servers.

Now we need to create a keystore for the discussions servi ce to use. This is done by issuing the following

command, this is done in the same dir ectory as the commands we use previously to create the keystore for

WebCenter, i.e. / u02/ keystores.

keyt ool- i mp or t c er t

- al i as d f _ or ak ey _publ i c


- keys t or e owc_d i scuss i ons . j ks


Owner : CN=your ser ver , DC=au, DC=or acl e, DC=com

I ssuer : CN=your ser ver , DC=au, DC=or acl e, DC=com

Ser i al number : 4b69f 328

Val i d f r om: Wed Feb 03 17: 05: 28 EST 2010 unt i l : Wed Jan 02 17: 05: 28 EST 2013

Cer t i f i c at e f i nger p r i nt s :

MD5: 3C: 7A: D7: 33: 1A: 21: 9F: BA: 24: A2: D1: 9E: 09: F6: FC: 93

SHA1: 59: B6: 3F: 78: 8D: 5B: 28: E4: E8: 8C: 7E: B1: 9A: 22: A9: 20: F6: 39: F1: 20

Si gnat ur e al gor i t hm name: SHA1wi t hRSA

Vers i on: 3

Tr u st t hi s c er t i f i cat e? [ no] : y es

Cer t i f i cat e was added t o keys t o re

In this same dir ectory, create a file named keystore.properties . This file must contain the following text. It is

very important that t his fi le does not contain any extr a spaces at the ends of the li nes, or any extr a lines. Please

check careful ly to make sure you have not added any extr a spaces. Note that the last l ine contains the name of the

keystore we just created in the last step.




56/60

or g. apache. ws. sec ur i t y. c r ypt o. pr ovi der =or g. apache. ws. sec ur i t y. c omponent s . cr ypt o. Mer l i n

or g. apache. ws. s ecur i t y . cr ypt o. mer l i n . key st or e. t ype=j ks

or g. apache. ws. sec ur i t y. c r ypt o. mer l i n. k eys t or e. pass wor d=wel c ome1

or g. apache. ws. s ecur i t y . cr ypt o. mer l i n . key st or e. al i as=df _or akey_publ i c

or g. apache. ws. sec ur i t y. cr ypt o. mer l i n. f i l e=/ u02/ keyst or es/ owc_di s cuss i ons . j ks

We need to update our domain configuration so that this fil e can be found on the servers CLASSPATH. This isdone by updating the file that sets up the environment for t he servers. This file is:

/ u02/ us er _pr oj ec t s/ domai ns/ boot _domai n / bi n / set Domai nEnv. s h

You need to add the following li nes to the end of this file:

i f [ " ${ CLASSPATH} " ! = " " ] ; t hen

CLASSPATH=" ${ CLASSPATH} ${ CLASSPATHSEP} / u02/ keyst or es/ "

ex por t CLASSPATH

el seCLASSPATH=" / u02 / keyst or es / "

ex por t CLASSPATH

f i

Note that the path to the directory containing the keystore.properties fi le is added to the CLASSPATH by this

fi le. You should now restart all your servers to pick up this change.

We need to tell the discussions server about the keystore now. This is done by logging in to the Discussion Server

Admin tool at ht t p: / / y our ser ver : 8890/ owc_di sc uss i ons / admi n usi ng t he weblogic user.

Go to System Proper ties

Modify the value ofwebser vi ces. soap. cust om. cr ypt o. f i l eName so that it points to the propert ies fil e you just created:

webser vi ces . soap. cust om. cr ypt o. f i l eName = key st or e. pr oper t i es

Note that you dont need to specify full path, as you made the change to the CLASSPATH. Click SavePropert y

Finally, we can register the Discussion Server with WebCenter. Like before, thi s is done in the Enterprise

Manager.

Navigate to Far m -> WebCenter -> WebCenter Spaces -> w ebcenter

From the context menu, select Settings -> Service Configur ation

Click on Discussions and Announcements -> Add

Complete the fields as shown below:




57/60

Connection name = di scuss i on_ser ver

Active Connection = check

Server URL = ht t p: / / your ser ver : 8890/ owc_di sc ussi ons

Administrator User Name = webl ogi c

Connecti on Secured = check

Then expand Additional Propertiesand click Addto add the following propert ies:

keystore.location = / u02/ user_ projects/domains/boot_domain/ config/ fmwconfig/webcenter.jks

keystore.type = jks

keystore.password = welcome1- To encrypt the password, check "I s Propert y Secured"

encrypti on.key.alias = orakey

encrypti on.key.password = welcome1- To encrypt t he password, check "I s Propert y Secured"

group.mapping = forum - that is the default value

Saveyour work and restart your servers again to activate these changes.

At thi s point, you may feel like you are restart ing your servers an awful lot . Str ictl y speaking, all these restarts are not necessary

you could make all the changes in the one go, and then just do one restart. But, if you get anything wrong, it wil l be pretty hard to

find your mi stake. This way, step by step, it i s easy to identif y where you have gone wrong if anything does not work .

I f you now log on to WebCenter Spaces (li ke before) you should be able to see your (empty) discussion forums using the discussions

icon in the personal sidebar. I t is the one right underneath the documents icon we saw earli er.

Last, but not least, lets set up the Wiki server. Again, this is a two step process. Fir st, in Enterprise Manager, we will generate

a passcode which will be used by the Wiki server for authenti cation.

Navigate to Farm_boot_domain -> Weblogic Domain -> boot_domain

In the context menu, select Securi ty -> Credentials

Click CreateMapto create a new credenti al map

Name the map owc_wi ki

Highlight/ select the owc_wi ki map that you just created, click Create Keyand complete the f ields as shown:

Select Map = owc_wi kiKey = wsPasscode

Type = Passwor d

User Name = webl ogi c - does not really matter

Password = wel come1

Click on OK to save this.




58/60

Now we can register the Wik i server to WebCenter. Sti ll in Enterprise Manager, navigate to Far m -> WebCenter -> WebCenter

Spaces -> webcenter

From the context menu, select Settings -> Service Configur ation

Click on Wiki and Blog Server -> Addand complete the fields as shown:

Connection name = wi ki _ser ver

Active Connection = check

Server URL = ht t p: / / y our ser ver : 8890

Passcode = wel come1 - the one we defined above

Now save your changes and restart all of your servers. You should now be able to login to WebCenter Spaces and get the option t o

add Wiki and Blog pages when you click on Page Actions and Create Page as seen in the image below. Note that these page types

would not have been available previously.

That completes all of the necessary configuarti on of WebCenter for use wit h BPM. Now we can move on to thefinal phase of the installation, setting up the Process Portal feature.

Configuring the Process Portal

The final step is to run the script that wi ll configure the Process Portal, but fir st we need to set up the

configuration fi le. All the fil es you need are included in the installation in the following directory:

/ u02/ Or acl e_SOA/ bpm/ pr ocess por t al . z i p

You need to unzip thi s fil e, then edit the process-portal-install.properties fil e located in the unzipped

location.

Here is an example of the fil e contents:

################################################

# BPM Process Portal installati on properties #

################################################

#Flag to decide whether to extend existing BPM domain or create a new one.




59/60

extendSoa=true

#Flag to decide whether to prompt for passwords or read them from th is fil e

promptForPasswords=false

#BPM Schema details

bpmDBUser=DEV_SOAINFRA

bpmDBPassword=welcome1

bpmDBType=ORACLE

bpmDBDriver=oracle.jdbc.OracleDriver

bpmDBUrl=jdbc:oracle:thin:@${oracle_db_host_name}:$ {oracle_db_port }:$ {db_sid}#BPM MDS details

bpmMDSUser=DEV_MDS

bpmMDSPassword=welcome1

#BPM Runtime details

bpmHost=yourserver

#M anaged server port if BPM is installed on managed server. Else admin port

bpmRuntimePort=8001

bpmAdminUser=weblogic

bpmAdminPassword=welcome1

#webcenter spaces installation details

wcOracleHome=/ u02/ Oracle_WC1

#I f extendSoa flag is set t o true, then configure the below two properties to point to BPM domain

wcDomainName=base_domain#Flag to control whether to set domain realm password or not

wcSetDomainRealmPassword=true

#This is the password to setup trusted domains. Same password should be set on BPM domain as well

wcDomainRealmPassword=welcome1

wc.server.port=8888

#Webcenter's weblogic installati on details

wcHost=yourserver

wcAdminPort= 7001

wcAdminUser=weblogic

wcAdminPwd=welcome1

wcManagedServerName=WLS_Spaces

#Flag to control whether t o configure servi ces

wcConfigServices=false

#content server details

wcContentServerName=yourserver

wcContentServerPort= 4444

wcContentSpacesRoot= / Spaces

wcContentAdminUser=sysadmin

#discussion server details

wcDiscussionServerUrl= http:/ / yourserver:8890/ owc_discussions

wcDiscussionAdminUser=orcladmin

You wil l need to go carefull y through this fil e and check every value against your environment. Now is a really

good time to take a backup so that you can easily retry this step if you got anything wrong.

Once you are ready, you need to make sure you have ANT on your path. I f you dont have it installed

independently, you can use the one provided in your Oracle Middleware home,

at / u0 2/ modules/ org.apache.ant_1.7.1

Then run ant -f install.xml in the dir ectory where you unzipped yourprocessportal.zip, i.e. the same

directory where you just edited that propert ies fil e to match your environment.




60/60

Share thi s: Share

About M ark NelsonMark Nelson is a Consulting Soluti on Architect in t he Fusion M iddleware Architects Team (known as The A-Team) in Oracle

Development. Their m ission i s to supply deep technical expertise to support customers deploying Oracle Fusion Mi ddleware,

and to collect r eal worl d feedback to continuously improve the product set. Before joini ng Oracle Development i n 2010, Mark

k d i S l C lt i t O l i 2006 d i l t IBM i 1994 i l di l i S ft G d

This will probably run for a while maybe ten minutes and if you got all your parameters correct, you will be

rewarded wi th a BUILD SUCCESSFUL at the end.

Congratulations! You have successful ly installed a ful l, complete, end to end Oracle BPM system, including the

Process Port al and all social BPM features. Give yourself a pat on t he back!

Now that you have got one, what do you do with it ?

A good place to start is to hi t the following URLs and start taking a look around. In future posts we wil l di scuss

how to use this environment you now have at your disposal.

WebLogic Console

ht t p: / / your ser ver : 7001/ consol e

Enterprise Manager

ht t p: / / y our ser ver : 7001/ em

BPM Worklist Appli cation

ht t p: / / y our ser ve r : 8001/ bpm/ wor kspace

WebCenter Spaces (and Process Portal)

ht t p: / / your ser ver : 8888/ webcent er

Process Composer

ht t p: / / y our ser ve r : 8001/ bpm/ composer

Business Activity Monitoring

ht t p: / / y our ser ve r : 9001/ Or acl eBAM

p.s. This post took us a long time to wri te gett ing all the information together and typed up to present (we hope)

nicely. I f it helped you out, or i f you found anything was missing, please leave us a comment to let us know.

Everything BPMN 2.0

New in BPMN 2.0, BPMN 2.0 Examples FreeBPMN 2.0 modeler for Visiowww.BusinessProcessIncubator.com

Morzine Properties

Chalets and apartm ents for sale Morzine and

valley Portes du Solielwww.geranium74.com

Cyprus Property for Sale

Luxurious property for sale Aphrodite Hills

Resort, Paphoswww.aphroditehills.com/realestate

BPA Workflow Suite

Looking for a workflow software? Lebanon &

Middle EastTechDriveME.com


end-to-end installation of fmw11g

Documents