nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

BEA BulkLoader Adapter - deployment design

Johnny

Before I go into scripting a solution to this - what does the BL adapter need to process a document - IE is the processing based off the document itself or the md.properties file from the OD manifest?

The reason why I ask is that currently we're looking to split our deployment into two steps to provide a more flexible deployment.

This is what we're planning

1. deployment is kicked off to push content to the portal doc root (could be filelist, area compare, whatever)
1.1 on success a dnr is kicked off on the source side and an .md.properties file is created for each content file that was deployed (based off the manifest)
1.2 the dnr then kicks off a second deployment that is a filelist deployment which pushes all the md.properties that were just generated.
1.2.1 this deployment is where the bulkloader should be invoked - the deployment manifest only consists of the .md.properties - not the content.

We came up with this idea because it allows step 1 to be any kind of deployment (filelist, comparison etc) - so it's not tied down to a workflow process etc... it gives us more options.

Two questions -

does this process seem complicated?.. is there a more obvious solution?
will this even work?.. will step 1.2.1 work with the bulkloader adapter considering the manifest will hold the .md.properties not the content files - what is the adapter looking for in the manifest - md.properties or the content or both (hopefully it's either / or).

Thanks

Find more posts tagged with

Comments

Migrateduser

I know u wanted to have flexibility but can you combine both the deployments into one deployment. Can u create the md.properties file as part of the first deployment? If not, you proposed solution should work.

Bulk Loader Adapter looks for both md.properties file as well as the content.

Johnny

for an area comparison deployment - you can't really do that - you don't know whats being deployed - we need that kind of deployment for certain synchronization purposes.

When you say the adapter uses both - does that mean - it can work with either... or does it need *both* in the one deployment?

Johnny

My testing failed - it seems to crash the bulkloader.

OD 6.0.1 SP 1, Solaris 8, BEA Portal 8.1

Is there more documentation on this?

The adapter log file does not update after the first run - does that mean something has crashed?... OD completes OK though....

This is the adapter log file from the first deployment test
2006-04-07 16:39:46,461 INFO Begin logfile [/app/teamsite/OpenDeployNG/log/conf-od/gwm_rp/adp.bbl.intranet_portal_properties_fl20060407_163947_7821.properties.pbgliccontd1.to.cpb_intranet_app_prod.log] ---------
2006-04-07 16:39:46,462 DEBUG Got logger: level=DEBUG, logFile=/app/teamsite/OpenDeployNG/log/conf-od/gwm_rp/adp.bbl.intranet_portal_properties_fl20060407_163947_7821.properties.pbgliccontd1.to.cpb_intranet_app_prod.log, layoutPattern="%d %-5p %m%n"
2006-04-07 16:39:46,462 INFO Input Parameter = /export/home/intradev/OD_602_installs/od_bl_conf.xml
2006-04-07 16:39:46,474 INFO Printing out the Deployment details
2006-04-07 16:39:46,474 INFO ODHOME = /app/teamsite/OpenDeployNG
2006-04-07 16:39:46,494 INFO Printing out the Manifest item details
2006-04-07 16:39:46,494 INFO Path = portalproperties/EMEA/folder2/Page 1.html.md.properties
2006-04-07 16:39:46,494 INFO Type = FILE
2006-04-07 16:39:46,494 INFO Action = UPDATE
2006-04-07 16:39:46,494 INFO Reason = UPDATE
2006-04-07 16:39:46,495 INFO Status = COMPLETED
2006-04-07 16:39:46,495 INFO Target Area = /opt/intranet/docs/ODDS/production
2006-04-07 16:39:46,495 INFO Source Area = /.iwmnt/default/main/Intranet/GWM-Risk/WORKAREA/Global
2006-04-07 16:39:46,495 INFO New Path = portalproperties/EMEA/folder2/Page 1.html

Migrateduser

Please post the complete log .

tsrookie

Hi Johnny,

We are using Teamsite 6.1 and BEA 8.1 sp4 on solaris.

In my presentation templates I create a .md.properties file for every piece of content to be deployed.

In my workflow we read the manifest and attach all files.

We use a filelist deployment. In the od config using dnr we create a temporary directory which we write both content and md.prop files too, we then invoke bulkloader to upload from the temporary directory, then we delete the temporary directory.

An alternative approach is to create a dir.md.properties file and that relates to all files in a directory rather than creating an md props file for each file, This didn't suit us as we required unique metadata for each file.

Bulkloader out of the box didn't work for us and our java guru had to make some changes. Deleting content from the vcr involved a bit of trickery too.

We have now succesfully launched our employee portal project, although the Team is looking to JBOSS to replace BEA.

HTH Colin

gzevin

We have now succesfully launched our employee portal project, although the Team is looking to JBOSS to replace BEA.

HTH Colin

Colin, it's nice to see you Smiley Happy

I am glad to see that this finally is done Smiley Happy

John -

I was going to reply, but I guess you figured out yourself - BL needs both file and .md. Even stub file will work, if you don't have much content

Johnny

Thanks Greg - the question was more about what the OD adapter expects.

I think the difference is that ours is a filesystem based repository - apparently OD 6.1 can handle that - though I still haven't figured out the remote upgrade options for OD 6.1 Smiley Happy