I have noted down the steps that I had taken for doing an installation of C2M 2.7.0.3 product on Windows 64bit OS. Have tried to highlight issues that came up. Also have mentioned the exact paths where the application has been installed. You can use the same OS paths wherever possible. This will help you in following the steps. Alternatively, if you wish to install the application in your desired location, make appropriate modifications in the paths while following the steps.
Since there are many steps for complete installation, I have divided it into three blogs instead of one single blog. This is the second part - Download and Installation of C2M.
Part I - Download of Softwares and Installation of Prerequisites
Since there are many steps for complete installation, I have divided it into three blogs instead of one single blog. This is the second part - Download and Installation of C2M.
Part I - Download of Softwares and Installation of Prerequisites
Part II - Download and Installation of C2M product
Part III - Deployment of C2M product in Weblogic using Native Installation
Part III - Deployment of C2M product in Weblogic using Native Installation
This blog covers steps for downloading and installing C2M product.
Oracle C2M download
Navigate to https://edelivery.oracle.com/
Login with your oracle user login
Search with 'Customer to Meter'
Select Oracle Utilities Customer to Meter 2.7.0.3.0
Navigate to top right corner of select downloads and click on Continue
Below screen opens up. Select Platform as Windows 64
Click on Continue Button
Click on Download button and download all the files
C2M Database installation
This step assumes that you have already covered the installation of database software covered in ‘software prerequisites’.
Configure Listener
Configure a Listener first before creating database.
Go to start. Go to Oracle Folder and select ‘Net Configuration Assistant’
Select Listener configuration
Select Add
Give a name to Listerner. Have given ‘LISTENER’
Click on Next and save the configuration.
Verify that the listener is up and running in Services
If you don’t configure the listener before creating the database, you will have to manually take care of linking a listener to your database. If listener is already present on the system, then the product dynamically links the database service to the listener when the database is created. No separate steps are needed.
Creating database
Navigate to Start -> Oracle Home -> Database Configuration Assistant
Select ‘Create a database’
Enter global database name as c2m2703
Update the database location to C:/c2m/database as shown below.
Click on Next and complete the installation
Verify that the database service is up and running in services
Next navigate to Oracle product home-> network->admin->tnsname.ora
Open tnsname.ora file
Verify that the entries for C2M2703 service is present and listener is attached to the service.
Next go to sqldeveloper and verify that you are able to connect to the database
Test with username as 'sys'
Put the password entered when creating the database
Ensure Role is set to 'SYSDBA'
Click on Test button. Status should show as Success
Next click on Connect and login to the database
Creating database users and granting access
Connect to the database with 'sys' user
Execute the following sqls
Modify the path in first statement as per your database installation folder
Importing Demo Database
Next execute the following sql
SELECT directory_name, directory_path FROM dba_directories where directory_name = 'DATA_PUMP_DIR';
DATA_PUMP_DIR C:\app\virtual\admin\c2m2703\dpdump\
Navigate to the location in the output of the query.
Navigate to V983681-01.zip\C2M\Demo
Go to the file exp_demo.dmp.gz
Extract the file using some extract tool like 7zip
Copy the extracted file exp_demo.dmp to the DATA_PUMP_DIR location
Next open a command prompt with ‘Run as Administrator’
Run the following import command
impdp directory=data_pump_dir dumpfile=exp_demo.dmp logfile=exp_demo.log schemas=CISADM
If the system variables for PATH have been configured, this will automatically call the impdp program in C:\app\virtual\product\12.2.0\dbhome_1\bin directory
The system will ask for login
Enter username as sys@c2m2703 as sysdba
This will import the entire demo database schema to your installed database
This operation takes around 25 min to 1 hour depending on your RAM size
Once the entire import operation is complete, verify the log output to check that no errors were present.
First error that comes saying CISADM user already present can be ignored.
Creating Synonyms for CISUSER and CISREAD
Extract the V983333-01.zip file.Open cmd prompt with run as Administrator option
Set the classpath variable and point it to above location where the V983333-01 is present.
SET CLASSPATH=C:\myfolder\OracleDownloads\C2M_2.7.0.3\V983333-01\jarfiles\*
Ensure there is no blank space in the path location.
Next run the following command
"%JAVA_HOME%"\bin\java -Xmx1500M com.oracle.ouaf.oem.install.OraGenSec -d CISADM,CISADM,jdbc:oracle:thin:@localhost:1521/C2M2703 -u CISUSER,CISREAD -r CIS_USER,CIS_READ -a A -p CISUSER,CISREAD -l output.log
This creates the synonyms for all objects in CISADM for CISUSER and CISREAD users
Next open sql developer and verify that you are able to connect to 'CISADM' user
The password is 'CISADM' only
Once it is connected you can verify that all the database entities are present
You can also verify that the synonyms are created for CISUSER and CISREAD
By navigating to Other Users -> CISUSER -> Synonyms from above objects browser on sql developer
This completes the database part of C2M installation
C2M Application installation
Framework installation
Copy the file V983334-01.zip/FW-V4.4.0.2.0-MultiPlatform.jarTo a temporary folder C:/temp
Open a command prompt with ‘Run as Administrator’ option
Navigate to the temporary folder
cd C:/temp
jar -xvf FW-V4.4.0.2.0-MultiPlatform.jar
Note* - Ensure you don't extract the jar file at the same location where you extracted V983334-01.zip. Create a directory (C:/temp) directly under root directory (C:) and use that. If you do it from same location as zip file, it might increase the time taken by your installation process. Also there can be errors due to windows filepath size being too long.
cd C:/temp
jar -xvf FW-V4.4.0.2.0-MultiPlatform.jar
Note* - Ensure you don't extract the jar file at the same location where you extracted V983334-01.zip. Create a directory (C:/temp) directly under root directory (C:) and use that. If you do it from same location as zip file, it might increase the time taken by your installation process. Also there can be errors due to windows filepath size being too long.
A sub-directory named “FW-V4.4.0.2.0” is created
Navigate to this directory
cd FW-V4.4.0.2.0
run install.cmd
Ensure you use ‘/’ instead of ‘\’ in file path highlighted above. This causes issue later.
Enter P
Below environment configuration will open up. Using the option numbers, update the values as given below. Ensure you use localhost instead of the autopopulated machine name. This is needed for native installation of application in weblogic later.
Note*: Below highlighted config value for JNDI password has to be same when you enter the password for system user during native weblogic configuration (Covered in Part 3 of this blog series).
Also set Deploy application viewer to false in case you don't need it. This reduces the ear build time during installation. You can set it to true later if you need it.
Enter P and complete installation
Verify that the installation completes without any errors.
Configuring OUAF keystore
Next part is setting configuring OUAF keystoreVerify that the keystore files .ouaf_keystore and .ouaf_storepass are present at the following location C:\c2m\ouaf\C2M2703\ks (%SPLEBASE\ks%)
If they are not present you can regenerate then using the following command
initialSetup.cmd –k
After that next, run configureEnv.cmd
Reenter the passwords for all configuration values
This encrypts the password with the keystore
You might face some error saying keystore file is not present, in that case verify the error logs, it might be due to incorrect keystore file path.
This is because ‘\’ is used instead of ‘/’ in some paths
To correct this error, do the following
Navigate to C:\c2m\ouaf\C2M2703\splapp\standalone\config (%SPLEBASE\splapp\standalone\config %)
Open spl.properties file and update the following paths
com.oracle.ouaf.file.tempStorage.dir=C:/c2m/ouaf/sploutput/C2M2703/tmp
com.oracle.ouaf.system.keystore.file=C:/c2m/ouaf/C2M2703/ks/.ouaf_keystore
com.oracle.ouaf.system.keystore.passwordFileName=C:/c2m/ouaf/C2M2703/ks/.ouaf_storepass
com.oracle.ouaf.system.truststore.file=C:/c2m/ouaf/C2M2703/ks/.ouaf_truststore
com.oracle.ouaf.system.truststore.passwordFileName=C:/c2m/ouaf/C2M2703/ks/.ouaf_truststore_pass
Replace ‘\’ with ‘/’ wherever present in above path
Rerun configureEnv.cmd
Next run initialSetup.cmd
If you had updated spl.properties earlier then again update the paths after initialSetup completes.
Next navigate to %SPLEBASE%/bin folder
Run splenviron.cmd -e C2M2703
Navigate back to bin folder
Run following commands
perl run_java_standalone.plx com.splwg.shared.common.ResetCryptographyKey
invokeDBUpdatePatch.cmd
Verify that both commands ran successfully.
This completes the configuration of OUAF keystore part of the installation
CCB installation
Navigate to V983674-01.zipCopy the file CCB-V2.7.0.3.0-MultiPlatform.jar to a temporary directory (C:/temp)
Open a command prompt with ‘Run as administrator option’
Next navigate to %SPLEBASE%/bin folder
Run splenviron.cmd -e C2M2703
Navigate to the temporary folder (C:/temp)
Run the following command jar –xvf CCB-V2.7.0.3.0-MultiPlatform.jar
A sub-directory named “CCB.V2.7.0.3.0” is created
Navigate to the folder “CCB.V2.7.0.3.0” (C:\temp\CCB.V2.7.0.3.0)
Run the command install.cmd
Options will come up. Enter ‘P’ and click on enter.
Wait for the installation to complete. This will take some time (around 1 hour). After installation is complete verify that there were no errors.
Note* - Ensure you don't extract the jar file at the same location where you extracted V983674-01.zip. Create a directory (C:/temp) directly under root directory (C:) and use that. If you do it from same location as zip file, it might increase the time taken by your installation process. Also there can be errors due to windows filepath size being too long.
MDM installation
Navigate to the V983676-01.zipCopy the file MDM_V2.3.0.2.0.zip to C:\
Rename it to t.zip
Extract the folder to C:\
“MDM.V2.3.0.2.0” folder should be created in C:\
Open a command prompt with ‘Run as administrator option’
Next navigate to %SPLEBASE%/bin folder
Run splenviron.cmd -e C2M2703
Navigate to the folder MDM.V2.3.0.2.0 (C:\MDM.V2.3.0.2.0)
Run the command install.cmd
Installation options should come up.
Enter ‘P’ and complete the installation.
WAM installation
Navigate to V983678-01.zipCopy the file WAM-V2.2.0.6.0-Multiplatform.jar to temporary directory (C:/temp)
Open a command prompt with ‘Run as administrator option’
Next navigate to %SPLEBASE%/bin folder
Run splenviron.cmd -e C2M2703
Navigate to the temporary folder (C:/temp)
Run the following command jar –xvf WAM-V2.2.0.6.0-Multiplatform.jar
A sub-directory named “W1.V2.2.0.6.0” is created
Navigate to the folder “W1.V2.2.0.6.0” (C:\temp\W1.V2.2.0.6.0)
Run the command install.cmd
Options will come up. Enter ‘P’ and click on enter.
Note* - Ensure you don't extract the jar file at the same location where you extracted V983678-01.zip. Create a directory (C:/temp) directly under root directory (C:) and use that. If you do it from same location as zip file, it might increase the time taken by your installation process. Also there can be errors due to windows filepath size being too long.
Installing Oracle Utilities Application Framework V4.4.0.2.0 Prerequisite Single Fixes
Navigate to V983672-01.zipCopy the file C2M-V27030-FW-PREREQ-MultiPlatform.jar to temporary directory (C:/temp)
Open a command prompt with ‘Run as administrator option’
Next navigate to %SPLEBASE%/bin folder
Run splenviron.cmd -e C2M2703
Navigate to the temporary folder (C:/temp)
Run the following command jar –xvf C2M-V27030-FW-PREREQ-MultiPlatform.jar
A sub-directory named “FW-V4.4.0.2.0-Rollup” is created
Navigate to the folder “FW-V4.4.0.2.0-Rollup\Application” (C:\temp\FW-V4.4.0.2.0-Rollup\Application)
Run the command installSFgroup.cmd
Wait for the command execution to complete. Verify that no errors occurred.
Note* - Ensure you don't extract the jar file at the same location where you extracted V983672-01.zip. Create a directory (C:/temp) directly under root directory (C:) and use that. If you do it from same location as zip file, it might increase the time taken by your installation process. Also there can be errors due to windows filepath size being too long.
Installing Oracle Utilities Customer to Meter
Navigate to V983680-01.zipCopy the file C2M-V2.7.0.3.0-MultiPlatform.jar to temporary directory (C:/temp)
Open a command prompt with ‘Run as administrator option’
Next navigate to %SPLEBASE%/bin folder
Run splenviron.cmd -e C2M2703
Navigate to the temporary folder (C:/temp)
Run the following command jar –xvf C2M-V2.7.0.3.0-MultiPlatform.jar
A sub-directory named “C2M.V2.7.0.3.0” is created
Navigate to the folder “C2M.V2.7.0.3.0” (C:\temp\C2M.V2.7.0.3.0)
Run the command install.cmd
Options will come up. Enter ‘P’ and click on enter.
This completes application installation of Oracle C2M (this included installation of OUAF framework, CCB, MDM, WAM, C2M)
Note* - Ensure you don't extract the jar file at the same location where you extracted V983680-01.zip. Create a directory (C:/temp) directly under root directory (C:) and use that. If you do it from same location as zip file, it might increase the time taken by your installation process. Also there can be errors due to windows filepath size being too long.
Generating Application Viewer
This is an optional installation of Application viewerFor doing this, open a command prompt with ‘Run as administrator option’
Next navigate to %SPLEBASE%/bin folder
Run splenviron.cmd -e C2M2703
Navigate back to bin folder
Run genappvieweritems.cmd command
Once the command completes, verify that there are no errors.
This concludes part II, click on below link to go to next part
