### Get Help for dynamicRouting setup

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=collectives-dynamic-routing-command

To access command help for the setup dynamicRouting command, execute the provided command. This will display usage information and available options.

```shell
${wlp.install.dir}/bin/dynamicRouting help setup
```

--------------------------------

### Install a Single Asset

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=assets-installing-using-installutility-command

Use the `installUtility install` command to install a specific asset by its shortName. This example installs the 'jca-1.6' feature.

```bash
installUtility install jca-1.6
```

--------------------------------

### Install a sample

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=command-installutility

Use this command to install a sample application or feature.

```bash
installUtility install JDBCSample
```

--------------------------------

### Server Command Usage Examples

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=line-server-command-options

Demonstrates common server command actions such as running, starting with a clean option, packaging, dumping, and generating Java dumps.

```shell
server run
```

```shell
server start myserver --clean
```

```shell
server package myserver --archive="archivefile.zip" --include=all
```

```shell
server dump myserver --archive="c:\mybackup\myserver.zip" --include=thread
```

```shell
server javadump myserver
```

```shell
server javadump myserver --include=thread,system
```

--------------------------------

### Install a server

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=command-installutility

Use this command to install a server configuration or package.

```bash
installUtility install myServer
```

--------------------------------

### Install Assets from a Local Repository

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=assets-installing-using-installutility-command

Install assets from a local directory-based repository by specifying the repository path with the `--from` option. This example installs 'jca-1.6' from a specific zip file.

```bash
installUtility install jca-1.6 --from=/wlp-featureRepo-17.0.0.1.zip
```

--------------------------------

### Display Help for Install Action

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=command-featuremanager

Displays detailed help information for the 'install' action of the featureManager command. Use this to understand available options for installation.

```bash
featureManager help install
```

--------------------------------

### Example: Download File from Member Server

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=tfilc-transferring-files-from-collective-member-registered-host-rest-calls

Demonstrates setting member server routing context and invoking a GET call to download a file.

```properties
com.ibm.websphere.jmx.connector.rest.routing.hostName=myTarget.com
com.ibm.websphere.jmx.connector.rest.routing.serverName=myServerA
com.ibm.websphere.jmx.connector.rest.routing.serverUserDir=C:/server/wlp
```

```http
GET https://myTarget.com:9443//IBMJMXConnectorREST/file/C%3A%2Ftemp%2FmyFile.txt
```

--------------------------------

### Example: Download File from Registered Host

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=tfilc-transferring-files-from-collective-member-registered-host-rest-calls

Demonstrates setting registered host routing context and invoking a GET call to download a file.

```properties
com.ibm.websphere.jmx.connector.rest.routing.hostName=myTarget.com
```

```http
GET https://myTarget.com:9443//IBMJMXConnectorREST/file/C%3A%2Ftemp%2FmyFile.txt
```

--------------------------------

### Example keytool command for JKS keystore

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=certificates-setting-up-third-party-existing-collective

This example demonstrates the use of the keytool utility to manage JKS keystores. Ensure the keytool utility is accessible from your Java installation directory. This command is part of the procedure for setting up third-party certificates.

```shell
keytool -import -alias root -keystore /path/to/collectiveTruststore.jks -trustcacerts -file /path/to/third_party_ca.crt
```

--------------------------------

### Logging Configuration Example

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=liberty-logging-trace

Example of setting logging and trace properties within the server configuration file.

```xml
<logging traceSpecification="*=audit:com.myco.mypackage.*=finest"/>
```

--------------------------------

### Install Configuration Snippet

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=line-configutility-command

Use 'configUtility install' to install a configuration snippet. Options include displaying information (--info), setting variables (--vvariable=value), and specifying the configuration file path (--createConfigFile).

```bash
configUtility install configSnippet
```

```bash
configUtility install configSnippet --info
```

```bash
configUtility install configSnippet --vvariable=value
```

```bash
configUtility install configSnippet --createConfigFile=C:/wlp/usr/servers/server1/snippet-include.xml
```

--------------------------------

### Example Log Detail Level Specification

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=liberty-logging-trace

An example demonstrating how to set specific log detail levels for components.

```text
*=info
```

--------------------------------

### Example Shared Configuration XML

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=sets-automatically-sharing-configurations-among-replicas

This is an example of a valid server.xml include file content that can be added to the shared configuration.

