The document provides an overview of the Payara Services Admin Console. It describes key concepts including domains, instances, applications, resources, monitoring, and configuration. Domains contain runtime environments made up of configurations for instances, applications, and resources. The admin console allows users to configure domains and instances, deploy applications and resources, monitor servers and their components, and ensure server stability through configuration.

1. Overviewing
Admin Console
Kenji HASUNUMA
Payara Services Ltd
kenji.hasunuma@payara.fish

2. Admin Console

3. Admin Console (L10N)

5. Domain
• Unit of Runtime Environments
• Collection of configurations:
• Instances, Applications, Resources
• Controlled by Admin Server (DAS)
• `asadmin start-domain` to start up

7. Instance
• JVM process that has its own:
• Jakarta EE configuration
• Jakarta EE resources
• application deployment area
• server configuration settings

9. Application
• Server-side Java applications
• Based on Jakarta EE API
• Uses shared resources (e.g. JDBC)
• Deploy application to enable to be
used by outside of the server

11. Resource
• Provide connectivity to EIS (via JNDI)
• JDBC w/Connection Pools
• JMS Resources
• JavaMail Sessions
• Connectors
• Concurrent Resources

13. Monitoring
• Reviewing the runtime state of
components and services
• Exposes via AMX that is extension of
JMX and JSR 77
• It's structured by Tree Node API and
explained using Dotted-names

14. Configuration
• Data set determines how to operate
• JVM Settings and System Properties
• Logging and Monitoring Settings
• Web/EJB Container and Thread Pools
• Security and Availability, etc.
• It's structured by Tree Node API and
explained using Dotted-names

15. Your Tasks
1. Configure domain and instances
2. Deploy applications and resources
3. Monitor servers:
instances, applications, resources
4. Keep your servers stable