On Tue, Dec 5, 2017 at 12:09 PM, Peter Kriens <[email protected]> wrote:
> I’ve added these points to the Resolve App Note. https://github.com/osgi/ > osgi.enroute.site/blob/gh-pages/_appnotes/resolving.md > Awesome! Thanks Peter! - Ray > Kind regards, > > Peter Kriens > > > On 5 Dec 2017, at 15:46, Raymond Auge via osgi-dev <[email protected]> > wrote: > > > > On Tue, Dec 5, 2017 at 9:42 AM, Raymond Auge <[email protected]> > wrote: > >> Hey Kevin, >> >> Here's what I could find: "Deploying OSGi applications to Liberty" [1] >> >> Now, this may be a little complicated by the fact that the enroute model >> tends to guide you to resolve a whole runtime. Meanwhile with openliberty >> or WebSphere Liberty you are deploying into a container which already >> "contains a lot of features". >> >> The crux of the issue becomes "resolving only what you need to deploy". >> This is were the complication comes in. What you need at that point is a >> way to "find out what the container provides in a way that you can use this >> during resolve time". >> >> Currently the way to do that is to create what's called a "distro" jar of >> the target container. This distro is a JAR file which provides all the >> capabilities that the target container provides at one point in time. >> >> How do you create a distro? >> >> *1)* install the bnd remote agent bundle [2] in the target container >> runtime. This will automatically open a local socket on a default port used >> to the remote cli next. >> *2)* execute the following command using the bnd cli [3]: >> >> bnd remote distro -o ws.liberty-5.6.7.jar ws.liberty 5.6.7 >> > > FYI, this "bnd" command is just an alias for invoking the executable bnd > jar: "java -jar <bnd.jar> remote distro ..." > > >> >> *3)* take the jar "ws.liberty-5.6.7.jar" create by that and place it >> into the maybe the directory containing the bndrun file which is used to >> resolve your deployment jars. >> *4)* in the bndrun file add: >> >> -distro: file:${.}/ws.liberty-5.6.7.jar >> >> *5)* resolve... the result of the resolve should be the set of bundles >> you need to install to openliberty. >> >> What you need to bare in mind is that the distro file needs to be >> regenerated each time the liberty installation changes in any significant >> way otherwise you won't get the real state of the system needed to resolve >> against. >> >> I hope that makes some sense. >> >> Let me know if the instructions were clear and if it worked. >> >> - Ray >> >> [1] https://www.ibm.com/support/knowledgecenter/en/SSEQTP_libert >> y/com.ibm.websphere.wlp.doc/ae/twlp_dep_osgi.html >> [2] http://search.maven.org/remotecontent?filepath=biz/aQute/ >> bnd/biz.aQute.remote.agent/3.5.0/biz.aQute.remote.agent-3.5.0.jar >> [3] http://search.maven.org/remotecontent?filepath=biz/aQute/ >> bnd/biz.aQute.bnd/3.5.0/biz.aQute.bnd-3.5.0.jar >> >> >> On Tue, Dec 5, 2017 at 9:11 AM, Matthews, Kevin via osgi-dev < >> [email protected]> wrote: >> >>> Hi Tim, a quick question. I am learning OSGI from osgi en route samples. >>> In our environment, our monolithic application runs on IBM Websphere >>> Liberty but I am doing a POC to convert to modular architecture then >>> bundles to run on Websphere Liberty. Can I build bundles using BND en route >>> from my eclipse and install these bundles on a Liberty server? I know >>> liberty uses the equinox OSGI container. >>> The information in this message may be proprietary and/or confidential, >>> and protected from disclosure. If the reader of this message is not the >>> intended recipient, or an employee or agent responsible for delivering this >>> message to the intended recipient, you are hereby notified that any >>> dissemination, distribution or copying of this communication is strictly >>> prohibited. If you have received this communication in error, please notify >>> First Data immediately by replying to this message and deleting it from >>> your computer. >>> >>> _______________________________________________ >>> OSGi Developer Mail List >>> [email protected] >>> https://mail.osgi.org/mailman/listinfo/osgi-dev >>> >> >> >> >> -- >> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> >> (@rotty3000) >> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com/> >> (@Liferay) >> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org/> >> (@OSGiAlliance) >> > > > > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com/> > (@Liferay) > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org/> > (@OSGiAlliance) > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > > > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
