OUAF C2M 2.9.0.0 installation on Windows64

This blog is for anyone looking to install Oracle C2M 2.9.0.0.

In this blog I have mainly tried to highlight the areas where there are differences between the installation steps for C2M 2.9 and C2M 2.7. For more detailed steps for installation refer my earlier blog for C2M 2.7.0.3 installation.

http://myouafworld.blogspot.com/2020/06/ouaf-c2m-2703-installation-on-windows64.html

Database installation steps:

For C2M 2.9.0.0, use Oracle 19c database.

Add Listener:

Create Database:

Login to database as sys as SYSDBA and verify that you are able to connect.

If you have multiple database services on the same listener use below method to join, else you can used sys as SYSDBA to connect. Also if there are multiple databases linked to same listener, ensure you stop the databases other than the one for C2M2900.

This is the first change for C2M 2.9, the database needs to be updated for extending the string size for VarChar. Refer below steps for doing the same.

SQLplus commands for updating database to EXTENDED

Connect to sqlplus Connect using sys as sysdba Shutdown database SHUTDOWN NORMAL Start database in upgrade mode STARTUP UPGRADE Update value to EXTENDED alter system set max_string_size='EXTENDED'; Run script @C:/myfolder/OracleDownloads/OracleDatabase/Oracle19c/V982656-01/rdbms/admin/utl32k.sql Restart DB in Normal Mode SHUTDOWN STARTUP Run script @C:/myfolder/OracleDownloads/OracleDatabase/Oracle19c/V982656-01/rdbms/admin/utlrp.sql

Use below command for logging in if you have multiple databases linked to same listener

sqlplus sys/password@localhost:1523/C2M2900 as SYSDBA

SQL output for reference

