Removed instructions about the OSGi Web Console.

[Ariho-Seth]

In this PR, information about the OSGi module management was removed from the administration-guide documentation because it no longer exists in GlassFish 7. The last update of the artifacts version in the Maven Central was made in 2017 for GlassFish 5.0.

<dependency>
    <groupId>org.glassfish.main.packager</groupId>
    <artifactId>glassfish-osgi-http</artifactId>
    <version>5.0</version>
</dependency>

Fixes https://github.com/eclipse-ee4j/glassfish/issues/24314

[Ariho-Seth]

Hello @OndroMih, Please have a look thru this PR and let me know whether there is anything to be added.

[OndroMih]

Hi @Ariho-Seth , the core OSGi functionality still works in GlassFish. Only the Web Console was removed - it's a component in the Admin UI of GlassFish. OSGi can be still administered via command line commands.

[Ariho-Seth]

Sorry @OndroMih, for the misunderstanding above. But I've updated the PR for to reflect the suggested changes. Please let me know if it delivers what we are intending to achieve. Thanks!

[OndroMih]

Hi, @Ariho-Seth, based on the conversation https://github.com/eclipse-ee4j/glassfish/pull/25649#discussion_r2249761354, we found out that it may be possible to install the Web Console. It cannot be installed from the Update Center anymore, but it might be possible to install it by directly added files to a GlassFish installation.

I think it's worth exploring this and keep the documentation for now. Let's pause work on this PR until we decide whether we want to explore how to install the Web Console or we just remove the docs.

[Ariho-Seth]

Hi, @Ariho-Seth, based on the conversation #25649 (comment), we found out that it may be possible to install the Web Console. It cannot be installed from the Update Center anymore, but it might be possible to install it by directly added files to a GlassFish installation.

I think it's worth exploring this and keep the documentation for now. Let's pause work on this PR until we decide whether we want to explore how to install the Web Console or we just remove the docs.

Sure thing, I'll be ready anytime.

[OndroMih]

Just for the record, I was able to install the Apache Felix OSGi console into GlassFish 7.0.25 in this way, bit hacky and manual:

I downloaded the following Maven artifacts into the glassfish/modules directory:

• org.owasp.encoder.encoder-1.3.1.jar
• org.apache.felix.http.bridge-6.0.0.jar
• org.osgi.service.log-1.5.0.jar
• glassfish-osgi-console-plugin-7.0.25.jar
• slf4j-api-2.0.17.jar
• slf4j-jdk14-2.0.17.jar
• org.apache.felix.http.servlet-api-3.0.0.jar
• org.apache.felix.inventory-1.1.0.jar
• javax.servlet-api-4.0.1.jar

And these ones into the glassfish/modules/autostart directory, so that it starts automatically at server startup:

• org.apache.felix.webconsole-5.0.12.jar
• org.apache.felix.http.jetty12-1.0.36.jar

Then I edited the file glassfish/config/osgi.properties and set org.osgi.framework.system.capabilities to:

org.osgi.framework.system.capabilities=\
osgi.ee; osgi.ee="JavaSE/compact1"; version:List="1.8",${eecap-${java.vm.specification.version}}

This is required because the module org.osgi.service.log-1.5.0.jar requires the osgi.ee=JavaSE/compact1)(versi on=1.8) capability, which is not realy needed and not supported on newer Java versions.

In the osgi.properties file, I added org.osgi.service.http.port=7080 property, which is for the embedded Jetty server to run on port 7080. I didn't find an easy way how to deploy the OSGi console to a GlassFish listener, so I used embedded Jetty and it binds to this port.

Then I could run GlassFish and access the OSGi console at https://