```xml
<?xml version="1.0" encoding="UTF-8" ?>
<server>
  <logging traceSpecification="com.ibm.ws.collective.repository.internal.SharedConfigManager=all"/>
</server>
```

--------------------------------

### Start Link Server with INITPARM

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=cics-liberty-server-transactions-bboc-bbo-bbo

Use this INITPARM string to start a link server under a specified register name and WOLA group names when CICS starts. Specifying SVC=* allows the link server to receive requests for all service names.

```shell
INITPARM=(BBOACPL2='STA RGN=PAYROLL DGN=LIB1 NDN=LIB2 SVN=LIB3 SVC=*')
```

--------------------------------

### Install a local .esa file

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=command-installutility

Use this command to install a local Enterprise Service Archive (.esa) file.

```bash
installUtility install c:\temp\myFeature.esa 
```

--------------------------------

### Install Assets from a Local Directory

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=assets-installing-using-featuremanager-command

Install assets from a local directory by specifying the directory path with the `--location` option.

```bash
bin/featureManager install feature_shortName1 feature_shortName2 --location=directoryPath
```

--------------------------------

### Install Feature Bundle Addons

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=assets-installing-using-installutility-command

Install feature bundle addons to get all features applicable to your edition. This example installs the 'ndControllerBundle' addon.

```bash
installUtility install ndControllerBundle
```

--------------------------------

### Example: Generate Controller Keystore with Basic Options

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=keys-generating-collective-controller-ssl

An example demonstrating the use of basic options to generate a keystore for a collective controller.

```bash
collective genKeyController --host=machineA --password=Admin1pwd --port=1090 --user=Admin1 --keystorePassword=kspwd --autoAcceptCertificates
```

--------------------------------

### GET request for coverage map

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=liberty-invoking-coverage-map-service

This is an example GET request to retrieve the coverage map for the bearer token type.

```http
GET https://server.example.com:443/oidc/endpoint/<provider_name>/coverage_map?token_type=bearer
```

--------------------------------

### Example: Generate Controller Keystore with Simplified Controller Option

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=keys-generating-collective-controller-ssl

An example showing how to use the `--controller` option for generating a keystore, simplifying the command structure.

```bash
collective genKeyController --controller=Admin1:Admin1pwd@machineA:1090  --keystorePassword=kspwd --autoAcceptCertificates
```

--------------------------------

### Example: Generate Member Keystore (Using --controller)

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=keys-generating-collective-member-ssl

This example shows how to generate a member keystore using the `--controller` option, which consolidates controller connection information into a single parameter. It specifies the keystore password and auto-accepts certificates.

```bash
collective genKey --controller=Admin1:Admin1pwd@machineA:1090  --keystorePassword=kspwd --autoAcceptCertificates
```

--------------------------------

### View Repository and Proxy Settings

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=command-configuring-repositories-proxy-settings-installutility

Run `installUtility viewSettings` to output a configuration template and review repository and proxy settings. The command also validates the properties file.

```shell
>installUtility viewSettings

installUtility Settings
----------------------------------------------------------------------
Properties File: c:\wlp\etc\repositories.properties
Default Assets Repository: IBM WebSphere Liberty Repository
Use Default Repository: True

Properties File Validation
----------------------------------------------------------------------
Validation Results: The properties file successfully passed the 
validation.

Configured Repositories
----------------------------------------------------------------------
Name: dev-rep
Location: http://dev.repo.ibm.com:9080/ma/v1
User Name: myname
Password: <Unspecified>

Proxy Settings
----------------------------------------------------------------------
Proxy Server: my.proxy.server.ibm.com
Port: 9080
User Name: myname
Password: ********
```

--------------------------------

### Example Custom Provider Output

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=slia-configuring-custompasswordencryption-provider-command-line-utilities-developer-tools

This is an example of the expected output when listing custom password encryption providers. It displays the name, feature name, and description of the installed provider.

```json
[{"name":"custom","featurename":"usr:customPasswordEncryption-1.0","description":"MyCompany custom password encryption"}]
```

--------------------------------

### Example Log Message for Custom Password Encryption Service

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=applications-configuring-custompasswordencryption-provider-liberty-runtime-environment

This is an example of the CWWKS1850I message that indicates the custom password encryption service has started successfully. It also shows the class name of the implementation.

