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:

• Creating Production Versions of the Manifest File and Deployment Plan

• Using the Java JAR Utility to Package Your Shared Library

• Deploying the Shared Library .war

• Redeploying Billing Care to Use Your Shared Library

Before running the jar command, create production versions of the manifest file and deployment plan.

To create production manifest and deployment plan files:

1. 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.

2. Create a copy of the MANIFEST.MF file in the myproject/build/web directory in the myproject/web/META-INF directory named manfiest.txt.

3. Open the manifest.txt file in an editor.

4. 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.

5. Save and close the manifest.txt file.

6. Copy the edited manifest.txt file to the myproject/build/web directory.

7. 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.

8. 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

9. 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 that can be deployed in the Oracle WebLogic Server Administration Console.

For more information on the Java JAR utility, see https://docs.oracle.com/en/java/javase/21/docs/specs/man/jar.html.

To create your BillingCareCustomizations.war using the jar utility:

1. 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.

2. Verify that the manifest.txt file is in the directory.

3. Run the following JAR command to package the manifest.txt file and the subfolders contained in your myproject/web directory into a .war file:

   jar cfm BillingCareCustomizations.war manifest.txt css custom js lib resources WEB-INF

4. 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:

1. Log in to WebLogic Server Remote Console.

2. Click Monitoring Tree, then Deployments, and then Application Management.

   A page with a list of installed Java EE applications and standalone application modules appears.

3. Select the BillingCare deployment.

4. Click Stop and then Force Stop Now to stop Billing Care.

5. Click Edit tree, then Deployments, and then Libraries.

6. Click +New.

7. Enter the Name using the same string used in the Custom-LibraryName element in the deployment plan and the Extension-Name parameter in the MANIFEST.MF file you previously created.

   For example, the string in the sample files provided is:

   BillingCareCustomizations

8. In Targets, select AdminServer and move it to the Chosen section.

9. In Source field, click the upload option and upload the BillingCareCustomization.war file.

10. Click +Create.

11. Once the changes are applied, go to the shopping cart, and then click Commit Changes.

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:

1. Log in to WebLogic Server Remote Console.

2. Click Monitoring Tree, then Deployments, and then Application Management.

   A page with a list of installed Java EE applications and standalone application modules appears.

3. In the table, select BillingCare.

4. Click Update/Redeploy and do one of the following:

   • If your updated deployment plan is located on the server containing WebLogic Server, select Update Deployment Plan on Server and enter the location of the file in the Plan Path field.

   • If your updated deployment plan is located on your local machine, select Update Deployment Plan on Local Machine and click Choose File
     
     to browse to the file or enter the file name in the Plan field.

5. Enter (or browse to) the location of your production deployment plan, prodplan.xml, and select the new deployment plan.

6. Click Done.

7. Select BillingCare, then click Start, and then select Servicing all requests.

8. Ensure that BillingCare is set to Active.