Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.1 Part Number E23118-04 |
|
|
PDF · Mobi · ePub |
This chapter discusses how to configure and deploy the Oracle Process Integration Pack for Oracle Utilities Field Work.
This chapter includes the following sections:
The DCW screens prompt you to enter the data required for successful configuration of the Utilities Field Work PIP. Enter the details of the Utilities Field Work PIP screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.
All artifacts associated with the PIP infrastructure components deploy to the PIP server. This screen contains the following fields:
Table 35-1 PIP Server Details Screen Fields
Field | Description |
---|---|
Admin Host Name |
Specifies where the admin server resides. This can be a remote server or the same system where the AIA Pre-Built Integrations Installer is launched. Example: The Admin Host Name is _________________________________ |
Admin Port |
This is the port number on which the Weblogic Admin server is started. To find this value contact the WebLogic administrator. Example: The Admin Port is _____________________________________ |
Domain Name |
This is WebLogic server domain corresponding to the Admin Server. Example: The Domain Name is _______________________________ |
Admin User |
This value is the WebLogic admin user name. To find this value contact your WebLogic administrator. The Admin User is __________________________________ |
Admin Password |
This value is the WebLogic admin password. To find this value contact your WebLogic administrator. The password is _____________________________________ |
Managed Server |
After you enter the Admin Host Name, Admin Port and Admin User, this field populates with managed servers for the domain. Select the managed server from the list. If you are deploying the PIP to a SOA cluster, you should select the cluster name in this field. The Managed Server is _______________________________ |
Managed Port |
This field is automatically updated after you select the managed server. If you have configured a SOA Cluster, the SOA Cluster port appears in the list. |
Use this screen to enter details related to Oracle Utilities Customer Care and Billing server.
The screen contains the following fields:
Table 35-2 Oracle Utilities Customer Care and Billing Server Details Screens Fields
Field | Description |
---|---|
CCB XAI Service URL |
This value is the location of the Customer Care and Billing web service. Example: CCB XAI Service URL is ________________________ |
CCB Username |
This value is the user ID of the Customer Care and Billing user authorized to invoke web services used in the integration. CCB Username is ________________________ |
CCB User Password |
This value is the password for the user specified above. CCB User Password is ________________________ |
Use this screen to enter details related to Oracle Utilities Work and Asset Management server.
Note:
If your implementation does not include Oracle Utilities Work and Asset Management, you must still enter a "dummy" url for the WAM Service URL field to avoid server errors later on during the installation. For example, enter: http://demo:8888/WAM/services. Also enter any values for the WAM User Name and WAM Password fields.
The screen contains the following fields:
Table 35-3 Oracle Utilities Work and Asset Management Server Details Screen Fields
Field | Description |
---|---|
WAM Service URL |
This value is the location of the Work and Asset Management web service. Example: WAM Service URL is ___________________________ |
WAM Username |
This value is the user ID of the Work and Asset Management user authorized to invoke web services used in the integration. WAM Username is ___________________________ |
WAM User Password |
This value is the password for the user specified above. WAM User Password is ___________________________ |
Use this screen to enter details related to Oracle Utilities Mobile Workforce Management server. Depending on the Oracle Utilities Mobile Workforce Management application version you are using, follow the screen details for that version.
The screen contains the following fields:
Table 35-4 Oracle Utilities Mobile Workforce Management Server Details Screen Fields (Version 1.x)
Field | Description |
---|---|
MWM Service URL |
This value is the location of the Mobile Workforce Management web service. Example: MWM Service URL is _____________________________ |
MWM Username |
This value is the user ID of the Mobile Workforce Management user authorized to invoke web services used in the integration MWM Username is ___________________________ |
MWM User Password |
This value is the password for the user specified above. MWM User Password is ________________________ |
MWM Appointment Booking Service URL |
This value is the location of the Mobile Workforce Management Appointments plug-in. Example: MWM Appoint Booking Service URL is ___________________ |
MWM Appointment Booking Username |
This value is the user ID of the MWM user authorized to invoke appointment service used in the integration MWM Appoint Booking Username is ____________________ |
MWM Appointment Booking Password |
This value is the password for the user specified above MWM Appoint Booking Password is _____________________ |
Note:
MWM User Name and Password for both server and appointment booking are not used in the 1.x version, but are reserved for future use.
Table 35-5 Oracle Utilities Mobile Workforce Management Server Details Screen Fields (Version 2.x)
Field | Description |
---|---|
MWM Service URL |
This value is the location of the Mobile Workforce Management web service. Example: MWM Service URL is _____________________________ |
MWM Username |
This value is the user ID of the Mobile Workforce Management user authorized to invoke web services used in the integration MWM Username is ___________________________ |
MWM User Password |
This value is the password for the user specified above. MWM User Password is ________________________ |
MWM Appointment Booking Service URL |
Leave option blank. |
MWM Appointment Booking Username |
Leave option blank. |
MWM Appointment Booking Password |
Leave option blank. |
Note:
MWM Appointment Booking URL, MWM Appointment Booking User Name and MWM Appointment Booking Password are not valid in 2.x version. Leave these blank.
This section discusses the PIP configuration and deployment process. There are two steps:
Configure your PIP using the deployment DCW.
Deploy the PIP to the Fusion Middleware server.
The screens that appear prompt you to enter the data that is required for successful configuration of the Utilities Field Work PIP. Keep the completed worksheets of the Utilities Field Work PIP screens ready before you launch the DCW.
Note:
If you are harvesting content to OER, perform the first three steps. Else start from step 4.
To configure the Utilities Field Work PIP:
Navigate to /slot/emsxxxx/oracle/Middleware/user_projects/domains/soa_domain/bin/ and open setDomainEnv.sh for Linux based systems and setDomainEnv.bat for Microsoft Windows.
Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".
Restart the server.
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh
for Linux based systems and aiaenv.bat
for Microsoft Windows to configure the environment.
Navigate to <AIA_HOME>/bin and run the command ./aiaconfig.sh
for Linux based systems and aiaconfig.bat
for Microsoft Windows.
This launches the AIA DCW.
Click Next.
Select the Utilities Field Work PIP
Click Next.
To specify PIP Server details:
Enter information related to your PIP server in the PIP Server Details screen.
Click Next.
To specify Utilities Mobile Workforce Management Services details:
Enter information about your Utilities Mobile Workforce Management Services installation in the Utilities Mobile Workforce Management Services Details screen.
Click Next.
To specify Utilities Work and Asset Management Services details:
Enter information about your Utilities Work and Asset Management Services installation in the Utilities Work and Asset Management Services Screen Details screen.
Click Next.
To specify Utilities Customer Care and Billing Services details:
Enter information about your Utilities Customer Care and Billing Services installation in the Utilities Customer Care and Billing Services Details screen.
Click Next.
Review the configuration information on the Configuration Summary screen.
Note:
If you want to make changes to the configuration, use the navigation pane on the left and select the screen you want to edit.
You can create a response file based on the input provided in the DCW and use it in future when you want to deploy the PIP. You can configure using the steps described in Section 35.2.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.
Click Configure to accept the configuration.
The system displays progress of the configuration in the Configuration Progress screen.
The system displays any warnings or errors as necessary. You can review the configuration log for additional details. The configuration log location is displayed in Configuration Progress screen.
When the configuration process completes without errors, the AIA DCW displays the Configuration Complete screen.
Click Finish to close the DCW.
To configure using the response file:
Open the response file.
When you create a response file through OUI, passwords get stored as <SECURE>.
Replace the password fields with actual passwords in the response file.
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh
for Linux based systems and aiaenv.bat
for Microsoft Windows to configure the environment.
Navigate to <AIA_HOME>/bin and run the command ./aiaconfig.sh <Response File Location and Name>
for Linux based systems and aiaconfig.bat <Response File Location and Name>
for Microsoft Windows.
To deploy the PIP to Fusion Middleware server:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh
for Linux based systems and aiaenv.bat
for Microsoft Windows to configure the environment.
Run the command for your platform.
Note:
When you copy and paste the command in the command line, ensure that there is space between .xml
and -
. Ensure that there is space between these two when you run undeployment command too.
Table 35-6 Deployment Commands for the Utilities Field Work PIP
Platform | Deployment Command |
---|---|
Linux Solaris SPARC IBM AIX Based Systems. HP-UX |
ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>/pips/FieldWork/DeploymentPlans/FieldWorkDP.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml -DSupplementaryDeploymentPlan=<AIA_HOME>/pips/FieldWork/DeploymentPlans/FieldWorkSupplementaryDP.xml -DDeploymentPolicyFile=<AIA_HOME>/pips/FieldWork/DeploymentPlans/FieldWorkConditionalPolicy.xml -l <AIA_HOME>/pips/FieldWork/DeploymentPlans/FieldWork.log |
Microsoft Windows |
ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>\pips\FieldWork\DeploymentPlans\FieldWorkDP.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<aia_instance>\config\AIAInstallProperties.xml -DSupplementaryDeploymentPlan=<AIA_HOME>\pips\FieldWork\DeploymentPlans\FieldWorkSupplementaryDP.xml -DDeploymentPolicyFile=<AIA_HOME>\pips\FieldWork\DeploymentPlans\FieldWorkConditionalPolicy.xml -l <AIA_HOME>\pips\FieldWork\DeploymentPlans\FieldWorkDP.log |
Note:
In Windows 2008, 2008 R2 and Vista, run the command prompt as an administrator (elevated mode). If the command prompt is invoked in normal mode, the PIPs are not displayed.
Review the log file in the location specified in the command to verify successful deployment.
Oracle AIA ships artifacts in AIA Lifecycle Workbench which can be used in your integrations. These artifacts are created using FMW technologies such as BPEL and Mediator and are natively supported by AIA Foundation Pack tools such as Project Lifecycle Workbench, Harvester, Deployment Generator, AIA Deployment Driver (ADD). These are called native artifacts and they include SOA artifact types such as composites, DataSources, DVM, xRef, and so on. These artifacts can be modified or new natively supported artifacts can be added using the AIA Lifecyle Workbench and a BOM.xml file can be generated.
AIA PIP development teams, most often, also require deployment of artifact types that are beyond what is supported by the Project Lifecycle Workbench and AIA Harvester. For instance, integration may require artifacts such as, Java applications, Shell Scripts, ANT based build scripts which constitute part of integration landscape in addition to the artifacts that are delivered by AIA. AIA also supports deployment of these supplementary artifacts. However, you must modify and add new non native artifacts outside AIA Lifecycle Workbench.
For more information on deploying artifacts, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".
To verify the Utilities Field Work PIP deployment:
Open the log files from the following location and look for warnings and error messages:
For Linux, Solaris SPARC, HP-UX and IBM AIX Based Systems: Review the install log located at <AIA_HOME>/aia_instances/<instance name>/logs to verify that the PIP is successfully installed.
For Microsoft Windows: Review the install log located at <AIA_HOME>\aia_instances\<instance name>\logs to verify that the PIP is successfully installed.
Confirm that the Utilities Field Work PIP components were successfully installed.
Navigate to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).
Log in with the server admin user name. For access details, contact the system administrator.
Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:
Note:
Oracle Utilities Mobile Workforce Management v1.x and v2.x have a few composites in common and a few that are unique to each version.
Common Composites
CCBGetMeterDataProvService
CreateCustomerInteractionOUCCBUtilitiesProvABCSImpl
CreateCustomerInteractionOUWAMUtilitiesReqABCSImpl
CreateInvoiceOUCCBUtilitiesJMSConsumer
CreateInvoiceOUCCBUtilitiesJMSProducer
CreateInvoiceOUCCBUtilitiesProvABCSImpl
CreateInvoiceOUWAMUtilitiesReqABCSImpl
CreateTimeSheetOUWAMUtilitiesProvABCSImpl
GetWOLineApptWinAvailOUCCBUtilitiesReqABCSImpl
ProcessWorkOrderCompleteOUWAMUtilitiesReqABCSImpl
ProcessWorkOrderCreateOUWAMUtilitiesReqABCSImpl
ProcessWorkOrderOUCCBUtilitiesJMSConsumer
ProcessWorkOrderOUCCBUtilitiesJMSProducer
ProcessWorkOrderOUCCBUtilitiesProvABCSImpl
ProcessWorkOrderOUCCBUtilitiesReqABCSImpl
ProcessWorkOrderOUMWMUtilitiesJMSProducer
ProcessWorkOrderOUWAMUtilitiesJMSConsumer
ProcessWorkOrderOUWAMUtilitiesJMSProducer
ProcessWorkOrderOUWAMUtilitiesProvABCSImpl
ProcessWorkOrderResponseOUCCBUtilitiesProvABCSImpl
ProcessWorkOrderResponseOUWAMUtilitiesProvABCSImp
ProcessWorkOrderUpdateOUWAMUtilitiesReqABCSImpl
TimeSheetEBS
UtilitiesCustomerInteractionEBS
UtilitiesCustomerInteractionResponseEBS
UtilitiesInstalledProductEBSV2
UtilitiesInvoiceEBSV2
UtilitiesWorkOrderEBS
UtilitiesWorkOrderResponseEBS
ValidateInstalledProductOUCCBUtilitiesProvABCSImpl
ValidateInstalledProductOUWAMUtilitiesReqABCSImpl
WAMGetMeterDataReqService
MWM Version 1.x Composites
CreateTimeSheetOUMWMUtilityReqABCSImpl
GetWOLineApptWinAvailOUMWMUtilitiesProvABCSImpl
ProcessWorkOrderCompleteOUMWMUtilitiesReqABCSImpl
ProcessWorkOrderCreateOUMWMUtilitiesReqABCSImpl
ProcessWorkOrderOUMWMUtilitiesJMSConsumer
ProcessWorkOrderOUMWMUtilitiesJMSProducer
ProcessWorkOrderOUMWMUtilitiesProvABCSImpl
ProcessWorkOrderResponseOUMWMUtilitiesProvABCSImpl
ProcessWorkOrderResponseOUMWMUtilitiesReqABCSImpl
ProcessWorkOrderStatusOUMWMUtilitiesReqABCSImpl
ValidateInstalledProductOUMWMUtilitiesReqABCSImpl
MWM Version 2.x Composites
GetWOLineApptWinAvailOUMWMUtilitiesProvABCSImplV2
ProcessWorkOrderCompleteOUMWMUtilitiesReqABCSImplV2
ProcessWorkOrderCreateOUMWMUtilitiesReqABCSImplV2
ProcessWorkOrderCreateOUMWMUtilitiesReqABCSImplV2
ProcessWorkOrderOUMWMUtilitiesJMSConsumerV2
ProcessWorkOrderOUMWMUtilitiesJMSProducer
ProcessWorkOrderOUMWMUtilitiesProvABCSImplV2
ProcessWorkOrderResponseOUMWMUtilitiesProvABCSImplV2
ProcessWorkOrderStatusOUMWMUtilitiesReqABCSImplV2
ValidateInstalledProductOUMWMUtilitiesReqABCSImplV2
Navigate to Farm_soa_domain, Weblogic Domain, right click <domain name>, Security, Credentials, oracle.wsm.security and verify the following items:
OU_CCB_01
OU_MWM_01
OU_WAM_01
For PIP implementation, see Oracle Process Integration Pack for Oracle Utilities Field Work Implementation Guide.
To undeploy the PIP from Fusion Middleware Server:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh
for Linux based systems and aiaenv.bat
for Microsoft Windows to configure the environment.
Run the command for your platform.
Table 35-7 Undeployment Command for the Utilities Field Work PIP
Platform | Undeployment Command |
---|---|
Linux Solaris SPARC IBM AIX Based Systems. HP-UX |
ant Uninstall -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<AIA_Instance_name>/config/AIAInstallProperties.xml -DDeploymentPlan=<AIA_HOME>/pips/FieldWork/DeploymentPlans/FieldWorkUndeployDP.xml -l <AIA_HOME>/pips/FieldWork/DeploymentPlans/FieldWorkUndeployDP.log |
Microsoft Windows |
ant Uninstall -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<AIA_Instance_name>\config\AIAInstallProperties.xml -DDeploymentPlan=<AIA_HOME>\pips\FieldWork\DeploymentPlans\FieldWorkUndeployDP.xml -l <AIA_HOME>\pips\FieldWork\DeploymentPlans\FieldWorkUndeployDP.log |
Restart the SOA server.
Uninstall the PIP following the instructions in Chapter 37, "Uninstalling Oracle AIA".