```log
[8/10/16 7:07:07:007 EDT] 0000001e com.ibm.ws.crypto.util.PasswordCipherUtil I CWWKS1850I: The custom password encryption service has started. The class name is com.ibm.websphere.crypto.sample.customencryption.CustomEncryptionImpl.
```

--------------------------------

### Example: Generate Member Keystore

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=keys-generating-collective-member-ssl

This example demonstrates generating a keystore with specific controller details (host, port, user, password) and a keystore password. It also includes the option to automatically accept certificates.

```bash
collective genKey --host=machineA --password=Admin1pwd --port=1090 --user=Admin1 --keystorePassword=kspwd --autoAcceptCertificates
```

--------------------------------

### Launch Eclipse with Specific Java VM and Clean Option

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=overview-viewing-documentation-offline

Start Eclipse using a specific Java Runtime Environment (JRE) and apply the -clean option for a fresh start. This is useful when you have multiple Java versions installed.

```bash
eclipse -vm c:\jdk_80510\jre\bin\javaw.exe -clean
```

--------------------------------

### Start a Server

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=line-starting-stopping-server-from-command

Use this command to initiate the server process. Replace 'serverName' with the actual name of your server.

```bash
server start serverName
```

--------------------------------

### Implicit Flow Request

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=liberty-invoking-authorization-endpoint-openid-connect

Example GET request for the Implicit Flow. This flow directly returns tokens in the redirect URI fragment.

```http
 GET /authorize?
     response_type=id_token token
     &scope=openid profile 
     &client_id=client01 
     &state=af0ifjsldkj 
     &redirect_uri=https://server.example.com:8020/oidcclient/redirect/client01 
     &nonce=n-0S6_WzA2Mj HTTP/1.1 
	
```

--------------------------------

### Full SSL Configuration Example

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=liberty-ssl-configuration-attributes

This example demonstrates a comprehensive SSL configuration within the server.xml file, including default and custom SSL settings, keystores, and truststores.

```xml
<featureManager>
  <feature>transportSecurity-1.0</feature>
</featureManager>


<!-- default SSL configuration is defaultSSLSettings -->
  <sslDefault sslRef="defaultSSLSettings" />
  <ssl id="defaultSSLSettings"
       keyStoreRef="defaultKeyStore"
       trustStoreRef="defaultTrustStore"
       clientAuthenticationSupported="true" />
  <keyStore id="defaultKeyStore"
            location="key.jks"
            type="JKS" password="defaultPWD" />
  <keyStore id="defaultTrustStore"
            location="trust.jks"
            type="JKS" password="defaultPWD" />

  <ssl id="mySSLSettings"
       keyStoreRef="myKeyStore"
       trustStoreRef="myTrustStore"
       clientAuthentication="true" />
  <keyStore id="LDAPKeyStore"
            location="${server.config.dir}/myKey.p12"
            type="PKCS12"
            password="{xor}CDo9Hgw=" />
  <keyStore id="LDAPTrustStore"
            location="${server.config.dir}/myTrust.p12"
            type="PKCS12"
            password="{xor}CDo9Hgw=" />

```

--------------------------------

### Get Servlet Response Time Statistics using MXBean

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=liberty-examples-accessing-mbean-attributes-operations

This example demonstrates retrieving response time statistics for a specific servlet. It shows how to access the 'ResponseTimeDetails' attribute using CompositeData and also how to obtain a proxy object for the ServletStatsMXBean to get the statistics.

```Java
import javax.management.ObjectName;
import javax.management.openmbean.CompositeData;
import javax.management.JMX;
import com.ibm.websphere.webcontainer.ServletStatsMXBean;

...

ObjectName servletMBean = new ObjectName("WebSphere:type=ServletStats,name=myApp.Example Servlet");
if (mbs.isRegistered(servletMBean)) {
	CompositeData responseTimeDetails = (CompositeData) mbs.getAttribute(servletMBean, "ResponseTimeDetails");
	CompositeData responseTimeReading = (CompositeData) responseTimeDetails.get("reading");
	Double mean = (Double) responseTimeReading.get("mean");
	Double standardDeviation = (Double) responseTimeReading.get("standardDeviation");
	// alternatively, obtain a proxy object
	ServletStatsMXBean servletStats = JMX.newMXBeanProxy(mbs, servletMBean, ServletStatsMXBean.class);
	StatisticsMeter meter = servletStats.getResponseTimeDetails();
	StatisticsReading reading = meter.getReading();
	mean = reading.getMean();
	standardDeviation = reading.getStandardDeviation();
}
```

