This chapter provides an overview on deploying Oracle Communications Billing Care customizations to production Billing Care domains.
After testing and verifying your Billing Care customizations, create a packaged archive (.war) file of your exploded archive shared library to deploy in your production Billing Care domain. Using a .war containing your customizations enables you to quickly deploy your customizations to multiple Billing Care instances.
Deploying customizations to production environments requires that you complete the following procedures:
Before running the jar command, create production versions of the manifest file and deployment plan.
To create production manifest and deployment plan files:
In a terminal session, change directory to the myproject/web/META-INF directory, where myproject is the NetBeans IDE project directory containing your Billing Care customizations.
Create a copy of the MANIFEST.MF file in the myproject/build/web directory in the myproject/web/META-INF directory named manfiest.txt.
Open the manifest.txt file in an editor.
Edit the values of the Custom-LibraryName and the Extension-Name parameters to a string for your production shared library. For example:
BillingCareCustomizations
See "Creating a Manifest for your Shared Library" for more information on creating a manifest file for your shared library.
Save and close the manifest.txt file.
Copy the edited manifest.txt file to the myproject/build/web directory.
Create a copy of the deployment plan you created for your exploded archive shared library deployment in "Creating a New Deployment Plan for Billing Care with your Shared Library" named prodplan.xml. Use this deployment plan for your production Billing Care deployments.
Edit the Custom-LibraryName element in prodplan.xml using the same string you provided in step 4.
Note:
Use the same string in the Custom-LibraryName element in your deployment plan as the Extension-Name parameter in the MANIFEST.MF file you previously created. For example, the string in this procedure is:BillingCareCustomizations
Save and close the prodplan.xml file.
The jar command packages all of the required contents of your exploded archive shared library into a .war file deployable in the Oracle WebLogic Server Administration Console.
For more information on the Java jar utility see:
http://docs.oracle.com/javase/7/docs/technotes/tools/windows/jar.html
To create your BillingCareCustomizations.war using the jar utility:
In a terminal session, change directory to the myproject/build/web directory, where myproject is the NetBeans IDE project directory containing your Billing Care customizations.
Verify that the manifest.txt file from step 2 is in the directory.
Execute the following jar command to package the manifest.txt file and the subfolders contained in of your myproject/web directory into a .war file:
jar cfm BillingCareCustomizations.war manifest.txt css custom js lib resources WEB-INF
Verify that the BillingCareCustomizations.war is created.
After creating your BillingCareCustomization.war and production deployment plan, deploy the .war in your Billing Care domain.
To deploy your shared library in your Billing Care domain:
In your browser, navigate to the Administration Console of your Billing Care domain.
Log in using administrative credentials for the Billing Care domain.
In Domain Structure, click Deployments.
Select the BillingCare deployment and click Stop, then Force Stop Now to stop Billing Care.
In the Control tab, click Install in the Deployments table.
In the Path: field, enter (or browse to) the location of the BillingCareCustomization.war.
Confirm that the option for BillingCareCustomization.war is selected.
Click Next.
In the Choose targeting style screen, select Install this deployment as a library.
Click Next.
In the Optional Settings screen, enter the Name using the same string used in the Custom-LibraryName element in your deployment plan and the Extension-Name parameter in the MANIFEST.MF file you previously created. For example, the string used in this chapter is:
BillingCareCustomizations
Click Next.
In the Review your choices and click Finish screen, click Finish.
Confirm in the Deployments screen that your shared library is deployed in your Billing Care domain and is in an Active state.
After deploying the BillingCareCustomizations.war, redeploy Billing Care using the production deployment plan. Redeploying Billing Care using the production plan restarts and configures Billing Care to use the .war shared library you previously deployed.
To redeploy Billing Care:
In your browser, navigate to the Administration Console of your Billing Care domain.
Log in using administrative credentials for the Billing Care domain.
In Domain Structure, click Deployments.
In the Control tab, select BillingCare in the Deployments table.
Click Update.
In the Update Application Assistant screen, select Redeploy this application using the following deployment files:.
For the Deployment plan path:, click Change Path.
Enter (or browse to) the location where your production prodplan.xml deployment plan is and select the production deployment plan.
Click Next.
In the Review your choices screen, click Finish.
Confirm in the Deployments screen that Billing Care redeploys successfully and is in an Active state.