Microsoft Windows [Version 10.0.19043.1706] (c) Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>sqlplus sys/password@localhost:1523/C2M2900 as SYSDBA SQL*Plus: Release 19.0.0.0.0 - Production on Sat May 28 01:11:54 2022 Version 19.3.0.0.0 Copyright (c) 1982, 2019, Oracle.  All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.3.0.0.0 SQL> SHUTDOWN NORMAL Database closed. Database dismounted. ORACLE instance shut down. ERROR: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor Warning: You are no longer connected to ORACLE. SQL> STARTUP UPGRADE SP2-0640: Not connected SQL> SHUTDOWN NORMAL SQL> SQL> ^C C:\WINDOWS\system32>sqlplus SQL*Plus: Release 19.0.0.0.0 - Production on Sat May 28 01:25:42 2022 Version 19.3.0.0.0 Copyright (c) 1982, 2019, Oracle.  All rights reserved. Enter user-name: sys as SYSDBA Enter password: Connected to an idle instance. SQL> select name from USER$; select name from USER$ * ERROR at line 1: ORA-01034: ORACLE not available Process ID: 0 Session ID: 0 Serial number: 0 SQL> STARTUP UPGRADE ORACLE instance started. Total System Global Area 3841981992 bytes Fixed Size                  9035304 bytes Variable Size             738197504 bytes Database Buffers         3087007744 bytes Redo Buffers                7741440 bytes Database mounted. Database opened. SQL> alter system set max_string_size='EXTENDED'; System altered. SQL> @C:/myfolder/OracleDownloads/OracleDatabase/Oracle19c/V982656-01/rdbms/admin/utl32k.sql Session altered. Session altered. DOC>####################################################################### DOC>####################################################################### DOC>   The following statement will cause an "ORA-01722: invalid number" DOC>   error if the database has not been opened for UPGRADE. DOC> DOC>   Perform a "SHUTDOWN ABORT"  and DOC>   restart using UPGRADE. DOC>####################################################################### DOC>####################################################################### DOC># no rows selected DOC>####################################################################### DOC>####################################################################### DOC>   The following statement will cause an "ORA-01722: invalid number" DOC>   error if the database does not have compatible >= 12.0.0 DOC> DOC>   Set compatible >= 12.0.0 and retry. DOC>####################################################################### DOC>####################################################################### DOC># PL/SQL procedure successfully completed. Session altered. 0 rows updated. Commit complete. System altered. PL/SQL procedure successfully completed. Commit complete. System altered. Session altered. Session altered. Table created. Table created. Table created. Table truncated. 0 rows created. PL/SQL procedure successfully completed. STARTTIME -------------------------------------------------------------------------------- 05/28/2022 01:28:49.612000000 PL/SQL procedure successfully completed. No errors. PL/SQL procedure successfully completed. Session altered. Session altered. 0 rows created. no rows selected no rows selected DOC>####################################################################### DOC>####################################################################### DOC>   The following statement will cause an "ORA-01722: invalid number" DOC>   error if we encountered an error while modifying a column to DOC>   account for data type length change as a result of enabling or DOC>   disabling 32k types. DOC> DOC>   Contact Oracle support for assistance. DOC>####################################################################### DOC>####################################################################### DOC># PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. Commit complete. Package altered. Package altered. Session altered. SQL> SHUTDOWN Database closed. Database dismounted. ORACLE instance shut down. SQL> STARTUP ORACLE instance started. Total System Global Area 3841981992 bytes Fixed Size                  9035304 bytes Variable Size             738197504 bytes Database Buffers         3087007744 bytes Redo Buffers                7741440 bytes Database mounted. Database opened. SQL> @C:/myfolder/OracleDownloads/OracleDatabase/Oracle19c/V982656-01/rdbms/admin/utlrp.sql Session altered. TIMESTAMP -------------------------------------------------------------------------------- COMP_TIMESTAMP UTLRP_BGN              2022-05-28 01:32:05 DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid DOC>   objects in the database. Recompilation time is proportional to the DOC>   number of invalid objects in the database, so this command may take DOC>   a long time to execute on a database with a large number of invalid DOC>   objects. DOC> DOC>   Use the following queries to track recompilation progress: DOC> DOC>   1. Query returning the number of invalid objects remaining. This DOC>      number should decrease with time. DOC>         SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6); DOC> DOC>   2. Query returning the number of objects compiled so far. This number DOC>      should increase with time. DOC>         SELECT COUNT(*) FROM UTL_RECOMP_COMPILED; DOC> DOC>   This script automatically chooses serial or parallel recompilation DOC>   based on the number of CPUs available (parameter cpu_count) multiplied DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu). DOC>   On RAC, this number is added across all RAC nodes. DOC> DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel DOC>   recompilation. Jobs are created without instance affinity so that they DOC>   can migrate across RAC nodes. Use the following queries to verify DOC>   whether UTL_RECOMP jobs are being created and run correctly: DOC> DOC>   1. Query showing jobs created by UTL_RECOMP DOC>         SELECT job_name FROM dba_scheduler_jobs DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%'; DOC> DOC>   2. Query showing UTL_RECOMP jobs that are running DOC>         SELECT job_name FROM dba_scheduler_running_jobs DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%'; DOC># PL/SQL procedure successfully completed. TIMESTAMP -------------------------------------------------------------------------------- COMP_TIMESTAMP UTLRP_END              2022-05-28 01:32:13 DOC> The following query reports the number of invalid objects. DOC> DOC> If the number is higher than expected, please examine the error DOC> messages reported with each object (using SHOW ERRORS) to see if they DOC> point to system misconfiguration or resource constraints that must be DOC> fixed before attempting to recompile these objects. DOC># OBJECTS WITH ERRORS -------------------                   0 DOC> The following query reports the number of exceptions caught during DOC> recompilation. If this number is non-zero, please query the error DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors DOC> are due to misconfiguration or resource constraints that must be DOC> fixed before objects can compile successfully. DOC> Note: Typical compilation errors (due to coding errors) are not DOC>       logged into this table: they go into DBA_ERRORS instead. DOC># ERRORS DURING RECOMPILATION ---------------------------                           0 Function created. PL/SQL procedure successfully completed. Function dropped. PL/SQL procedure successfully completed. SQL>

Login to database as sys as SYSDBA.

Run below db statements.

