Installing and Configuring Oracle WebCenter Spaces

Purpose

This tutorial covers installing and configuring Oracle WebCenter Spaces along with the bundled Oracle WebCenter Services and the optional Oracle Universal Content Management (UCM) in a Linux environment.

Overview

WebCenter Spaces is an online environment that brings together an array of social networking, collaboration, and personal productivity tools. WebCenter Services is a complete set of complementary services that enables you to embed Web 2.0-style communication and collaboration services directly into WebCenter Spaces. The component applications for both WebCenter Spaces and WebCenter Services run on Oracle WebLogic Server and store their metadata in an Oracle database. UCM is an enterprise level content management platform.

Scenario

You are an Administrator who needs to install WebCenter Spaces in a Linux environment. You will run the Repository Creation Utility (RCU) to create the required schemas in the database. Then you will create the necessary files in the file system by running the WebCenter Installer. You will install WebCenter Spaces, WebCenter Services, as well as the optional UCM. Next you will run the Oracle Fusion Middleware Configuration Wizard to create the WebCenter domain. WebCenter Spaces and WebCenter services are deployed to servers in this domain. In this scenario, you create a single node WebCenter domain and everything is installed on one machine. This would not be typical for a production installation but can work well for a development or test environment. In this scenario you are setting up for a development environment but apart from the single node domain and the startup mode of the WebLogic Server, the steps are essentially the same as for a production environment.

Note: The screenshots will not reflect the specific environment you are using. Also product installer directories, installation directories, and the location of Middleware_Home may be different from the locations on your system.

Software and Hardware Requirements

The following is a list of software requirements:

• Oracle Database 10g or 11g must be installed
• Oracle WebLogic Server 11g must be installed
• An HTTP server must be installed (required for UCM)
• Your system environment must meet the general installation requirements for Oracle Fusion Middleware, Oracle WebCenter, and RCU

Prerequisites

Before starting this tutorial, you should:

1.	Have access to the WebCenter installer
2.	Have access to the UCM installer
3.	Have access to the Repository Creation Utility (RCU)
4.	Start your Oracle database
5.	Know the location of your Java Runtime Environment (JRE)
6.	Know the location of your Middleware_Home directory (the directory that contains your WebLogic_Server_Homedirectory)
7.	Know the address and port number of your HTTP Server
8.	Have some familiarity with basic product installs

Creating WebCenter Schemas

To create the WebCenter database schemas using RCU, perform the following steps:

1.	Navigate to the RCU bin directory and start RCU: $ cd /u01/app/rcu/bin $ ./rcu
2.	In the Welcome window, click Next.
3.	In the Create Repository window, accept the default of Create and click Next.
4.	In the Database Connection Details window, enter the following values and click Next. Field Value Host Name <your_host_name> Port 1521 Service Name owcdb01 Username sys Password welcome1 Role SYSDBA A dialog box opens confirming the database prerequisites have been checked successfully. Click OK.
5.	In the Select Components window, accept the default of Create a new Prefix with the value of DEV (this is the default prefix, you can give it any value.) Select the WebCenter Suite component and click Next. Note: When you select WebCenter Suite, Metadata Services under AS Common Schemas will also be selected. A dialog box opens confirming the database component prerequisites have been checked successfully. Click OK.
6.	In the Schema Passwords window, accept the default of Use same passwords for all schemas and enter the password welcome1 twice. Click Next.
7.	In the Map Tablespaces window, click Next. A dialog box may open requesting confirmation to create the tablespaces. Click OK. Then a dialog box opens confirming the tablespaces have been created successfully. Click OK.
8.	In the Summary window, click Create. A dialog box opens showing the progress of schema creation.
9.	In the Completion Summary window, click Close.

Installing WebCenter Spaces

The WebCenter installer installs the files for WebCenter Spaces, WebCenter Services, and UCM. To install WebCenter Spaces, WebCenter Services, and UCM, perform the following steps:

