Portal Application DC

[former_member191569]

Hello,

I am developing a Portal application (PAR) using SAP's component model, so I have created a DC of type Enterprise Portal -> Portal Application Module. My application uses external Java libraries, like log4j, so I created another DC of type External Library to include those JARs needed for the compilation of the PAR DC. But these libraries are needed to be deployed in the server and the External Library DC is not deployable, my question is "which is the correct way to deploy those libraries"? Can I include the JARs inside the folder dist/PORTAL-INF/lib of the PAR (adding the resource to the DTR) or is a best approach to create another DC (of type J2EE Server Component -> Library) for its deployment?

[detlev_beutner · Accepted solution]

Hi David,

You can go both ways, anyhow, deploying it seperately seems to be more "efficient", as with that you can reuse it from other apps you are developing.

Search for "deploy external library" here on SDN, you will find many threads about it, but you gave the answer by yourself; you need a J2EE Server Component - Library DC, that wraps the external library DC.

Hope it helps

Detlev