CREATE TABLESPACE CISTS_01 LOGGING DATAFILE 'C:/c2m/database/c2m2900/oradata/C2M2900/cists01.dbf' SIZE 1024M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M; CREATE ROLE CIS_ADM NOT IDENTIFIED; CREATE ROLE CIS_USER NOT IDENTIFIED; CREATE ROLE CIS_READ NOT IDENTIFIED; GRANT CREATE TABLE TO CIS_ADM; GRANT CREATE VIEW TO CIS_ADM; GRANT CREATE SYNONYM TO CIS_ADM; GRANT CREATE MATERIALIZED VIEW TO CIS_ADM; GRANT CREATE SEQUENCE TO CIS_ADM; GRANT CREATE INDEXTYPE TO CIS_ADM; GRANT CREATE ROLE TO CIS_ADM; GRANT CREATE TRIGGER TO CIS_ADM; GRANT CREATE PROCEDURE TO CIS_ADM; GRANT CREATE SYNONYM TO CIS_USER; GRANT CREATE SYNONYM TO CIS_READ; CREATE USER CISADM IDENTIFIED BY CISADM DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP PROFILE DEFAULT; ALTER USER CISADM QUOTA UNLIMITED ON CISTS_01; GRANT CREATE SESSION TO CISADM; GRANT CREATE TABLESPACE TO CISADM; GRANT READ on DBA_TABLESPACES TO CISADM; GRANT ALTER TABLESPACE TO CISADM; GRANT UNLIMITED TABLESPACE TO CISADM; GRANT DROP TABLESPACE TO CISADM; GRANT EXECUTE on DBMS_UTILITY TO CISADM; GRANT SELECT_CATALOG_ROLE TO CISADM; GRANT EXECUTE_CATALOG_ROLE TO CISADM; GRANT CIS_ADM TO CISADM; grant execute on dbms_rls to CISADM with grant option; grant execute on dbms_crypto to CISADM; CREATE USER CISUSER PROFILE DEFAULT IDENTIFIED BY CISUSER DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP; ALTER USER CISUSER QUOTA UNLIMITED ON CISTS_01; GRANT CIS_USER to CISUSER; GRANT CREATE SESSION TO CISUSER; CREATE USER CISREAD IDENTIFIED BY CISREAD DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP; ALTER USER CISREAD QUOTA UNLIMITED ON CISTS_01; GRANT CIS_READ to CISREAD; GRANT CREATE SESSION TO CISREAD; CREATE USER CISOPR PROFILE DEFAULT IDENTIFIED BY OPRPLUS DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP; GRANT CREATE SESSION,EXP_FULL_DATABASE TO CISOPR;

Import Demo Database:

Check datapump dir location:

SELECT directory_name, directory_path FROM dba_directories where directory_name = 'DATA_PUMP_DIR';

DATA_PUMP_DIR C:\c2m\dbadmin\app\admin\c2m2800\dpdump/

Extract dmp file and place it in data pump directory

Get the dump file from below location.

C:\myfolder\OracleDownloads\C2M_2.9.0.0\V1020108-01.zip\C2M\Demo

DATA_PUMP_DIR C:\c2m\dbadmin\app\admin\c2m2900\dpdump/

Extract the .gz file and place the exp_demo.dmp file at the data pump dir location

Run below import command on command prompt

impdp directory=data_pump_dir dumpfile=exp_demo.dmp logfile=exp_demo.log schemas=CISADM

Login with username as sys@C2M2900 as SYSDBA

Login with sys user and run below sql.

grant execute on dbms_crypto to CISADM;

Creating Synonyms for CISUSER and CISREAD:

Extract the files in V1020069-01

C:\myfolder\OracleDownloads\C2M_2.9.0.0\V1020069-01\jarfiles

SET CLASSPATH=C:\myfolder\OracleDownloads\C2M_2.9.0.0\V1020069-01\jarfiles\*

"%JAVA_HOME%"\bin\java -Xmx1500M com.oracle.ouaf.oem.install.OraGenSec -d CISADM,CISADM,jdbc:oracle:thin:@localhost:1523/C2M2900 -u CISUSER,CISREAD -r CIS_USER,CIS_READ -a A -p CISUSER,CISREAD -l output.log

Verify that all synonyms are created properly and there are no errors.

Weblogic Installation:

Download steps:

Ensure you download version 12.2.1.4 or above of weblogic

Only below file ‘V983368-01.zip’ is needed for installation.

Installation steps:

Open command prompt, navigate to above location

Run below command

C:\c2m\java\jdk\bin\java –jar fmw_12.2.1.4.0_infrastructure.jar

Below screen opens up, follow the steps shown below.

Weblogic Installation completed.

Application Installation:

Extract all the jar files for CCB, MDM, WAM, C2M and place it in a temporary location.

I have placed them in C:/t location

Use 7-Zip and extract all the jar files. Alternatively you can also use jar -xvf command in command prompt for extracting the files if you don't have 7-Zip application.

All folders are extracted as seen below.

The Framework component (FW) is not available currently in jar format. It is in zip format. Extract the same also and place here.

Navigate to C:\t\FW-V4.5.0.0.0 folder and run install.cmd file

Navigate to FW-V4.5.0.0.0 folder on command prompt and run install.cmd file

Enter values for the menu options as specified below