--------------------------------

### Include Configuration Syntax

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=files-using-include-elements-in-configuration

Demonstrates the basic syntax for including configuration files, with an option to make the include optional.

```xml
<include optional="true" location="pathname/filename"/>
or
<include optional="true" location="url"/>
```

--------------------------------

### Install a server package from a compressed .jar file

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=command-installutility

Use this command to install a server package provided as a compressed .jar file.

```bash
installUtility install c:\temp\myServer.jar
```

--------------------------------

### Obtain OSGi Service Directly

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=registry-registering-osgi-services

Retrieve an OSGi service using BundleContext. This example demonstrates getting a service reference and the service object.

```java
package com.ibm.foo.simple;

import java.util.Collection;

import org.osgi.framework.BundleContext;
import org.osgi.framework.InvalidSyntaxException;
import org.osgi.framework.ServiceReference;

/**
 * A simple Foo client that directly obtains the Foo service and returns it when done.
 */
public class FooUser
{

    private final BundleContext bundleContext;

    public FooUser( BundleContext bundleContext )
    {
        this.bundleContext = bundleContext;
    }

    /**
     * assume there's only one Foo
     */
    public void useFooSimple() {
        ServiceReference<Foo> sr = bundleContext.getServiceReference( Foo.class );
        String[] propertyKeys = sr.getPropertyKeys();
        for (String key: propertyKeys) {
            Object prop = sr.getProperty( key );
            //think about whether this is the Foo we want....
        }
        Foo foo = bundleContext.getService( sr );
        try {
            //use foo
        } finally {
            //we're done
            bundleContext.ungetService( sr );
        }
    }

    /**
     * Use a filter to select a particular Foo. Note we get a collection back and have to pick one.
     * @throws InvalidSyntaxException
     */
    public void useFooFilter() throws InvalidSyntaxException {
        Collection<ServiceReference<Foo>> srs = bundleContext.getServiceReferences( 
          Foo.class, "(&(service.vendor=IBM)(id='myFoo')"
        );
        ServiceReference<Foo> sr = srs.iterator().next();
        String[] propertyKeys = sr.getPropertyKeys();
        for (String key: propertyKeys) {
            Object prop = sr.getProperty( key );
            //think about whether this is the Foo we want....
        }
        Foo foo = bundleContext.getService( sr );
        try {
            //use foo
        } finally {
            //we're done
            bundleContext.ungetService( sr );
        }
    }
}
```

--------------------------------

### Example: Download Server Configuration File

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=tfilc-transferring-files-from-collective-member-registered-host-rest-calls

Shows how to download a server configuration file like server.xml from a member server, including URL-encoding Liberty variables.

```properties
com.ibm.websphere.jmx.connector.rest.routing.hostName=myTarget.com
com.ibm.websphere.jmx.connector.rest.routing.serverName=myServerA
com.ibm.websphere.jmx.connector.rest.routing.serverUserDir=C:/server/wlp
```

```http
GET https://myTarget.com:9443//IBMJMXConnectorREST/file/%24{server.config.dir}%2Fserver.xml
```

--------------------------------

### Detailed Library and Application Configuration

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=applications-shared-libraries

An example demonstrating how to configure a shared library with various elements and reference it in an application's classloader.

```xml
<library id="someLibrary">
   <!-- Location of XML and .properties files in the file system for easy editing -->
   <folder dir="${server.config.dir}/editableConfig" />

   <!-- Location of some classes and resources in the file system -->
   <folder dir="${server.config.dir}/extraStuff" />

   <!-- A zip file containing some resources -->
   <file name="${server.config.dir}/lib/someResources.zip" />

   <!-- All the jar files in ther servers lib folder -->
   <fileset dir="${server.config.dir}/lib" includes="*.jar" scanInterval="5s" />
</library>

<application location ="webStore.war">
   <classloader commonLibraryRef="someLibrary" />
</application>
```

--------------------------------

### configUtility Command Syntax

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=line-configutility-command

Basic syntax for using the configUtility command. It supports actions like finding, installing, or getting help for configuration snippets.

```bash
configUtility action | configUtility configSnippet [options]
```

--------------------------------

### Authorization Code Flow Request

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=liberty-invoking-authorization-endpoint-openid-connect

