February 23, 2019
Hot Topics:

Propagating Weblogic 8.x Portals

  • September 28, 2006
  • By Scott Nelson
  • Send Email »
  • More Articles »

The import process also is very simple, and has step-by-step prompts. With lots and lots and lots of warnings. Again, I'll cover the short path here. And, again, read the docs at the link given earlier if you have concerns. For me, the longest part was reading the warning labels.

With the EAR and the propagation application deployed on the target server, open the propagation application the same way as before, only with your new URL (http://mynewhost:7001/propagation), and do the following:

  1. Click Import an Inventory.
  2. Log in.
  3. Click the Specify the file radio button.
  4. Enter the full path to the zip file you created in the export process, including the file name; in other words, I:DeveloperDotComPropagating BEA Portalsinventory.zip.
  5. Click Continue. If you see The input file was not found. The application tree was loaded instead., check your path.
  6. Click Continue.
  7. Click Preview Changes.
  8. Click the checkbox; then click Continue.
  9. Click Deployment Complete.
  10. Click Continue.
  11. Click Continue.
  12. Scroll to the bottom and Click Continue.
    1. On the Review Manual Changes page, there probably will be a list. This is why I recommend a dry run. You may not need to do anything with this list, so click Continue the first time and out and note during your testing if anything needs to be dealt with. Note that users are not exported, and this is addressed later in this article.
  13. Click Continue.
  14. Click Commit the Inventory.

The next screen has you export what you have just imported. Again, for the dry run, I wouldn't bother. For the real deal, though, it is a good best practice.

You now can go to your new portal URL and review how well things turned out for you. You will need to add your users to do much real testing. If you have an authentication method that relies on an external application, you will need to test and possibly reconfigure it for your new domain. If you use the internal LDAP, you should create your users before testing.

Although not considered a best practice by BEA, it is a common practice to have the same users in Staging as Production, so I feel obligated to list the steps here to propagate these as well.

In your original domain, go to the Weblogic Server Console, navigate to your security realm, click on the Migration tab, and then the Export tab.

Click here for a larger image.

I prefer to enter a path ending with LDAP to make it easy to find. Click export and then check the path you entered to make sure you have the five expected files.

If necessary, copy the folder you exported to to somewhere where your new deployment can access it.

Now, go to the Import tab in your new domain and enter the location to import from.

Despite the dire warning in the propagation screen, you should have most of your assets up and running, except some as noted in the Manual screen.

Now, go have dinner at home rather than the pizza.

About the Author

Scott Nelson is a Principal professional services consultant specializing in BEA portal products. His blog is located at http://fuq.fywservices.com/. All opinions and recommendations in this article are those of the author and not official BEA information except what is noted in the links to BEA-owned sites.

Page 2 of 2

Comment and Contribute


(Maximum characters: 1200). You have characters left.



Enterprise Development Update

Don't miss an article. Subscribe to our newsletter below.

Thanks for your registration, follow us on our social networks to keep up-to-date