The Content Rave

Configuring the iPlanet as web tier for Oracle WebCenter Content (UCM)

2012-05-31T11:00:00.000-07:00

If you are looking for configure the iPlanet as Web server/proxy to use with the Oracle WebCenter Content, you probably won’t found an specific documentation for that or will found some old complex notes related to the old 10gR3.

This post will help you out with few simple steps.

That’s the diagram of the test scenario, considering that you will deploy in production in an cluster environment.

First you need the software, for our scenario you will need:

- Oracle iPlanet Web Server 7.0.15+ (Installed)
- Oracle WebCenter Content 11gR1 PS5 (Installed)
- Oracle WebLogic Web Server Plugins 11g (1.1)
- Supported JDK (Using Oracle Java JDK 7u4 for the test)
- Certified Client OS
- Certified Server OS (Using Oracle Solaris 11 for the test)
- Certified Database (Using Oracle Database 11.2.0.3 for the test)

Then the configuration:

- Download the latest plugin:
http://www.oracle.com/technetwork/middleware/ias/downloads/wls-plugins-096117.html

- Extract the WLSPlugin11g-iPlanet7.0 in some folder, like <iPlanet_Home>/plugins/wls11

- Include the plugin reference to the magnus.conf:

If Unix (Solaris or Linux), include the line:

Init fn="load-modules" shlib="/apps/oracle/WebServer7/plugins/wls11/lib/mod_wl.so"

If Windows, Include the line:

Init fn="load-modules" shlib="D:\\oracle\\WebServer7\\plugins\\wls11\\lib\\mod_wl.dll"

- Include the proxy reference to the obj.conf of each instance:

<Object name="weblogic" ppath="*/cs/*">Service fn="wl-proxy" WebLogicCluster="wcc-node1:16201,wcc-node2:16202, wcc-node3:16203" </Object> <Object name="weblogic" ppath="*/_dav/*">Service fn="wl-proxy" WebLogicCluster="wcc-node1:16201,wcc-node2:16202, wcc-node3:16203" </Object> <Object name="weblogic" ppath="*/_ocsh/*">Service fn="wl-proxy" WebLogicCluster="wcc-node1:16201,wcc-node2:16202, wcc-node3:16203" </Object> <Object name="weblogic" ppath="*/adfAuthentication/*">Service fn="wl-proxy" WebLogicCluster="wcc-node1:16201,wcc-node2:16202, wcc-node3:16203" </Object>

If you are using an single node setup, change the Service fn=…. line to something like:

Service fn="wl-proxy" WebLogicHost=<wcc-server> WebLogicPort=16200

