Using Liberty as an application development environment
Liberty is a lightweight, and very quick, application server. Coupled with the associated free developer tools, Liberty provides a convenient application development environment for your web and OSGi applications.
About this task
Liberty is extremely lightweight, easy to install, and very fast to use. It therefore provides a convenient and capable platform for developing and testing your web and OSGi applications. This is especially true if you are developing applications to run on IBM® WebSphere® Application Server, because any application that runs on Liberty will also run on WebSphere Application Server traditional.
For application development, you might want to install Liberty on its own, either by using the
Installation Manager or by downloading an executable JAR file from the WASdev community download page. On
distributed platforms, you might prefer to develop your applications using the WebSphere Application Server Developer Tools for Eclipse that are freely available. If you do this,
you do not have to install Liberty
beforehand. The developer tools can also download and install the application-serving environment.
Procedure
- Migrating applications to Liberty
- Migrating data access applications to Liberty
- Configuration differences between the WebSphere Application Server traditional and Liberty: dataSource and jdbcDriver elements
- Configuration differences between the WebSphere Application Server traditional and Liberty: connectionManager element
- Migrating a DB2 data source to Liberty
- Migrating a Derby embedded data source to Liberty
- Migrating data access applications to Liberty
- Installing Liberty by using downloaded archives
Installing Liberty developer tools and (optionally) Liberty
Installing Liberty by extracting a Java archive file
Applying a fix pack to a Liberty Java archive installation
Applying an interim fix to a Liberty archive installation
Configuring the Liberty server to start as a job in the QWAS9 subsystem on IBM i
Uninstalling the Liberty application-serving environment from IBM i
- Setting up Liberty
- Administering Liberty
- Liberty features
Administering Liberty by using developer tools
- Editing the Liberty configuration by using developer tools
- Starting and stopping a server by using developer tools
- Defining a utility project as a shared library
- Setting a web project to use shared libraries
- Exploring the runtime environment by using developer tools
- Displaying the server configuration in a merged view
- Viewing the schema documentation for the server configuration
- Generating a Liberty server dump using developer tools
- Packaging a Liberty server by using developer tools
- Adding a data source by using developer tools
- Administering Liberty manually
- Customizing the Liberty environment
- Administering Liberty from the command line
- Adding and removing Liberty features
- Using include elements, variables, and Ref tags in configuration files
- Controlling dynamic updates
- Configuring class loaders and libraries for Java EE applications
- Using a Java library with a Java EE application
- Sharing a library across multiple Java EE applications
- Providing global libraries for all Java EE applications
- Accessing third-party APIs from a Java EE application
- Removing access to third-party APIs for a Java EE application
- Overriding a provided API with an alternative version
- Adding a plug-in configuration to a web server
- Configuring session persistence for Liberty
- Connecting to Liberty by using JMX
- Administering data access applications on Liberty
- Administering web applications on Liberty
- Extending Liberty
- Developing a Liberty feature for Liberty
- Developing a Liberty feature manually
- Creating a Liberty feature by using developer tools
- Developing an OSGi bundle with simple activation
- Composing advanced features by using OSGi Declarative Services
- Advanced Configuration
- Providing an application endpoint
- Liberty SPI utilities
- Including protected features
- Locating OSGi applications
- Developing a custom TAI as a Liberty feature
- Dynamic content management
- Packaging and installing Liberty features
- Embedding the Liberty server in your applications
- Creating Liberty servers from custom configurations
- Developing a Liberty feature for Liberty
- Securing Liberty and its applications
- Getting started with security in Liberty
- Securing communications with Liberty
- Authenticating users in Liberty
- Authorizing access to resources in Liberty
- Configuring secure JMX connection to Liberty
- Configuring web security related properties in Liberty
- Configuring authentication aliases for Liberty
- Setting up Liberty to run in SP800-131a
- Developing extensions to the Liberty security infrastructure
- Deploying applications in Liberty
Deploying applications to Liberty servers by using developer tools
- Packaging a Liberty server from the command line
- Using JNDI binding for constants from the server configuration files
- Deploying OSGi applications to Liberty
- Deploying data access applications to Liberty
- Deploying a web application to Liberty
- Deploying a JPA application to Liberty
- Deploying web services applications to Liberty
- Deploying JAX-RS 2.0 applications to Liberty
- Deploying JAX-WS applications to Liberty
- Implementation of JAX-WS web services applications
- Implementation of JAX-WS client applications
- Customizing web services endpoints
- Enabling HTTP conduit client properties and user custom properties
- Enforcing adherence to WSDL bindings in JAX-WS web services
- The ibm-ws-bnd.xml file
- The web services commands
- Deploying messaging applications to Liberty
- Monitoring the Liberty server runtime environment
- Tuning Liberty

File name: thread_twlp_devenv.html