users@glassfish.java.net

Re: Neet help getting started

From: Lachezar Dobrev <l.dobrev_at_gmail.com>
Date: Fri, 5 Apr 2013 16:09:01 +0300

  You need to SSH into the target machine and issue:
    asadmin enable-secure-admin

  This (if I recall correctly) ask you to set up a password for the
admin user. Afterwards you will be able to access the administrative
console via https://host:4848.

  If you're going to remotely manage a Glassfish server I *strongly*
suggest you familiarise yourself with the 'asadmin' administrative
tool. It can do everything the UI does, possibly some things the UI
can not handle.

  I would suggest you run the Glassfish server as a non-privileged
user, but that's just my preference.

2013/4/5 Blake McBride <blake_at_arahant.com>
>
> I'd like to add that I am familiar with SSH port forwarding. Unfortunately, some of my clients have me accessing SSH through a non-standard, commercial, proprietary VPN that renders port forwarding not an option.
>
> Thanks.
>
> Blake
>
>
> Blake McBride
>
> www.arahant.com
> Cell: 615-394-6760
> Office: 615-376-5500
> Fax: 615-377-6006
>
>
>
>
> On Fri, Apr 5, 2013 at 7:39 AM, Blake McBride <blake_at_arahant.com> wrote:
>>
>> Greetings,
>>
>> I am a long time tomcat user evaluating glassfish 3.1.2.2. I imagine that following the instructions would be an easy way to get things going, however, the glassfish method of setup runs contrary to what I think is normal (or even possible) in most environments. I'm sure I am missing something simple. Here are my problems.
>>
>> I understand that glassfish has a gui install. The problem is that most places I would install glassfish are linux servers without X11. It seems that I would therefore prefer the zip install. I did that.
>>
>> I presume the setup is done through the management console. The problem is that the management console is run at port 4848. I perform my installs remotely over SSH. Most clients I would install for have hefty firewalls and hefty security policies that would disallow port 4848, period. Tomcat has its management console over the same port as the application just using a different URL. This means I can manage tomcat at the same port as my app by just adding "/admin" to the end of my application URL (for example).
>>
>> The second problem I have is that (since I installed with a zip file) nothing has been configured. When I try to access tha management console I get: Configuration Error Secure Admin must be enabled to access the DAS remotely.
>>
>> I need to be able to set a password and configure the management console through some text base config files before I even start glassfish up.
>>
>> So, as you can see I am having a problem with the most basic stuff. I looked on the net briefly and I have Heffelfinger's book but neither answered these most basic questions.
>>
>> Thanks for the help!
>>
>> Blake McBride
>>
>>
>>
>>
>