Example GET request for the Authorization Code Flow. This flow is used to obtain an authorization code that can be exchanged for an access token.

```http
 GET /authorize?
     response_type=code
     &scope=openid profile email 
     &client_id=client01 
     &state=af0ifjsldkj 
     &redirect_uri=https://server.example.com:8020/oidcclient/redirect/client01 HTTP/1.1 
	
```

--------------------------------

### Install a server package from a compressed .zip file

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=command-installutility

Use this command to install a server package provided as a compressed .zip file.

```bash
installUtility install c:\temp\myServer.zip
```

--------------------------------

### Configure Quick Start Security

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=liberty-pluginutility-command

This snippet shows how to configure security settings for quick start, including the administrator user name and password.

```xml
<quickStartSecurity
userName="AdminUser"
userPassword="AdminPassword" />
```

--------------------------------

### Configure QuickStart Security in Liberty

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=liberty-authenticating-users-connect-messaging-engine

Use the <quickStartSecurity> element to enable a simple, single-user security setup for Liberty. This is the simplest way to specify a username and password for application connections.

```xml
<quickStartSecurity userName="liberty" userPassword="liberty123"/>
```

--------------------------------

### Wildcard Cluster Matching in Scaling Policy

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=collectives-defining-scaling-policies-manage-workload

Demonstrates how to use a wildcard in the 'clusters' attribute to apply a scaling policy to multiple clusters. This example applies to 'west' and any cluster starting with 'south'.

```xml
<bind clusters="west,south*"/>
```

--------------------------------

### Invoke JMX to Get Outbound Response Counters

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=10-sip-application-monitoring

Example of invoking a JMX method to retrieve outbound response counters. This requires a JMX connection and specifies the MXBean object name, method, application name, and response code.

```Java
_connection.invoke("WebSphere:type=OutboundResponseCounters,name=SipContainer.OutboundResponse", "getTotalOutboundResponses", _appName, "100");
```

--------------------------------

### Example keytool command for PKCS12 keystore

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=certificates-setting-up-third-party-existing-collective

This example shows how to use the keytool utility with PKCS12 keystores. When using PKCS12, remember to specify the correct file name and include the -storetype PKCS12 option in your command. This is an alternative to the JKS keystore type.

```shell
keytool -import -alias root -keystore /path/to/collectiveTruststore.p12 -storetype PKCS12 -trustcacerts -file /path/to/third_party_ca.crt
```

--------------------------------

### Invoke JMX to Get Outbound Request Counters

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=10-sip-application-monitoring

Example of invoking a JMX method to retrieve outbound request counters. This requires a JMX connection and specifies the MXBean object name, method, application name, and request type.

```Java
_connection.invoke("WebSphere:type=OutboundRequestCounters,name=SipContainer.OutboundRequest", "getTotalOutboundRequests", _appName, "INVITE");
```

--------------------------------

### Start Eclipse Help Server

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=overview-viewing-documentation-offline

Use this command to start the Eclipse help server for offline documentation access. Ensure the classpath points to the correct help base JAR file and specify a listener port.

```shell
java -classpath eclipse\plugins\org.eclipse.help.base_4.2.102.v20171130-0510.jar  org.eclipse.help.standalone.Infocenter -eclipsehome eclipse -port 8680 -command start -noexec -clean
```

--------------------------------

### Verify Installation Manager Installation

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=zos-installing-installation-manager

Navigate to the Installation Manager tools directory and run the 'imcl -version' command to verify the installation.

```shell
cd /InstallationManager/bin/eclipse/tools

imcl -version
```

--------------------------------

### Minimal quickStartSecurity Configuration

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=liberty-mapping-management-roles

Use this snippet for a single user mapping with minimal required configuration.

```xml
<featureManager>
     <feature>restConnector-2.0</feature>
 </featureManager>
 <quickStartSecurity userName="bob" userPassword="bobpassword" />
 <keyStore id="defaultKeyStore" password="keystorePassword"/>

```

--------------------------------

### Configure QuickStart Security in server.xml

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=applications-getting-started-security-in-liberty

Define a user and an AES-encrypted password for administrative access using the `quickStartSecurity` element. This provides a basic level of security for server management.

```xml
<quickStartSecurity userName="Bob" userPassword="U2FsdGVkX1Y1xVwsP9LpI5b7KQ23oO7pIE4rU0k32uY=" />
```