1.	Navigate to the staged location for the WebCenter installer and start the installer: $ cd /stage $ ./runInstaller -jreLoc /u01/app/oracle/product/fmwhome/jdk160_14_R27.6.5-32The installer requires the location of a JRE. When you installed Oracle WebLogic Server, a JRE was installed on your system. You can use this location to start the installer. You must supply an absolute path. The JRE location in this path is the Sun JRE. The Sun JRE is recommended when you are installing in a development environment. If you are installing in a production environment, use the JRockit JRE.
2.	In the Welcome window, click Next.
3.	The installer runs various tests to check system prerequisites. When it is done, click Next in the Prerequisite Checks window.
4.	In the Specify Installation Location window, enter the location of Middleware_Home, in this scenario,/u01/app/oracle/product/fmwhome/. Accept the default Oracle Home Directory and click Next.
5.	In the Specify UCM Configuration Options window, select Install and Configure Oracle Universal Content Management. Accept the defaults for Content Server Port and Content Server Admin Port and for Web Server HTTP Address the format should be http://<your_host_name>:<port_number>/<webroot>. In this scenario, it ishttp://edvmr1p0.us.oracle.com:7777/idc. Click Next.
6.	In the Specify UCM Database Details window, enter the following values and click Next. Note: These values must match the values used when you ran RCU in the previous section. Field Value Connect String <your_host_name>:<port_number>:owcdb01 Schema User Name DEV_OCSERVER Schema Password welcome1
7.	In the Installation Summary window, click Install. Installation Progress is shown. When it is complete, click Next.
8.	In the Specify UCM Installer Directory window, enter the location of the UCM installation files,/stage/ContentServer. Click Next. UCM Installation Progress is shown .
9.	In the Installation Complete window, click Finish.

Configuring WebCenter Spaces

The Oracle Fusion Middleware Configuration Wizard creates and configures a new WebLogic domain for Oracle WebCenter Spaces and components. To configure WebCenter Spaces and components, perform the following steps:

1.	Navigate to the WebCenter_Oracle_Home/common/bin directory and start the Configuration Wizard: $ cd /u01/app/oracle/product/fmwhome/Oracle_WC1/common/bin $ ./config.sh
2.	In the Welcome window, accept the default of Create a new WebLogic domain and click Next.
3.	In the Select Domain Source window, accept the default of Generate a domain configured automatically to support the following products and select the following products then click Next: Oracle WSM Policy Manager (oracle_common) Oracle WebCenter Spaces Oracle Portlet Producers Oracle Wiki and Blog Server Oracle WebCenter Discussion Server Oracle Identity Management Oracle Enterprise Manager Oracle JRF Note: You need to select Oracle WSM Policy Manager before you select Oracle WebCenter Spaces else you will receive an error. Also Oracle Enterprise Manager and Oracle JRF are selected automatically when you select Oracle WebCenter Spaces.
4.	In the Specify Domain Name and Location window, enter the following values and click Next. Field Value Domain name practice_domain Domain location /u01/app/oracle/product/fmwhome/user_projects/domains Application location /u01/app/oracle/product/fmwhome/user_projects/applications
5.	In the Configure Administrator User Name and Password window, accept the default User name of weblogic and enter welcome1 twice for the password. Click Next.
6.	In the Configure Server Start Mode and JDK window, accept the defaults of Development Mode and Sun SDK 1.6.0_14 and click Next.
7.	In the Configure JDBC Component Schema window, select all the component schemas in the lower portion of the window. Enter the following values in the upper portion of the window and click Next. Field Value DBMS/Service owcdb01 Driver default value Host Name <your_host_name> Schema Owner default value Port default value Schema Password welcome1 The Testing Connections dialog opens.
8.	In the Test Component Schema window, click Next.
9.	In the Select Optional Configuration window, select Administration Server and Managed Servers, Clusters and Machines. Click Next.
10.	In the Configure the Administration Server window, accept all the defaults and click Next.
11.	In the Configure Managed Servers window, accept all the defaults and click Next.
12.	In the Configure Clusters window, click Next.
13.	In the Configure Machines window, click Add. Enter the following values and click Next. Field Value Name practice_machine Node manager listen address All Local Addresses Node manager listen port default value
14.	In the Assign Servers to Machines window, select all the servers in the left pane and click the right arrow icon. Click Next.
15.	In the Configuration Summary window, click Create. This may take a few minutes to complete.
16.	In the Creating Domain window, click Done.