With these configurations, your should have the WebCenter Content UI working with the iPlanet, test it. [http://<web-server>/cs/]

With the UI working, the last step is to configure the WebDav:

- Go to the iPlanet Admin Console (usually https://<web-server>:8989)

- Go to Configurations >> [instance] >> Virtual Servers >> [Virtual Server] >> WebDAV:

- Click New

- Populate the URI with /cs/idcplg/webdav:

- Select “Anyone (No Authentication)”, the wc Content will take care of the security:

This will allow you to use the WebDav feature and the Desktop Integration Suite, including double-byte characters.

Another iPlanet tunes could be done, I can cover in the next post related to the iPlanet.

Cross-posted on the WebCenter A-Team Blog

- Using a Web Proxy Server with WebCenter Family

Partitioned Repository for WebCenter Content using Oracle Database 11g

2012-04-13T19:03:00.001-07:00

One of the biggest challenges for content management solutions is related to the storage management due the high volumes of the unstoppable growing of information.
Even if you have storage appliances and a lot of terabytes, thinks like backup, compression, deduplication, storage relocation, encryption, availability could be a nightmare.
One standard option that you have with the Oracle WebCenter Content is to store data to the database. And the Oracle Database allows you leverage features like compression, deduplication, encryption and seamless backup.
But with a huge volume, the challenge is passed to the DBA to keep the WebCenter Content Database up and running.
One solution is the use of DB partitions for your content repository, but what are the implications of this? Can I fit this with my business requirements?
Well, yes. It’s up to you how you will manage that, you just need a good plan. During you “storage brainstorm plan” take in your mind what you need, such as storage petabytes of documents? You need everything on-line? There’s a way to logically separate the “good content” from the “legacy content”?
The first thing that comes to my mind is to use the creation date of the document, but you need to remember that this document could receive a lot of revisions and maybe you can consider the revision creation date. Your plan can have also complex rules like per Document Type or per a custom metadata like department or an hybrid per date, per DocType and an specific virtual folder.
Extrapolation the use, you can have your repository distributed in different servers, different disks, different disk types (Such as ssds, sas, sata, tape,…), separated accordingly your business requirements, separating the “hot” content from the legacy and easily matching your compliance requirements.
If you think to use by revision, the simple way is to consider the dId, that is the sequential unique id for every content created using the WebCenter Content or the dLastModified that is the date field of the FileStorage table that contains the date of inclusion of the content to the DB Table using SecureFiles.
Using the scenario of partitioned repository using an hierarchical separation by date, we will transform the FileStorage table in an partitioned table using “Partition by Range” of the dLastModified column (You can use the dId or a join with other tables for other metadata such as dDocType, Security, etc…).
The test scenario bellow covers:

Previous existent data on the JDBC Storage to be migrated to the new partitioned JDBC Storage
Partition by Date
Automatically generation of new partitions based on a pre-defined interval (Available only with Oracle Database 11g+)
Deduplication and Compression for legacy data
Oracle WebCenter Content 11g PS5 (Could present some customizations that do not affect the test scenario)

For the test case you need some data stored using JDBC Storage to be the “legacy” data. If you do not have done before, just create an Storage rule pointed to the JDBC Storage:

FileStorage Providers

Enable the metadata StorageRule in the UI and upload some documents using this rule.
For this test case you can run using the schema owner or an dba user. We will use the schema owner TESTS_OCS.
I can’t forgot to tell that this is just a test and you should do a proper backup of your environment.
When you use the schema owner, you need some privileges, using the dba user grant the privileges needed:

REM Grant privileges required for online redefinition.
GRANT EXECUTE ON DBMS_REDEFINITION TO TESTS_OCS;
GRANT ALTER ANY TABLE TO TESTS_OCS;
GRANT DROP ANY TABLE TO TESTS_OCS;
GRANT LOCK ANY TABLE TO TESTS_OCS;
GRANT CREATE ANY TABLE TO TESTS_OCS;
GRANT SELECT ANY TABLE TO TESTS_OCS;
REM Privileges required to perform cloning of dependent objects.
GRANT CREATE ANY TRIGGER TO TESTS_OCS;
GRANT CREATE ANY INDEX TO TESTS_OCS;

In our test scenario we will separate the content as Legacy, Day1, Day2, Day3 and Future. This last one will partitioned automatically using 3 tablespaces in a round robin mode. In a real scenario the partition rule could be per month, per year or any rule that you choose.
Table spaces for the test scenario:

CREATE TABLESPACE TESTS_OCS_PART_LEGACY DATAFILE 'tests_ocs_part_legacy.dat' SIZE 500K AUTOEXTEND ON NEXT 500K MAXSIZE UNLIMITED;
CREATE TABLESPACE TESTS_OCS_PART_DAY1 DATAFILE 'tests_ocs_part_day1.dat' SIZE 500K AUTOEXTEND ON NEXT 500K MAXSIZE UNLIMITED;
CREATE TABLESPACE TESTS_OCS_PART_DAY2 DATAFILE 'tests_ocs_part_day2.dat' SIZE 500K AUTOEXTEND ON NEXT 500K MAXSIZE UNLIMITED;
CREATE TABLESPACE TESTS_OCS_PART_DAY3 DATAFILE 'tests_ocs_part_day3.dat' SIZE 500K AUTOEXTEND ON NEXT 500K MAXSIZE UNLIMITED;
CREATE TABLESPACE TESTS_OCS_PART_ROUND_ROBIN_A 'tests_ocs_part_round_robin_a.dat' DATAFILE SIZE 500K AUTOEXTEND ON NEXT 500K MAXSIZE UNLIMITED;
CREATE TABLESPACE TESTS_OCS_PART_ROUND_ROBIN_B 'tests_ocs_part_round_robin_b.dat' DATAFILE SIZE 500K AUTOEXTEND ON NEXT 500K MAXSIZE UNLIMITED;
CREATE TABLESPACE TESTS_OCS_PART_ROUND_ROBIN_C 'tests_ocs_part_round_robin_c.dat' DATAFILE SIZE 500K AUTOEXTEND ON NEXT 500K MAXSIZE UNLIMITED;

Before start, gather optimizer statistics on the actual FileStorage table:

EXEC DBMS_STATS.GATHER_TABLE_STATS(USER, 'FileStorage', cascade => TRUE);

Now check if is possible execute the redefinition process:

EXEC DBMS_REDEFINITION.CAN_REDEF_TABLE('TESTS_OCS', 'FileStorage',DBMS_REDEFINITION.CONS_USE_PK);

If no errors messages, you are good to go.

Create a Partitioned Interim FileStorage table.

You need to create a new table with the partition information to act as an interim table:

CREATE TABLE FILESTORAGE_Part
  (
    DID          NUMBER(*,0) NOT NULL ENABLE,
    DRENDITIONID VARCHAR2(30 CHAR) NOT NULL ENABLE,
    DLASTMODIFIED TIMESTAMP (6),
    DFILESIZE  NUMBER(*,0),
    DISDELETED VARCHAR2(1 CHAR),
    BFILEDATA BLOB
  )
  
  LOB (BFILEDATA) STORE AS SECUREFILE
    (
        ENABLE STORAGE IN ROW
        NOCACHE LOGGING
        KEEP_DUPLICATES
        NOCOMPRESS
    ) 
  PARTITION BY RANGE (DLASTMODIFIED) 
  INTERVAL (NUMTODSINTERVAL(1,'DAY'))
  STORE IN (TESTS_OCS_PART_ROUND_ROBIN_A, TESTS_OCS_PART_ROUND_ROBIN_B, TESTS_OCS_PART_ROUND_ROBIN_C)
  (
          PARTITION FILESTORAGE_PART_LEGACY VALUES LESS THAN (TO_DATE('05-APR-2012 12.00.00 AM', 'DD-MON-YYYY HH.MI.SS AM')) 
            TABLESPACE TESTS_OCS_PART_LEGACY
            LOB (BFILEDATA) STORE AS SECUREFILE 
              ( TABLESPACE TESTS_OCS_PART_LEGACY 
                RETENTION NONE 
                DEDUPLICATE 
                COMPRESS HIGH
              ),
          PARTITION FILESTORAGE_PART_DAY1 VALUES LESS THAN (TO_DATE('06-APR-2012 07.25.00 PM', 'DD-MON-YYYY HH.MI.SS AM')) 
            TABLESPACE TESTS_OCS_PART_DAY1 
            LOB (BFILEDATA) STORE AS SECUREFILE 
              ( TABLESPACE TESTS_OCS_PART_DAY1 
                RETENTION AUTO 
                KEEP_DUPLICATES 
                COMPRESS 
              ),
          PARTITION FILESTORAGE_PART_DAY2 VALUES LESS THAN (TO_DATE('06-APR-2012 07.55.00 PM', 'DD-MON-YYYY HH.MI.SS AM')) 
            TABLESPACE TESTS_OCS_PART_DAY2
            LOB (BFILEDATA) STORE AS SECUREFILE 
              ( TABLESPACE TESTS_OCS_PART_DAY2
                RETENTION AUTO 
                KEEP_DUPLICATES 
                NOCOMPRESS 
              ),
          PARTITION FILESTORAGE_PART_DAY3 VALUES LESS THAN (TO_DATE('06-APR-2012 07.58.00 PM', 'DD-MON-YYYY HH.MI.SS AM')) 
            TABLESPACE TESTS_OCS_PART_DAY3
            LOB (BFILEDATA) STORE AS SECUREFILE 
              ( TABLESPACE TESTS_OCS_PART_DAY3 
                RETENTION AUTO 
                KEEP_DUPLICATES 
                NOCOMPRESS 
              )
  );

After the creation you should see your partitions defined.

Note that only the fixed range partitions have been created, none of the interval partition have been created.

Start the redefinition process:

BEGIN
    DBMS_REDEFINITION.START_REDEF_TABLE(
         uname => 'TESTS_OCS'
        ,orig_table => 'FileStorage'
        ,int_table => 'FileStorage_PART'
        ,col_mapping => NULL
        ,options_flag => DBMS_REDEFINITION.CONS_USE_PK
    );
END;

This operation can take some time to complete, depending how many contents that you have and on the size of the table.
Using the DBA user you can check the progress with this command:

SELECT * FROM v$sesstat WHERE sid = 1;

Copy dependent objects:

DECLARE
redefinition_errors PLS_INTEGER := 0;
BEGIN
    DBMS_REDEFINITION.COPY_TABLE_DEPENDENTS(
        uname => 'TESTS_OCS'
        ,orig_table => 'FileStorage'
        ,int_table => 'FileStorage_PART'
        ,copy_indexes => DBMS_REDEFINITION.CONS_ORIG_PARAMS
        ,copy_triggers =>  TRUE
        ,copy_constraints =>  TRUE
        ,copy_privileges =>  TRUE
        ,ignore_errors =>  TRUE
        ,num_errors => redefinition_errors
        ,copy_statistics => FALSE
        ,copy_mvlog => FALSE    
    );
    IF (redefinition_errors > 0) THEN
        DBMS_OUTPUT.PUT_LINE('>>> FileStorage to FileStorage_PART temp copy Errors: ' || TO_CHAR(redefinition_errors));
    END IF;    
    
END;

With the DBA user, verify that there's no errors:

SELECT object_name, base_table_name, ddl_txt FROM DBA_REDEFINITION_ERRORS;

*Note that will show 2 lines related to the constrains, this is expected.

Synchronize the interim table FileStorage_PART:

BEGIN
  DBMS_REDEFINITION.SYNC_INTERIM_TABLE(
    uname      => 'TESTS_OCS',        
    orig_table => 'FileStorage',
    int_table  => 'FileStorage_PART');
END;

Gather statistics on the new table:

EXEC DBMS_STATS.GATHER_TABLE_STATS(USER, 'FileStorage_PART', cascade => TRUE);

Complete the redefinition:

BEGIN
  DBMS_REDEFINITION.FINISH_REDEF_TABLE(
    uname      => 'TESTS_OCS',        
    orig_table => 'FileStorage',
    int_table  => 'FileStorage_PART');
END;

During the execution the FileStorage table is locked in exclusive mode until finish the operation.
After the last command the FileStorage table is partitioned.
If you have contents out of the range partition, you should see the new partitions created automatically, not generating an error if you “forgot” to create all the future ranges. You will see something like:

You now can drop the FileStorage_PART table:

DROP TABLE FileStorage_PART PURGE;

To check the FileStorage table is valid and is partitioned, use the command:

SELECT num_rows,partitioned
FROM   user_tables
WHERE  table_name = 'FILESTORAGE';

You can list the contents of the FileStorage table in a specific partition, per example:

SELECT *
FROM   FileStorage
PARTITION (FILESTORAGE_PART_LEGACY)

Some useful commands that you can use to check the partitions, note that you need to run using a DBA user:

SELECT *
FROM   DBA_TAB_PARTITIONS
WHERE  table_name = 'FILESTORAGE';
 
SELECT *
FROM   DBA_TABLESPACES
WHERE  tablespace_name like 'TESTS_OCS%';

After the redefinition process complete you have a new FileStorage table storing all content that has the Storage rule pointed to the JDBC Storage and partitioned using the rule set during the creation of the temporary interim FileStorage_PART table.
At this point you can test the WebCenter Content downloading the documents (Original and Renditions). Note that the content could be already in the cache area, take a look in the weblayout directory to see if a file with the same id is there, then click on the web rendition of your test file and see if have created the file and you can open, this means that is all working.
The redefinition process can be repeated many times, this allow you test what the better layout, over and over again.
Now some interesting maintenance actions related to the partitions:

Make an tablespace read only.

No issues viewing, the WebCenter Content do not alter the revisions

When try to delete an content that is part of an read only tablespace, an error will occurs and the document will not be deleted

The only way to prevent errors today is creating an custom component that checks the partitions and if you have an document in an “Read Only” repository, execute the deletion process of the metadata and mark the document to be deleted on the next db maintenance, like a new redefinition.

Take an tablespace off-line for archiving purposes or any other reason.

When you try open an document that is included in this tablespace will receive an error that was unable to retrieve the content, but the others online tablespaces are not affected.

Same behavior when deleting documents.

Again, an custom component is the solution. If you have an document “out of range”, the component can show an message that the repository for that document is offline. This can be extended to a option to the user to request to put online again.

Moving some legacy content to an offline repository (table) using the Exchange option to move the content from one partition to a empty nonpartitioned table like FileStorage_LEGACY. Note that this option will remove the registers from the FileStorage and will not be able to open the stored content. You always need to keep in mind the indexes and constrains.

An redefinition separating the original content (vault) from the renditions and separate by date ate the same time. This could be an option for DAM environments that want to have an special place for the renditions and put the original files in a storage with less performance.

The process will be the same, you just need to change the script of the interim table to use composite partitioning. Will be something like:

CREATE TABLE FILESTORAGE_RenditionPart
  (
    DID          NUMBER(*,0) NOT NULL ENABLE,
    DRENDITIONID VARCHAR2(30 CHAR) NOT NULL ENABLE,
    DLASTMODIFIED TIMESTAMP (6),
    DFILESIZE  NUMBER(*,0),
    DISDELETED VARCHAR2(1 CHAR),
    BFILEDATA BLOB
  )
  
  LOB (BFILEDATA) STORE AS SECUREFILE
    (
        ENABLE STORAGE IN ROW
        NOCACHE LOGGING
        KEEP_DUPLICATES
        NOCOMPRESS
    ) 
  PARTITION BY LIST (DRENDITIONID)
  SUBPARTITION  BY RANGE (DLASTMODIFIED) 
  (
  PARTITION Vault VALUES ('primaryFile')
      ( SUBPARTITION FILESTORAGE_VAULT_LEGACY VALUES LESS THAN (TO_DATE('05-APR-2012 12.00.00 AM', 'DD-MON-YYYY HH.MI.SS AM')) LOB (BFILEDATA) STORE AS SECUREFILE 
      , SUBPARTITION FILESTORAGE_VAULT_DAY1 VALUES LESS THAN (TO_DATE('06-APR-2012 07.25.00 PM', 'DD-MON-YYYY HH.MI.SS AM')) LOB (BFILEDATA) STORE AS SECUREFILE 
      , SUBPARTITION FILESTORAGE_VAULT_DAY2 VALUES LESS THAN (TO_DATE('06-APR-2012 07.55.00 PM', 'DD-MON-YYYY HH.MI.SS AM')) LOB (BFILEDATA) STORE AS SECUREFILE        
      , SUBPARTITION FILESTORAGE_VAULT_DAY3 VALUES LESS THAN (TO_DATE('06-APR-2012 07.58.00 PM', 'DD-MON-YYYY HH.MI.SS AM')) LOB (BFILEDATA) STORE AS SECUREFILE  
      , SUBPARTITION FILESTORAGE_VAULT_FUTURE VALUES LESS THAN (MAXVALUE)
      )
 ,PARTITION WebLayout VALUES ('webViewableFile')
      ( SUBPARTITION FILESTORAGE_WEBLAYOUT_LEGACY VALUES LESS THAN (TO_DATE('05-APR-2012 12.00.00 AM', 'DD-MON-YYYY HH.MI.SS AM')) LOB (BFILEDATA) STORE AS SECUREFILE 
      , SUBPARTITION FILESTORAGE_WEBLAYOUT_DAY1 VALUES LESS THAN (TO_DATE('06-APR-2012 07.25.00 PM', 'DD-MON-YYYY HH.MI.SS AM')) LOB (BFILEDATA) STORE AS SECUREFILE 
      , SUBPARTITION FILESTORAGE_WEBLAYOUT_DAY2 VALUES LESS THAN (TO_DATE('06-APR-2012 07.55.00 PM', 'DD-MON-YYYY HH.MI.SS AM')) LOB (BFILEDATA) STORE AS SECUREFILE        
      , SUBPARTITION FILESTORAGE_WEBLAYOUT_DAY3 VALUES LESS THAN (TO_DATE('06-APR-2012 07.58.00 PM', 'DD-MON-YYYY HH.MI.SS AM')) LOB (BFILEDATA) STORE AS SECUREFILE  
      , SUBPARTITION FILESTORAGE_WEBLAYOUT_FUTURE VALUES LESS THAN (MAXVALUE)
      )      
 ,PARTITION Special VALUES ('Special')
      ( SUBPARTITION FILESTORAGE_SPECIAL_LEGACY VALUES LESS THAN (TO_DATE('05-APR-2012 12.00.00 AM', 'DD-MON-YYYY HH.MI.SS AM')) LOB (BFILEDATA) STORE AS SECUREFILE 
      , SUBPARTITION FILESTORAGE_SPECIAL_DAY1 VALUES LESS THAN (TO_DATE('06-APR-2012 07.25.00 PM', 'DD-MON-YYYY HH.MI.SS AM')) LOB (BFILEDATA) STORE AS SECUREFILE 
      , SUBPARTITION FILESTORAGE_SPECIAL_DAY2 VALUES LESS THAN (TO_DATE('06-APR-2012 07.55.00 PM', 'DD-MON-YYYY HH.MI.SS AM')) LOB (BFILEDATA) STORE AS SECUREFILE        
      , SUBPARTITION FILESTORAGE_SPECIAL_DAY3 VALUES LESS THAN (TO_DATE('06-APR-2012 07.58.00 PM', 'DD-MON-YYYY HH.MI.SS AM')) LOB (BFILEDATA) STORE AS SECUREFILE  
      , SUBPARTITION FILESTORAGE_SPECIAL_FUTURE VALUES LESS THAN (MAXVALUE)
      )      
  )ENABLE ROW MOVEMENT;

The next post related to partitioned repository will come with an sample component to handle the possible exceptions when you need to take off line an tablespace/partition or move to another place.

Also, we can include some integration to the Retention Management and Records Management.

Another subject related to partitioning is the ability to create an FileStore Provider pointed to a different database, raising the level of the distributed storage vs. performance.

Let us know if this is important to you or you have an use case not listed, leave a comment.

Cross-posted on the WebCenter A-Team Blog

Using a Web Proxy Server with WebCenter Family

2011-07-31T23:43:00.002-07:00

The use of a Web Tier is always recommended in a production environment, for security, performance and better control and load management, no matter if is a Intranet, internet or extranet environment.

The most common use for the Web Tier with WebCenter is acting as Reverse Proxy to forward all requests to a frontend WebCenter site to the application server (Figure A), but there’s to many ways to do an enterprise deployment with a web tier and many flavors of web servers and load balancing options.

Let’s start with the WebLogic plugin with supported webservers. You can found the standard plugins in your WebLogic instalation dir, that will something like “%WEBLOGIC_HOME%/server/plugin/%OS%/”, but I recommend you to download the latest plugin from Oracle’s OTN or eDelivery websites, you will found the Oracle WebLogic Server Web Server Plugins 1.1 or later. With the version 1.1 you will found plugins for Apache 2.2.x (32-Bits and 64-Bits) and for IIS 6+ and IIS 7+. Always confirm the OS support with the WLS Plugin Support Matrix. If you need support for iPlanet 6+ or 7+, you can use the version 1.0. Any throuble to found the files, try search or create to the Oracle support (Ref.: Doc ID 1111903.1).

Some times you do not want to use a separate web server, you can use the WebLogic as a Web Server by using a servlet, but this is subject for another post.

When you are deploying a WebCenter solution using a proxy server, you need to remember to proxy all your requests from all weblogics for Security, performance and Control and also all non-weblogic requests such as static files, WebCenter Content custom requests, Services, Portlets and 3rd Party.

Is common in intranet deployments you see calls direct to the application servers, calls to several different servers, like the Figure C.

Above you can see the same sample with all calls using the web server, for proxy forward, for reverse proxy, static files caching, even the use of Oracle Coherence is easy when you have a WebCenter Spaces + Content deployment.

We cannot forget to talk about the clustering and load balancers, Clustering is easy done by the WebLogic, you just need to follow the documentation. For Load balancing you need to choose what kind and what load balancer you will use.

LOAD BALANCING

You can do load balancing using the Web Proxy Server with WLS Plugin or a servlet as mentioned above or a External Load Balancer (Hardware) or Appliance.

Using the WLS Plugin you will need to remember to create a entry for WebCenter Server that are you using, that means that you need to create a entry for the /webcenter/ another for the /cs/, another for the “custom sitestudio” calls, for the portlets (If you do not create a parent folder for the portlets, you will need to create a entry for each portlet) and an entry for any other 3rd calls.

The configuration file for each entry will looks like this sample for IIS7:

# Changed by Oracle A-Team (Adao.Junior)
# Date: 07/31/2011
# WebCenter Content: CUSTOMER_WEB_SERVER
# WLSPlugin1.1-IIS6-IIS7-win64-x64
WebLogicCluster=192.168.100.101:8888,192.168.100.102:8888,192.168.100.101:8891,192.168.100.102:8891
ConnectTimeoutSecs=25
ConnectRetrySecs=5
KeepAliveEnabled=true
FileCaching=ON
SecureProxy=OFF
Debug=OFF
WLTempDir=C:\DEBUG\CONTENT

For a External Load Balancer (Hardware) you have many options, such as the f5 Big-IP, a guide to help you deploy with WebCenter could be found here.

There’s a option to use a hybrid configuration, with Hardware loadbalancers and Web Proxy to handle the web calls between the users and web farms, and web proxies and between the proxies and applications servers.