************************************ * Environment Installation Options * ************************************  1. Environment ID, Roles, Third Party Software Configuration        Environment ID:                                    69029504        Server Roles:                                      batch,online        Oracle Client Home Directory:                      C:\myfolder\OracleDownloads\OracleDatabase\Oracle19c\V982656...        Web Java Home Directory:                           C:\c2m\java\jdk        Hibernate JAR Directory:                           C:\c2m\hibernate        ONS JAR Directory:        Web Application Server Home Directory:             C:/c2m/weblogic/12.2.1.4.0/Oracle/Middleware/Oracle_Home/wls...        Additional JAR Directory:  2. Keystore Options        Import Keystore Directory: 50. Environment Installation Options        Environment Mount Point:                           C:/c2m/ouaf        Log Files Mount Point:                             C:/c2m/ouaf/sploutput        Environment Name:                                  C2M2900        Install Application Viewer Module:                 false        Install Sample CM Source Code:                     true Each item in the above list should be configured for a successful install. Choose option (1,2,50, <P> Process, <X> Exit):

Enter P and process it

Below menu opens up. Enter the values as shown below.

************************************* * Environment Configuration C2M2900 * *************************************  1. Environment Description        Environment Description:                           c2m2900  2. Business Application Server Configuration        Business Server Host:                              localhost        Business Server Application Name:                  SPLService  3. Web Application Server Configuration        Web Server Host:                                   localhost        WebLogic SSL Port Number:                          6501        WebLogic Console Port Number:                      7001        Web Context Root:                                  ouaf        WebLogic JNDI User ID:                             system        WebLogic JNDI Password:                            ouafadmin        WebLogic Server Name:                              c2m2900server        Web Server Application Name:                       SPLWeb        Deploy Application Viewer Module:                  false        Enable The Unsecured Health Check Service:         false        MDB RunAs User ID:                                 SYSUSER        Super User Ids:  4. Database Configuration        Application Server Database User ID:               CISADM        Application Server Database Password:              CISADM        XAI Database User ID:                              CISADM        XAI Database Password:                             CISADM        Batch Database User ID:                            CISADM        Batch Database Password:                           CISADM        Web JDBC DataSource Name:        Database Name:                                     C2M2900        Database Server:                                   localhost        Database Port:                                     1523        ONS Server Configuration:        Database Override Connection String:        Character Based Database:                          false        Oracle Client Character Set NLS_LANG:              AMERICAN_AMERICA.AL32UTF8  5. General Configuration Options        Batch RMI Port:                                    6540        RMI Port number for JMX Business:                  6550        RMI Port number for JMX Web:                       6570        JMX Enablement System User ID:                     system        JMX Enablement System Password:                    ouafadmin        Coherence Cluster Name:                            mycluster        Coherence Cluster Address:                         localhost        Coherence Cluster Port:                            6903        Coherence Cluster Mode:                            dev  6. OUAF TrustStore Options        Import TrustStore Directory: Each item in the above list should be configured for a successful install. Choose option (1,2,3,4,5,6, <P> Process, <X> Exit):

After entering all values, enter P and process it.

Updating keystore:

Verify keystore files are present under ks folder

1. Using configureEnv.cmd, re-enter the menu passwords to encrypt the data.

2. Run initialSetup.cmd to update property files with the encrypted data.

Next navigate to %SPLEBASE%/bin folder

Run splenviron.cmd -e C2M2900

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

Installing the Oracle Utilities Customer Care and Billing Application Component:

In case of no errors, proceed further with installing CCB, MDM, WAM and C2M module in that order.

Navigate to the corresponding folder in command prompt and execute the install.cmd file in each.

No need to change any values in the menu for these modules. Just enter P and process it.

Native installation of C2M 2.9.0.0 on Weblogic:

(Kindly also refer my latest blog for using WLST to do native installation on weblogic. It helps to reduce the time taken as well as reduces any errors. Link to blog: Native installation using WLST)

Refer below steps for deploying the C2M application on Weblogic in native mode

Navigate to C:\c2m\weblogic\12.2.1.4.0\Oracle\Middleware\Oracle_Home\oracle_common\common\bin

Run config.cmd with ‘Run as administrator’ option
Below configuration Wizard screen opens up.
Select Create a new domain
Update the domain location. Instead of base_domain, update it to c2m2900_domain

Select Oracle Restricted JRF option

