How to incorporate log4j into a BusinessStudio Java component?

I want to see, how I can use, access and configure log4j from my HelloWorld application. The AMX SG documentation at several levels and locations states, that AMX SG supports log4j (and slf), but HOW does it actually do that?

Now, I do have extensive experience with Eclipse as well as with log4j, i.e. I know where I can download the log4j library or how to integrate and pack it up with a plain vanilla Java application but how is this done with AMX SG and  BusinessStudio? What is the expected/suggested approach?

From experience with other platforms I would have expected that AMX SG would be what eclipse calls a "target runtime" or "target platform", i.e. that it would come with a description of all packages available in the runtime into which the application (fragment) will later be deployed. But BusinessStudio does not offer such a runtime...

Or, since it is OSGi-based, that one has to declare an OSGi project and import/refer to a couple of other specific OSGi plugins, that represent the AMX SG runtime (including the log4j library). However, AMX SG projects are apparently not OSGi projects - at least they don't show the usual OSGi-related tabs under properties.

Or, is log4j to be accessed via references as an SCA component? How is such a component then made visible to my component at compile time?

I have gone through several Tibco AMX SG developer's manuals (like AMX SG Development Tutorials, Java Component Development, Web Application Development, Composite Development, Admin Tutorial, etc.) but I couldn't find any information or example on how to actually refer to and incorporate log4j into my project. Nowhere did I find any description or synopsis summarizing the suggested development approach. How does one make log4j (or for that matter: any code that is packed as a resource-template that is later part of the runtime) visible to a Java application during build time in BusinessStudio so that I can compile it and so that it gets properly packed up into a .daa with all corresponding references properly resolved later at deployment time

Any pointer or tutorial welcome!


(1) Answer