Starting the WebLogic Servers

To start all the WebLogic Servers as well as the Node Manager, perform the following steps:

Starting the Administration Server

1.	Navigate to the domain directory and start the Administration server: $ cd /u01/app/oracle/product/fmwhome/user_projects/domains/practice_domain $ ./startWebLogic.shWait until you see the message <Server started in RUNNING mode>. Do not close this window as it will shut down the Administration server.

Starting the Node Manager

1.

In a new window, navigate to the Oracle_Common_Home/common/bin directory and set the Node Manager properties: $ cd /u01/app/oracle/product/fmwhome/oracle_common/common/bin $ ./setNMProps.shYou see the message Appending required nodemanager .properties. Note: If you are installing and older 11g version of WebCenter Spaces that does not include Patch Set 1 then the Node Manager file is located in WebCenter_Oracle_Home/common/bin.

2.

Navigate to the WebLogic_Server_Home/server/bin directory and start the Node Manager: $ cd /u01/app/oracle/product/fmwhome/wlserver_10.3/server/bin $ ./startNodeManager.shWait until y ou see the message INFO: Secure socket listener started on port 5,556. Do not close this window as it will shut down the Node Manager.

Starting the Managed Servers

1.	Start the WebLogic Server Administration Console by opening a web browser and enteringhttp://<your_host_name>:7001/console. For Username enter weblogic, for Password enter welcome1then click Log In. Note: You can also start the managed servers from the commandline usingDOMAIN_DIR/bin/startManagedWebLogic.sh. Before you see the login window a message briefly appears indicating the application is being deployed for the console.
2.	In the left Domain Structure pane, expand Environment and click Servers.
3.	In the Summary of Servers window, click the Control tab and select the three managed servers. Then click theStart button.
4.	Refresh the window by clicking the Refresh icon in the browser or pressing F5 until the State for all servers isRUNNING.

Verifying the Installation

To verify that WebCenter Spaces has been installed correctly, perform the following steps:

1.

Start WebCenter Spaces by opening a web browser and entering http://<your_hostname>:8888/webcenter. For User Name enter weblogic, for Password enter welcome1 then click Login.

2.

You are now logged into WebCenter Spaces. This confirms that it has been installed correctly. Note: The messages on the right of the window regarding the Worklist and Documents services being unavailable are because they are not configured yet. At this point WebCenter Spaces is installed and up and running but your work is not complete. You still need to configure the services you wish to use in WebCenter Spaces, for example, the Documents service (including UCM), the Worklist service, and the Discussions service. You may also wish to register portlet producers. See the Oracle Fusion Middleware Installation Guide for Oracle WebCenter 11g and theOracle Fusion Middleware Administrator's Guide for Oracle WebCenter for more information.

How Recover WebSphere Admin console Password

Recover WAS admin console password

There are two ways to deal with password at WAS admin console

1. Disable the security for WAS and login as anonymous. Go to security settings, if it is local security are free to modify the password, but if it is LDAP user then find the user and check with LDAP team for respective user.

Now in Production environment this becomes next to impossible to disable security, we can find the password by using step 2.

2. Login on server ( either application server or deployment server).

• Go to directory profiles/profie_name/config/cells .
• Open file security.xml.
• Look for tag userRegistry
• Find the encrypted password for respective user
• Enter the encrypted value to URL : http://www.sysman.nl/wasdecoder/

This will descript the password for WAS admin console.

IBM WebSphere Application Server How To

How to decode WAS password

Run the following command on the server where WAS is installed. Search for the ws_runtime.jar on your system to get the correct path for your version of WAS.

java -classpath <WASHOME>/deploytool/itp/plugins/com.ibm.websphere.v61_6.1.200/ws_runtime.jar com.ibm.ws.security.util.PasswordDecoder "<password starting with {xor}>"

For WAS 7 and BPM you might also need other libs in your CLASSPATH:

WAS_ROOT=/software/ems/bpm/WebSphere/AppServer
WAS_JARS_DIR=$WAS_ROOT/deploytool/itp/plugins/com.ibm.websphere.v7_7.0.1.v20101015_1536/wasJars
SEC_JARS=securityimpl.jar:wssec.jar:crypto.jar:bootstrap.jar:ras.jar:wsexception.jar:com.ibm.ws.emf.jar:org.eclipse.emf.ecore.jar:org.eclipse.emf.common.jar
cd $WAS_JARS_DIR
$WAS_ROOT/java/bin/java -cp $SEC_JARS com.ibm.ws.security.util.PasswordDecoder "{xor}LDo8LTor"

For encoding the password you can run the following

$WAS_ROOT/java/bin/java -cp $SEC_JARS com.ibm.ws.security.util.PasswordEncoder secret

How to enable WAS performance monitoring

Enable PMI in the administrative console.

1. In the administrative console, click Monitoring and Tuning > Performance Monitoring Infrastructure > server_name.
2. Verify that Enable Performance Monitoring Infrastructure (PMI) is selected. This setting is enabled by default. If the setting is not enabled, select the check box, pick the amount of the stats you want to pull (basic,extended and all) then restart the server.

You could also do it with the JACL wsadmin script:

 set s1 [$AdminConfig getid /Cell:CELL_NAME/Node:NODE_NAME/Server:APPLICATION_SERVER_NAME/]
 set pmi [$AdminConfig list PMIService $s1]
 $AdminConfig show $pmi.
 $AdminConfig modify $pmi {{enable true}}
 $AdminConfig save

If you need to enable PMI, restart the server.

Now you can use a script like this to list all active MBeans that have a stats component

perfOName = AdminControl.makeObjectName(AdminControl.completeObjectName('type=Perf,*'))
for a in AdminControl.queryNames('*').split('\n'): #type=ConnectionPool,
        try:
                config=AdminControl.invoke_jmx(perfOName, 'getConfig', [AdminControl.makeObjectName(a)], ['javax.management.ObjectName']) #com.ibm.websphere.pmi.PmiModuleConfig
                if config is not None:
                        print a
        except:
                pass

How to trigger a heap dump in a running WebSphere instance

Start wsadmin on the instance. Run

set jvmname [$AdminControl queryNames WebSphere:type=JVM,process=server1,node=SERVERNode01,*]

Use the proper node name. You should get a reply, something like this:

 WebSphere:name=JVM,process=server1,platform=proxy,node=SERVERNode01,j2eeType=JVM,J2EEServer=server1,version=7.0.0.13,type=JVM,mbeanIdentifier=JVM,cell=SERVERNode01Cell,spec=1.0

To dump threads run

$AdminControl invoke $jvmname dumpThreads

This will create a javacore.YYYMMDD.HHMMSS.mmmm.nnnnn.txt file in the profiles\AppSrv01 (root) folder. To dump the heap (memory) run

 $AdminControl invoke $jvmname generateHeapDump

It should generate a heapdump.YYYMMDD.HHMMSS.mmmm.nnnnn.phd file and report it's location back to you. It should be in the root folder as well.

How to configure permanent mapping of users/groups to roles in a webapp

In the EAR container create ibm-application-bnd.xmi with the similar contents:

<?xml version="1.0" encoding="UTF-8"?>
<applicationbnd:ApplicationBinding xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:applicationbnd="applicationbnd.xmi" xmlns:common="common.xmi" xmlns:application="application.xmi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmi:id="Application_ID_Bnd">
  <appName xsi:nil="true"/>
  <authorizationTable xmi:id="AuthorizationTable_1">
    <authorizations xmi:id="RoleAssignment_1">
      <specialSubjects xmi:type="applicationbnd:AllAuthenticatedUsers" xmi:id="AllAuthenticatedUsers_1" name="AllAuthenticatedUsers"/>
      <role href="META-INF/application.xml#SecurityRole_1"/>
    </authorizations>
  </authorizationTable>
  <application href="META-INF/application.xml#Application_ID"/>
  <runAsMap xmi:id="RunAsMap_1"/>
</applicationbnd:ApplicationBinding>

How to configure WebSphere to authenticate against AD