For deploying the application on weblogic, refer the steps in my earlier blog for deploying SPLService, SPLWeb and ohelp ear files. Before deployment ensure you do the below changes, the size of deployment files has increased in V2.9.0.0. Some configuration changes are needed before proceeding with deployment of SPLService and SPLWeb.

Navigate to C:\c2m\weblogic\12.2.1.4.0\Oracle\Middleware\Oracle_Home\user_projects\domains\c2m2900_domain\bin

startWebLogic.cmd

Add below line in file. Refer screenshot below for location to update.

set JAVA_OPTIONS=%JAVA_OPTIONS% -Dweblogic.deploy.MaxPostSize="2000000000"

(Max value allowed in this option is 21474836480 or 2GB)

Refer to my earlier blog for steps for native installation. I have put in the screenshots for this installation for quick reference.

Set Timeout seconds to 86400 on home -> c2m200_domain

Uncheck on-demand deployment of internal applications on domain. This is only for loading the weblogic admin immediately and does not impact anything else.

Add new machine ‘c2m2900mac’ and set the nodemanager port here

Add new server c2m2900server

Set port to 6500

Set SSL port to 6501 and select machine as c2m2900mac

Set classpath to C:\c2m\ouaf\C2M2900\splapp\standalone\lib\antlr-2.7.7.jar;C:\c2m\weblogic\12.2.1.4.0\Oracle\Middleware\Oracle_Home\wlserver\server\lib\weblogic_sp.jar;C:\c2m\weblogic\12.2.1.4.0\Oracle\Middleware\Oracle_Home\wlserver\server\lib\weblogic.jar

Create new XML Registry

Update the below parameters as defined below. Other values remain same.

Parameter	Setting
Document Builder Factory	com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
SAX Parser Factory	com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
Transformer Factory	com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl

Set name as 'myxmlregistry'

Navigate to Security Realms and open ‘myrealm’

Uncheck combined role mapping check box

Navigate to Credential Mappings -> Providers -> SystemPasswordValidator

Update minimum number of non-Alphabetic characters to 0

Navigate to Users and Groups and create new Group ‘cisusers’

Next create new User ‘system’

Ensure that the password for system user is the same as set in application installation for ‘Weblogic JNDI User id’

Add below groups to ‘system’

Add new user ‘SYSUSER’

Add user to cisusers group

Next navigate to deployments and Install SPLService.ear

Set deployment order to 100

Next install SPLWeb.ear

Set deployment order to 200

Next install ohelp.ear

As seen below all there ear files SPLService.ear, SPLWeb.ear and ohelp.ear have been deployed

Now navigate to servers and start c2m2900server. Ensure you have started nodemanager below starting server.

Next go to browser and enter the application URL

https://localhost:6501/ouaf/cis.jsp

If everything is proper, the login screen will open up. As seen below for 2.9 version, the new redwood UI has been defaulted.

Login with SYSUSER and password as sysuser00

As seen below the main page loads up. This is how the C2M screen looks with the new Redwood UI.

IWS Deployment

Admin server and C2M server should be up and running.

In below command, 7001 port number is weblogic admin port number. Update the port number in the command with the port number configured in your system.

Connect to oracle database

Login as SYS user.
2. On the SQL prompt, run:
@?/rdbms/admin/userlock.sql
3. Grant permission.
grant execute on USER_LOCK to public;

Go to command prompt

Go to $WeblogicHome\oracle_common\common\bin

Run below commands

wlst.cmd
connect("weblogicuser","password","t3://localhost:weblogicAdminconsoleport")
storeUserConfig('$SPLBASE/etc/.wlsuserconfig',' $SPLBASE/etc/.wlsuserkey')

connect("weblogic","password","t3://localhost:7001")

storeUserConfig('C:/c2m/ouaf/C2M2800/etc/.wlsuserconfig','C:/c2m/ouaf/C2M2800/etc/.wlsuserkey')

