Web Self Service installation on Windows
Posted
by Rajesh Sharma
on Oracle Blogs
See other posts from Oracle Blogs
or by Rajesh Sharma
Published on Sat, 29 May 2010 12:44:38 +0000
Indexed on
2010/05/29
13:03 UTC
Read the original article
Hit count: 730
Web Self Service (WSS) installation on windows is pretty straight forward but you might face some issues if deployed under tomcat. Here's a step-by-step guide to install Oracle Utilities Web Self Service on windows.
Below installation steps are done on:
- Oracle Utilities Framework version 2.2.0
- Oracle Utilities Application - Customer Care & Billing version 2.2.0
- Application server - Apache Tomcat 6.0.13 on default port 6500
- Other settings include:
- SPLBASE = C:\spl\CCBDEMO22
- SPLENVIRON = CCBV22
- SPLWAS = TCAT
Follow these steps for a Web Self Service installation on windows:
- Download Web Self Service application from edelivery.
- Copy the delivery file Release-SelfService-V2.2.0.zip from the Oracle Utilities Customer Care and Billing version 2.2.0 Web Self Service folder on the installation media to a directory on your Windows box where you would like to install the application, in our case it's a temporary folder C:\wss_temp.
- Setup application environment, execute splenviron.cmd -e <ENVIRON_NAME>
- Create base folder for Self Service application named SelfService under %SPLEBASE%\splapp\applications
- Install Oracle Utilities Web Self Service
C:\wss_temp\Release-SelfService-V2.2.0>install.cmd -d %SPLEBASE%\splapp\applications\SelfService
- Web Self Service installation menu. Populate environment values for each item.
********************************************************
Pick your installation options:
********************************************************
1. Destination directory name for installation. | C:\spl\CCBDEMO22\splapp\applications\SelfService
2. Web Server Host. | CCBV22
3. Web Server Port Number. | 6500
4. Mail SMTP Host. | CCBV22
5. Top Product Installation directory. | C:\spl\CCBDEMO22
6. Web Application Server Type. | TCAT
7. When OAS: SPLWeb OC4J instance name is required. | OC4J1
8. When WAS: SPLWeb server instance name is required. | server1
P. Process the installation.
Each item in the above list should be configured for a successful installation.
Choose option to configure or (P) to process the installation: P
Option 7 and Option 8 can be ignored for TCAT.
- Above step installs SelfService.war file in the destination directory. We need to explode this war file. Change directory to the installation destination folder, and
C:\spl\CCBDEMO22\splapp\applications\SelfService>jar -xf SelfService.war
- Review SelfServiceConfig.properties and CMSelfServiceConfig.properties. Change any properties value within the file specific to your installation/site. Generally default settings apply, for this exercise assumes that WEB user already exists in your application database.
For more information on property file customization, refer to Oracle Utilities Web Self Service Configuration section in Customer Care & Billing Installation Guide.
- Add context entry in server.xml located under tomcat-base folder C:\spl\CCBDEMO22\product\tomcatBase\conf
...
<!-- SPL Context -->
<Context path="" docBase="C:/spl/CCBDEMO22/splapp/applications/root" debug="0" privileged="true"/>
<Context path="/appViewer" docBase="C:/spl/CCBDEMO22/splapp/applications/appViewer" debug="0" privileged="true"/>
<Context path="/help" docBase="C:/spl/CCBDEMO22/splapp/applications/help" debug="0" privileged="true"/>
<Context path="/XAIApp" docBase="C:/spl/CCBDEMO22/splapp/applications/XAIApp" debug="0" privileged="true"/>
<Context path="/SelfService" docBase="C:/spl/CCBDEMO22/splapp/applications/SelfService" debug="0" privileged="true"/>
...
- Add User in tomcat-users.xml file located under tomcat-base folder C:\spl\CCBDEMO22\product\tomcatBase\conf
<user username="WEB" password="selfservice" roles="cisusers"/>
Note the password is "selfservice", this is the default password set within the SelfServiceConfig.properties file with base64 encoding.
- Restart the application (spl.cmd stop | start)
12. Although Apache Tomcat version 6.0.13 does not come with the admin pack, you can verify whether SelfService application is loaded and running, go to following URL http://server:port/manager/list, in our case it'll be http://ccbv22:6500/manager/list
Following output will be displayed
OK - Listed applications for virtual host localhost
/admin:running:0:C:/tomcat/apache-tomcat-6.0.13/webapps/ROOT/admin
/XAIApp:running:0:C:/spl/CCBDEMO22/splapp/applications/XAIApp
/host-manager:running:0:C:/tomcat/apache-tomcat-6.0.13/webapps/host-manager
/SelfService:running:0:C:/spl/CCBDEMO22/splapp/applications/SelfService
/appViewer:running:0:C:/spl/CCBDEMO22/splapp/applications/appViewer
/manager:running:1:C:/tomcat/apache-tomcat-6.0.13/webapps/manager
/help:running:0:C:/spl/CCBDEMO22/splapp/applications/help
/:running:0:C:/spl/CCBDEMO22/splapp/applications/root
Also ensure that the XAIApp is running.
- Run Oracle Utilities Web Self Service application http://server:port/SelfService in our case it'll be http://ccbv22:6500/SelfService
- Still doesn't work? And you get '503 HTTP response' at the time of customer registration?
This is because XAI service is still unavailable. There is initialize.waittime set for a default value of 90 seconds for the XAI Application to come up.
Remember WSS uses XAI to perform actions/validations on the CC&B database.
© Oracle Blogs or respective owner