1. Login to the WAS admin https://was.corp.dom:9043/ibm/console/ as an existing admin
2. Click on Security -> Global security
3. Choose standalone ldap registry in the pull down window for ‘Available realm definitions’ then click configure…
4. Put in the following parameters:
   1. Primary administrative user name: adminid_from_AD
   2. Type of LDAP server: Microsoft Active Directory
   3. Host: primary_domain_controller.corp.dom
   4. Base dn: dc=corp,dc=dom
   5. Bind dn: cn=adminid_from_AD,ou=users,dc=corp,dc=dom
   6. Enter password
5. Hit test to test the connect and then ok.
6. At the top hit save.
7. Go to Administrative group roles, hit add, change the search string to the name of the group that will be WAS admins and click add, then save.
8. Change the “federated directories” to the “standalone ldap registry” in the “available real definitions” drop-box. Click “set as current”
9. Check “enable application security” under Application Security
10. Click apply and then save
11. Reinstall the Websphere service. On the WAS Server run the following in the command prompt (correct names as appropriate):

F:\IBM\WebSphere\AppServer\bin\WASService.exe -remove WASNode01
F:\IBM\WebSphere\AppServer\bin\WASService.exe -add WASNode01 -servername server1 -profilepath "...\WebSphere\AppServer\profiles\AppSrv01" -configroot "...\WebSphere\AppServer\profiles\AppSrv01\config" -logroot "...\WebSphere\AppServer\profiles\AppSrv01\logs\server1" -logFile "...\WebSphere\AppServer\profiles\AppSrv01\logs\server1\WASNode01 Service.log" -washome "...\WebSphere\AppServer" -restart false -stopArgs "-username adminid_from_AD -password passwordhere " -starttype automatic –encodeparams

12. Restart WAS.
13. First stop it and try to access it. Make sure that it can not be accessed on the admin console
    1. If it is still up, login onto the WAS server, start the command prompt and stop WebSphere using following command:

 ...\websphere\appserver\profiles\appsrv01\bin\stopserver.bat server1

1. 2. Provide proper admin credentials
14. Start WAS back up
15. Verify that you can login as yourself to the WebSphere admin console

How to change session expiration

• in WAS admin console (:9090/admin) clck applications->enterprise applications->enRole->Session Management->Session Timeout)
• Restart enRole
• Also you need to change the web.xmls

Session-Timeout (how long it takes for the system to take you back to the logon screen):

File             line
---------       -------------------------------------------------
web.xml:         10

• Ok, first we need to find the correct web.xml file - and there are a number of them.

set was_home=C:\Progra~1\WebSphere
dir %was_home%\AppServer\installedApps\web.xml /b /s>one &findstr /i /c:enrole one
C:\Progra~1\WebSphere\AppServer\installedApps\appname\enRole.ear\app_web.war\WEB-INF\web.xml
C:\Progra~1\WebSphere\AppServer\installedApps\appname\enRole.ear\passwordsynch_web.war\WEB-INF\we
C:\>notepad C:\Progra~1\WebSphere\AppServer\installedApps\appname\enRole.ear\app_web.war\WEB-INF\web.xml

How to change the ports for the WebSphere Application Server - Express

The embedded version of WebSphere Application Server - Express uses four default port settings:

Http Transport (port 1): 9080
Http Transport (port 2): 9443
Bootstrap/rmi port: 2809
Soap connector port: 8880
Http Transport port 1

• Find the line containing the port number 9080 in the following files and replace the 9080 with the port number that you want:

$WASHOME\config\cells\DefaultNode\nodes\DefaultNode\servers\server1\server.xml
$WASHOME\config\cells\DefaultNode\virtualhosts.xml
Http Transport port 2

• Find the line containing the port number 9443 in the following files and replace the 9443 with the port number that you want:

$WASHOME\config\cells\DefaultNode\nodes\DefaultNode\servers\server1\server.xml
$WASHOME\config\cells\DefaultNode\virtualhosts.xml
* Bootstrap/rmi port

Find the line containing the port number 2809 in the following file and replace the 2809 with the port number that you want:

$WASHOME\config\cells\DefaultNode\nodes\DefaultNode\serverindex.html

• Soap connector port

Find the line containing the port number 8880 in the following file and replace the 8880 with the port number that you want:

$WASHOME\config\cells\DefaultNode\nodes\DefaultNode\serverindex.html

How to change IP for the WebSphere Application Server - Express to listen on

Same procedure as the one for changing a port, but change "host" instead of "port". Use comma to put both short and FQDN.

How to check WAS version

/opt/IBM/WebSphere/AppServer/bin/versionInfo.sh

How to configure WAS for SSL

• Restart server1
• Goto WPS server WAS admin interface: http://server:9090/admin
• Login as wpsbind

Environment->virutal hosts->default_host->host aliases->new

name *
port 443

• Ok->save->save. Click update web server plug-in -> ok
• Copy Y:\WebSphere\AppServer\config\cells\plugin-cfg.xml X:\WebSphere\AppServer\config\cells\

where y is on was server and x is on ihs server

• Restart server1 on WPS server
• Test by going to http://server/snoop and https://server/snoop

How to configure WAS or WPS to start as a service

WASService -add server2 -servername server2 -wasHome "D:\Program Files\WebSphere\AppServer" -logfile "D:\Program Files\WebSphere\AppServer\logs\server2\startServer.log" -logRoot "D:\Program Files\WebSphere\AppServer\logs\server2" -restart true

See [1]

How to delete a WAS 6.x profile

E:\WebSphere\AppServer\bin>wasprofile.bat -unaugment -profileName AppSrv01
INSTCONFSUCCESS: Profile unaugmentation succeeded.
E:\WebSphere\AppServer\bin>wasprofile.bat -delete -profileName AppSrv01
INSTCONFSUCCESS: Success: The profile no longer exists.

How to enable and Disable WAS Tracing for Security Components

It is recommended to enable this feature until you are satisfied that everything is working correctly. The page is accessed through WAS Administrative console. Go to Troubleshooting->Logs and trace. Select the server you want to trace (another way is Servers->Application Servers. Select the server you want to trace. Click on Logging and Tracing Properties). Click on Diagnostic Trace Service In the Trace Specification text box change to:

com.ibm.ws.security.*=all=enabled

Or

*=all=disabled

Click Apply for the changes to take affect. The trace.log file will appear in the log/<server name> directory under the WAS installation path.

How to get a dump of the hung threads in WAS

goto WAS_HOME\bin run wsadmin Type:

$AdminControl invoke [$AdminControl completeObjectName type=JVM,process=MY_JVM_NAME_HERE,*] dumpThreads

How to restart WAS (App Server)

when bouncing WAS service does not work

D:\WebSphere\AppServer\bin\stopServer server1 -username wpsbind -password ****
D:\WebSphere\AppServer\bin\startServer server1 -username wpsbind -password ****

How to update a WebSphere IHS plugin

WebSphere\AppServer\bin\GenPluginCfg.sh

or through WAS admin console -> Environment -> Update WebServerPlugin Then physically move the file on the IHS server

copy Y:\WebSphere\AppServer\config\cells\plugin-cfg.xml X:\WebSphere\AppServer\config\cells\

How to version verification command for WAS6 and WAS5.1

• WAS6.0:

bin\versionInfo.bat -maintenancePackages

• WAS5.1:

bin\versionInfo.bat -fixes

How to clear WAS JSP or JIT compiler cache

Helpful in situations like this one:

Error 404: SRVE0202E: Servlet [/jsp/logon/LogonLayout.jsp]: org.apache.jsp._LogonLayout was found, but is corrupt: SRVE0227I: 1. Check that the class resides in the proper package directory. SRVE0228I: 2. Check that the classname has been defined in the server using the proper case and fully qualified package. SRVE0229I: 3. Check that the class was transferred to the filesystem using a binary transfer mode. SRVE0230I: 4. Check that the class was compiled using the proper case (as defined in the class definition). SRVE0231E: 5. Check that the class file was not renamed after it was compiled.

Clear

"A:\Program Files\ibm\WebSphere\AppServer\profiles\AppSrv01\temp\ADNode01\server1"

How to disable WAS security

wsadmin -conttype NONE
securityoff

If it fails backup security.xml file, change the very first enabled=”true” to enabled=”false” and restart the servers