C:\WINDOWS\system32>cd C:\c2m\weblogic\12.2.1.4.0\Oracle\Middleware\Oracle_Home\user_projects\domains\c2m2900_domain\bin C:\c2m\weblogic\12.2.1.4.0\Oracle\Middleware\Oracle_Home\user_projects\domains\c2m2900_domain\bin>cd C:\c2m\weblogic\12.2.1.4.0\Oracle\Middleware\Oracle_Home\oracle_common\common\bin C:\c2m\weblogic\12.2.1.4.0\Oracle\Middleware\Oracle_Home\oracle_common\common\bin>wlst.cmd Initializing WebLogic Scripting Tool (WLST) ... Jython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away. Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands wls:/offline> connect("weblogic","password","t3://localhost:7001") Connecting to t3://localhost:7001 with userid weblogic ... Successfully connected to Admin Server "C2M2900_AdminServer" that belongs to domain "c2m2900_domain". Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or Admin port should be used instead. wls:/c2m2900_domain/serverConfig/> storeUserConfig('C:/c2m/ouaf/C2M2900/etc/.wlsuserconfig','C:/c2m/ouaf/C2M2900/etc/.wlsuserkey') Creating the key file can reduce the security of your system if it is not kept in a secured location after it is created. Creating new key... The username and password that were used for this WebLogic Server connection are stored in C:/c2m/ouaf/C2M2900/etc/.wlsuserconfig and C:/c2m/ouaf/C2M2900/etc/.wlsuserkey. wls:/c2m2900_domain/serverConfig/>

Navigate to etc folder as shown below, you can see that the .wlsuserconfg and .wlsuserkey files have got created.

Navigate to “C:\c2m\ouaf\C2M2800\splapp\iws” and update below file

iws-build-WLS.xml

  <property name="web.admin.url"         value="t3://localhost:7001" />

Navigate to below file and do the highlighted updates for Heap size

iws-build-common.xml

<target name="generate" depends="clean">     <echo message="Running IWS generator. Please wait..." />     <property name="logprop" value="${gen.home.dir}/config/log4j2.properties" />     <echo file="${logprop}" append="false" message="status=error${nl}" />     <echo file="${logprop}" append="true" message="name=PropertiesConfig${nl}" />     <echo file="${logprop}" append="true" message="appender.A1.type=Console${nl}" />     <echo file="${logprop}" append="true" message="appender.A1.name=A1${nl}" /> <echo file="${logprop}" append="true" message="appender.A1.layout.type=PatternLayout${nl}" /> <echo file="${logprop}" append="true" message="appender.A1.layout.pattern=%X{userId} - %X{transactionId} %d [%t] %-5p (%c{3}) %m%n${nl}" />     <java classname="com.oracle.ouaf.ws.tools.artifactgen.InboundWebserviceGenerator" fork="true" failonerror="true">       <jvmarg value="-Xmx2048m" />       <jvmarg value="-Xms2048m" />

splenviron.cmd -e <ENV NAME>

Execute the following command in %SPLEBASE%\bin. Make sure the application

server is up and running.

iwsdeploy.cmd

Command should run successfully without any errors.

C:\c2m\ouaf\C2M2900\bin>splenviron.cmd -e C2M2900 Version ................ (OUAFVERSION) : 4.5.0.0.0 Database Type ............... (OUAFDB) : oracle ORACLE_SID ............. (ORACLE_SID) : NLS_LANG ................. (NLS_LANG) : AMERICAN_AMERICA.AL32UTF8 Environment Name ....... (SPLENVIRON) : C2M2900 Environment Code Directory (SPLEBASE) : C:\c2m\ouaf\C2M2900 App Output Dir - Logs ... (SPLOUTPUT) : C:\c2m\ouaf\sploutput\C2M2900 C:\c2m\ouaf\C2M2900>cd bin C:\c2m\ouaf\C2M2900\bin>iwsdeploy.cmd

Next login to weblogic admin and go to deployments, you should see Webservice.ear deployed and Active.

Testing Webservice with SOAPUI.

Refer below steps for testing webservice is working after deployment

Open below OOB webservice and open its wsdl

https://localhost:6501/ouaf/webservices/D1-DeviceEventSeeder?WSDL

Open SOAP UI, open new SOAP project. Copy the WSDL URL here.

Sample xml below for reference

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:d1="http://ouaf.oracle.com/webservices/d1/D1-DeviceEventSeeder">    <soapenv:Header/>    <soapenv:Body>       <d1:D1-DeviceEventSeeder>          <d1:externalSenderId>SENSUS</d1:externalSenderId>          <d1:deviceEventType>DEVICELOWBATTERY</d1:deviceEventType>          <d1:eventDateTime>2020-05-29T10:20:15</d1:eventDateTime>          <d1:deviceId>272059640649</d1:deviceId>       </d1:D1-DeviceEventSeeder>    </soapenv:Body> </soapenv:Envelope>

Update the username and password in the request properties. Set WSS-Password Type to ‘PasswordText’ and set WSS TimeToLive to ‘72’

Now run the request, if the webservice deployment is proper, you should see a successful response as seen below.