1. Overview of GlassFish Server Administration
Default Settings and Locations
Instructions for Administering GlassFish Server
4. Administering the Virtual Machine for the Java Platform
6. Administering Web Applications
7. Administering the Logging Service
8. Administering the Monitoring Service
9. Writing and Running JavaScript Clients to Monitor GlassFish Server
10. Administering Life Cycle Modules
11. Extending and Updating GlassFish Server
Part II Resources and Services Administration
12. Administering Database Connectivity
13. Administering EIS Connectivity
14. Administering Internet Connectivity
Administering HTTP Network Listeners
To Create an Internet Connection
Administering HTTP Configurations
To Create an HTTP Configuration
To Delete an HTTP Configuration
Administering HTTP Network Listeners
To Create an HTTP Network Listener
To List HTTP Network Listeners
To Update an HTTP Network Listener
To Delete an HTTP Network Listener
To Configure an HTTP Listener for SSL
To Assign a Default Web Module to a Virtual Server
To Assign a Virtual Server to an Application or Module
To Set JSESSIONIDSSO Cookie Attributes
15. Administering the Object Request Broker (ORB)
16. Administering the JavaMail Service
17. Administering the Java Message Service (JMS)
18. Administering the Java Naming and Directory Interface (JNDI) Service
19. Administering Transactions
By default, when GlassFish Server starts, the following HTTP listeners are started automatically:
HTTP listeners associated with the virtual server named server:
The listener named http-listener-1 does not have security enabled.
The listener named http-listener-2 has security enabled
An HTTP listener named admin-listener, associated with the virtual server named __asadmin. For this listener, security is not enabled.
The following table describes the GlassFish Server default ports for the listeners that use ports.
Table 14-1 Default Ports for Listeners
|
The following topics are addressed here:
Use the subcommands in this procedure to create an internet connection with the full range of listener options. A network listener is created behind the scenes. For the shortcut version of this process , see To Create an HTTP Network Listener.
Remote subcommands require a running server.
To use the built-in http-listener-1 HTTP protocol, or http-listener-2 HTTPS protocol, skip this step.
To use a built-in protocol, skip this step.
To use the built-in tcp transport, skip this step.
To avoid using a thread pool, or to use the built-in http-thread-pool thread pool, skip this step.
For additional thread pool information, see Chapter 5, Administering Thread Pools.
Specify a protocol and transport, optionally a thread pool.
See To Restart a Domain.
See Also
You can also view the full syntax and options of the subcommand by typing a command such as asadmin help create-http-listener at the command line.
Each HTTP listener has an HTTP protocol, which is created either by using the create-protocol subcommand or by using the built-in protocols that are applied when you follow the instructions in To Create an HTTP Network Listener.
The following topics are addressed here:
Use the create-protocol subcommand in remote mode to create a protocol.
Remote subcommands require a running server.
Information about options and properties for the subcommand are included in this help page.
Example 14-1 Creating an HTTP Protocol
This example creates a protocol named http-1 with security enabled.
asadmin> create-protocol --securityenabled=true http-1 Command create-protocol executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help create-protocol at the command line.
Use the list-protocols subcommand in remote mode to list the existing HTTP protocols.
Remote subcommands require a running server.
Example 14-2 Listing the Protocols
This example lists the existing protocols.
asadmin> list-protocols admin-listener http-1 http-listener-1 http-listener-2 Command list-protocols executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help list-protocols at the command line.
Use the delete-protocol subcommand in remote mode to remove a protocol.
Remote subcommands require a running server.
Example 14-3 Deleting a Protocol
This example deletes the protocol named http-1.
asadmin> delete-protocol http-1 Command delete-protocol executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help delete-protocol at the command line.
Each HTTP listener has an HTTP configuration, which is created either by using the create-http subcommand or by using the built-in configurations that are applied when you follow the instructions in To Create an HTTP Network Listener.
The following topics are addressed here:
Use the create-http subcommand in remote mode to create a set of HTTP parameters for a protocol. This set of parameters configures one or more network listeners,
Remote subcommands require a running server.
Information about options and properties for the subcommand are included in this help page.
Example 14-4 Creating an HTTP Configuration
This example creates an HTTP parameter set for the protocol named http-1.
asadmin> create-http --timeout-seconds 60 --default-virtual-server server http-1 Command create-http executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help create-http at the command line.
Use the delete-http subcommand in remote mode to remove HTTP parameters from a protocol.
Remote subcommands require a running server.
Example 14-5 Deleting an HTTP Configuration
This example deletes the HTTP parameter set from a protocol named http-1.
asadmin> delete-http http-1 Command delete-http executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help delete-http at the command line.
Each HTTP listener has an HTTP transport, which is created either by using the create-transport subcommand or by using the built-in transports that are applied when you follow the instructions in To Create an HTTP Network Listener.
The following topics are addressed here:
Use the create-transport subcommand in remote mode to create a transport for a network listener,
Remote subcommands require a running server.
Information about options and properties for the subcommand are included in this help page.
Example 14-6 Creating a Transport
This example creates a transport named http1-trans that uses a non-default number of acceptor threads.
asadmin> create-transport --acceptorthreads 100 http1-trans Command create-transport executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help create-transport at the command line.
Use the list-transports subcommand in remote mode to list the existing HTTP transports.
Remote subcommands require a running server.
Example 14-7 Listing HTTP Transports
This example lists the existing transports.
asadmin> list-transports http1-trans tcp Command list-transports executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help list-transports at the command line.
Use the delete-transport subcommand in remote mode to remove a transport.
Remote subcommands require a running server.
Example 14-8 Deleting a Transport
This example deletes he transport named http1-trans.
asadmin> delete-transport http1-trans Command delete-transport executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help delete-transport at the command line.
The following topics are addressed here:
Use the create-http-listener subcommand or the create-network-listener subcommand in remote mode to create a listener. These subcommands provide backward compatibility and also provide a shortcut for creating network listeners that use the HTTP protocol. Behind the scenes, a network listener is created as well as its associated protocol, transport, and HTTP configuration. This method is a convenient shortcut, but it gives access to only a limited number of options. If you want to specify the full range of listener options, follow the instructions in To Create an Internet Connection.
Remote subcommands require a running server.
If you edit the special HTTP network listener named admin-listener, you must restart the server for changes to take effect. See To Restart a Domain.
Example 14-9 Creating an HTTP Listener
This example creates an HTTP listener named sampleListener that uses a non-default number of acceptor threads. Security is not enabled at runtime.
asadmin> create-http-listener --listeneraddress 0.0.0.0 --listenerport 7272 --defaultvs server --servername host1.sun.com --acceptorthreads 100 --securityenabled=false --enabled=false sampleListener Command create-http-listener executed successfully.
Example 14-10 Creating a Network Listener
This example a network listener named sampleListener that is not enabled at runtime:
asadmin> create-network-listener --listenerport 7272 protocol http-1 --enabled=false sampleListener Command create-network-listener executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help create-http-listener or asadmin help create-network-listener at the command line.
Use the list-http-listeners subcommand or the list-network-listeners subcommand in remote mode to list the existing HTTP listeners.
Remote subcommands require a running server.
Example 14-11 Listing HTTP Listeners
This example lists the HTTP listeners. The same output is given if you use the list-network-listeners subcommand.
asadmin> list-http-listeners admin-listener http-listener-2 http-listener-1 Command list-http-listeners executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help list-http-listeners or asadmin help list-network-listeners at the command line.
The listener is identified by its dotted name.
Example 14-12 Updating an HTTP Network Listener
This example changes security-enabled to false on http-listener-2.
asadmin> set server.network-config.protocols.protocol.http-listener-2.security-enabled=false Command set executed successfully.
Use the delete-http-listener subcommand or the delete-network-listener subcommand in remote mode to delete an existing HTTP listener. This disables secure communications for the listener.
Remote subcommands require a running server.
See To Restart a Domain.
Example 14-13 Deleting an HTTP Listener
This example deletes the HTTP listener named sampleListener:
asadmin> delete-http-listener sampleListener Command delete-http-listener executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help delete-http-listener or asadmin help delete-network-listener at the command line.
Use the create-ssl subcommand in remote mode to create and configure an SSL element in the specified listener. This enables secure communication for the listener.
Remote subcommands require a running server.
See To Restart a Domain.
Example 14-14 Configuring an HTTP Listener for SSL
This example enables the HTTP listener named http-listener-1 for SSL:
asadmin> create-ssl --type http-listener --certname sampleCert http-listener-1 Command create-ssl executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help create-ssl at the command line.
Use the delete-ssl subcommand in remote mode to delete the SSL element in the specified listener. This disables secure communications for the listener.
Remote subcommands require a running server.
See To Restart a Domain.
Example 14-15 Deleting SSL From an HTTP Listener
This example disables SSL for the HTTP listener named http-listener-1:
asadmin> delete-ssl --type http-listener http-listener-1 Command delete-http-listener executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help delete-ssl at the command line.
For more information, see To Assign a Default Web Module to a Virtual Server.
See Also
For details, click the Help button in the Administration Console from the HTTP Listeners page.