--------------------------------

### List Installed Packages

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=uulz-installing-liberty-interim-fixes-fix-packs-zos-operating-systems

Verify the installation by listing all installed packages with their long names.

```bash
imcl listInstalledPackages -long
```

--------------------------------

### Example server.xml Configuration for Binary Logging

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=bl-configuring-binary-logging-in-liberty

This example configures binary logging with log content expiring after 96 hours and trace content retaining a maximum of 1024MB.

```xml
<server description="new server">

    <logging>
        <binaryLog purgeMinTime="96"/>
        <binaryTrace purgeMaxSize="1024"/>
    </logging>

</server>
```

--------------------------------

### Install Interim Fix with Installation Manager

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=uulz-installing-liberty-interim-fixes-fix-packs-zos-operating-systems

Command to install an interim fix for WebSphere Application Server for z/OS Liberty.

```bash
imcl install fix_name
  -installationDirectory offering_installation_location
  -repositories repository_URL_or_path
  -secureStorageFile storage_file -masterPasswordFile master_password_file
```

--------------------------------

### Install Multiple Assets

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=assets-installing-using-installutility-command

Install multiple assets by listing their shortNames separated by spaces. This command installs both 'jca-1.6' and 'adminCenter-1.0' features.

```bash
installUtility install jca-1.6 adminCenter-1.0
```

--------------------------------

### Example: Generate Controller Keystore with Hostname Option

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=keys-generating-collective-controller-ssl

This example includes the `--hostName` option, which specifies the host or DNS name used during collective creation or replication for hostname verification.

```bash
collective genKeyController --controller=Admin1:Admin1pwd@machineA:1090  --keystorePassword=kspwd --autoAcceptCertificates --hostName machineA.ibm.com
```

--------------------------------

### Start a Server on Windows

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=line-starting-stopping-server-from-command

Use the 'server.bat' script to start a server on Windows systems. Replace 'serverName' with the actual name of your server.

```batch
server.bat start serverName
```

--------------------------------

### Install a User Subsystem Archive

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=command-featuremanager

Installs a subsystem archive as a user feature. Use this to add custom or third-party features to your Liberty installation.

```bash
featureManager install my_feature.esa --to=usr
```

--------------------------------

### Start Collective Controller

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=collective-removing-controller-from-liberty-replica-set

If the collective controller is not running, start it using the `start` or `run` command. Replace `myController` with the actual name of your controller.

```shell
wlp/bin/server start myController
```

--------------------------------

### Setup Command for Single Collective

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=collectives-dynamic-routing-command

Use this command to generate WebSphere plug-in configuration files and a keystore for a single collective. Ensure all required arguments are provided.

```bash
./dynamicRouting setup --port=9444 --host=controller1.acme.com --user=admin --password=password --keystorePassword=keypass --pluginInstallRoot=/opt/HTTPServer_Plugins --webServerNames=webServer1,webServer2
```

--------------------------------

### Install Fix Pack with Installation Manager

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=uulz-installing-liberty-interim-fixes-fix-packs-zos-operating-systems

Command to install a fix pack for WebSphere Application Server for z/OS Liberty, with options for features and repositories.

```bash
imcl install offering_ID_offering_version,optional_feature_ID
  -installationDirectory offering_installation_location
  -properties user.useLibertyRepository=[true|false],user.addon=addon_shortOrSymbolicName,user.feature=feature_shortOrSymbolicName
  -repositories repository_URL_or_path,Liberty_asset_repository_URL_or_path
  -secureStorageFile storage_file -masterPasswordFile master_password_file
  -acceptLicense
```

--------------------------------

### Install osgiAppConsole-1.0 Feature

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=liberty-troubleshooting-osgi-applications-by-using-developer-tools

Install the osgiAppConsole-1.0 feature from the Liberty Repository if it is not already present. This command is run from the Liberty installation's bin directory.

```bash
bin\installUtility install osgiAppConsole-1.0
```

--------------------------------

### Install Features from Local Directory Offline

Source: https://www.ibm.com/docs/en/was-liberty/zos?topic=command-featuremanager

Installs features strictly from a local directory. Missing dependencies will not be downloaded from the Liberty Repository, enforcing an offline installation.

```bash
featureManager install feature_shortName --location=c:\temp\download --offlineOnly
```