This topic highlights what is new or changed, for users who are going to customize, administer, monitor, and tune production server environments. It also addresses those who are going to deploy and operate applications.
-
Administering OSGi applications
The OSGi Applications
support in WebSphere® Application
Server helps you to develop and deploy modular applications that use
both Java EE and OSGi technologies.
This enables the same, or different, applications to use different
versions of the same third party libraries without interference. You
can configure a business-level application to contain an OSGi application,
you can maintain the bundle versions used by an OSGi application,
and you can administer bundles and bundle repositories.
-
Administrative job types using wsadmin scripting
- The system administrator
can use the runCommand job of the job manager to run a command on
a remote host. The command might be a command-line utility such as startServer in
a
app_server_root
/bin directory,
a wsadmin command, or an operating system command.
- The system administrator
can use the manageprofiles job of the job manager to create, augment,
or delete a
WebSphere Application Server profile.
This job runs the manageprofiles administrative
command.
- The
system administrator can use Installation Manager jobs to install
Installation Manager instances, update Installation Manager with a
repository, manage Installation Manager offerings, and install
WebSphere Application Server products.
-
Audit service provider settings
- In this
release
of
WebSphere Application Server, there
are new customizable options available when specifying the default
audit log wrapping behavior. This is only applicable to the Binary
Audit Log implementation.
Choose from one of the following options:
- WRAP
- If you select this option, when the maximum
audit logs are reached,
the oldest audit log is rewritten; notification is not sent to the
auditor. This is the default option, and mimics the default behavior
in
WebSphere Application Server Version
7.0.
- NOWRAP
- This option does not
rewrite over the oldest audit log. It stops
the audit service, sends a notification to the SystemOut.log,
and quiesces the application server.
- SILENT_FAIL
- This option does not rewrite over the oldest audit log. It also
stops the audit service, but does allow the WebSphere process to continue.
Notifications are not posted in the SystemOut.log.
Note: If
audit notification of failures in the audit subsystem is configured,
and SILENT_FAIL is selected, the auditor is not notified of the audit
subsystem failure. The SILENT_FAIL option takes precedence
Note: If you use the NOWRAP or SILENT_FAIL options,
when the server is stopped as a result of the logs being maxed-out,
a stopserver is performed, or because the server abends in some way,
you must archive the binary audit logs before you restart the server.
-
Collecting Java dumps and core files using the administrative console
The Java virtual machine (JVM) is capable of producing Java dump and core files to aid
in troubleshooting. You can use heap dump and system dump files to
help you diagnose memory-related problems, such as memory leaks. You
can use Java core files to help
you diagnose problems where the CPU is persistently 100% busy, when
threads are hanging, or where threads are in a deadlock.
-
Communications Enabled Applications concepts
You can take advantage
of integrated telephony and collaborative web services to extend the
interactivity of Enterprise and web commerce applications. With the
CEA capability, Enterprise solution architects and developers can
use a single core application to enable multiple modes of communication.
Enterprise developers do not need to have extensive knowledge of telephony
or Session Initiation Protocol (SIP) to implement CEA. The CEA capability
delivers call control, notifications, and interactivity and provides
the platform for more complex communications.
-
CustomProperties policy and binding properties
This product supports using CustomProperties
policy and binding to set generic properties that are not supported
in other policy types. The additional properties are set in the binding.
You must only update existing properties, such as the enabled attribute,
in the policy. The CustomProperties policy provides an alternative
way to set a binding property instead of using the JAX-WS programming
model to set the property on the BindingProvider object. The CustomProperties
binding is only supported for service clients.
-
Disabling WebSphere MQ functionality in WebSphere Application Server
When a
WebSphere Application Server process or an
application client process starts, and while this process is running,
an amount of processing is performed to allow it to support WebSphere MQ-related functionality
such as the WebSphere MQ
messaging provider. By default this processing is performed regardless
of whether any WebSphere MQ-related
functionality is ever used. If you do not need to take advantage of
any WebSphere MQ functionality,
it is possible to disable all WebSphere MQ
functionality in an application server or client process to give increased
performance.
-
Dynamic cache provider for the JPA 2.0 second level cache
A dynamic cache JPA
second level (L2) cache provider for JPA 2.0 shares entity states
across various persistence contexts, transactions and users. When
caching is enabled, entities that are not found in the persistence
context are loaded from the L2 cache. L2 caching avoids database access
for currently-loaded entities. For more details about L2 caching,
view the JPA 2.0 specification.
-
External high availability frameworks and service integration
To provide
high availability for a
WebSphere MQ queue
manager connected to
WebSphere Application Server,
you can specify multiple connection names in your
WebSphere Application Server definition for the
WebSphere MQ link sender channel. If
the active gateway queue manager fails, the service integration bus
can use this information to reconnect to a standby gateway queue manager.
-
High Performance Extensible Logging (HPEL)
- HPEL provides a convenient mechanism for storing
and accessing log, trace, System.err, and System.out information produced
by the application server or your applications. It is an alternative
to the basic log and trace facility, which provided the JVM logs,
diagnostic trace, and service log files commonly named SystemOut.log/SystemErr.log,
trace.log, and activity.log.
- HPEL has been designed and tested to significantly
outperform the existing basic log and trace facility. One result is
that the application server can run with trace enabled while causing
less impact to performance than tracing the same components using
basic logging. Another result is that applications that frequently
write to the logs might run faster with HPEL. A number of factors
contribute to the overall performance of HPEL logging and tracing.
- HPEL has
been designed to be easy to configure and understand. For example,
administrators can easily configure how much disk space to dedicate
to logs or trace, or how long to retain log and trace records, and
leave the management of log and trace content up to the server. As
another example all log, trace, System.out, and System.err content
can be accessed using one easy-to-use command (LogViewer), avoiding
any possible confusion over which file to access for certain content.
- HPEL has been
designed to make working with log and trace content more flexible
and effective than the basic logging facility. Log and trace content
can be easily filtered to show only the records that are of interest.
You can use the command line (see the description of the HPEL LogViewer
command), or developers can create powerful log handling programs
using the HPEL API.
-
Hung threads in Java Platform, Enterprise Edition applications
An application server monitors the
activity of threads on which system alarms execute. When a system
alarm thread has been active longer than the time defined by the alarm
thread monitor threshold, the application server logs the following
warning in the system log. This message indicates the name of the
thread that is not responding, the length of time that the thread
has already been active, and the exception stack of the thread, which
identifies the system component.
-
Implementing RESTful views of EJB applications using JAX-RS
JAX-RS supports the use of enterprise beans that
declare a local business interface and no-interface view enterprise
beans.
-
Interoperation using the WebSphere MQ messaging provider
-
WebSphere Application Server Version 8.0 provides first class
support for connecting to multi-instance
WebSphere MQ queue managers. You can
provide host and port information in the form of a connection name
list, which a connection factory or activation specification uses
to connect to a multi-instance queue manager.
-
Version 8.0 exposes
WebSphere MQ queue or topic destination
properties allowing you to specify:
- Whether an application processes the RFH version 2 header of a
WebSphere MQ message as part of the JMS
message body.
- The format of the JMSReplyTo field.
- Whether an application can read or write the values of MQMD fields
from JMS messages that have been sent or received using the
WebSphere MQ messaging provider.
- Which message context options are specified when sending messages
to a destination.
-
Version 8.0 makes available the
following four
WebSphere MQ connection
properties that are used to configure the
WebSphere MQ resource adapter used by
the
WebSphere MQ messaging provider.
These properties affect the connection pool that is used by activation
specifications:
- maxConnections
- connectionConcurrency (Setting
this property only affects
WebSphere Application Server 7 nodes. The property
has no effect for
WebSphere Application Server Version
8 nodes.)
- reconnectionRetryCount
- reconnectionRetryInterval
-
JAXB
This
version of the application server supports the JAXB 2.2 specification.
JAX-WS 2.2 requires JAXB 2.2 for data binding. JAXB 2.2 provides minor
enhancements to its annotations for improved schema generation and
better integration with JAX-WS.
-
JAX-WS
Version
8.0 supports the JAX-WS Version 2.2 and Web Services for Java EE (JSR 109) Version 1.3 specifications.
The
JAX-WS 2.2 specification supersedes and includes functions within
the JAX-WS 2.1 specification. JAX-WS 2.2 adds client-side support
for using WebServiceFeature-related annotations such as @MTOM, @Addressing,
and the @RespectBinding annotations. JAX-WS 2.1 had previously added
support for these annotations on the server. There is also now the
ability to enable and configure WS-Addressing support on a client
or service by adding WS-Policy assertions into the WSDL document.
In addition, the Web Services for Java EE
1.3 specification introduces support for these WebServiceFeature-related
annotations, as well as support for using deployment descriptor elements
to configure these features on both the client and server. JAX-WS
2.2 requires Java Architecture
for XML Binding (JAXB) Version 2.2 for data binding.
-
JCA 1.6 support for annotations in RAR modules
- The Java Connector Architecture (JCA) Version 1.6
specification adds support for Java annotations
in resource archive (RAR) modules. Annotations are a means of specifying
metadata, or configuration data, for a RAR module in the class files
that make up the module.
- The
JCA Version 1.6 specification also adds support for Bean Validation
constraint annotations in RAR modules. You can specify Bean Validation
constraint metadata for RAR JavaBeans by
decorating your classes with Bean Validation constraint annotations
or by supplying XML validation descriptors. The Application Server
validates the constraints of all JCA 1.6 RAR JavaBeans instances before placing them
into service at run time.
-
Job manager
You
can complete job manager actions and run jobs from a deployment manager.
The deployment manager administrative console has Jobs navigation
tree choices similar to those in the job manager administrative console.
-
JobManagerNode command group for the AdminTask object using wsadmin scripting
- Use commands and parameters
added in Version 8.0 to the JobManagerNode command group to register
targets that do not contain an administrative agent with the job manager.
The new commands have Target in the command names: cleanupTarget, queryTargets, getTargetProperties, modifyTargetProperties,
and getTargetKeys. These commands replace deprecated
commands that have ManagedNode in the command names.
- Use the registerHost command
to:
- Register a remote host target with the job manager. Unlike targets
that are
WebSphere Application Server profiles
and are registered using the registerWithJobManager command
at the deployment manager or administrative agent, a remote host target
is not required to have any
WebSphere Application Server products installed.
There are no software requirements for this host beyond its operating
system.
- Collect an inventory of the remote host. Information regarding
managed resources and job types is available upon successful completion
of the registerHost command.
You can work with remote host targets the same as those that
are registered using registerWithJobManager, but
the types of jobs available to a remote host target are different.
- Use the unregisterHost command
to unregister a remote host target from the job manager. After a host
is unregistered, the job manager cannot run jobs on the target.
-
JSR 289 overview
Version 8.0 includes support
for SIP Servlet Specification 1.1, also referred to as Java Specification Request (JSR) 289.
-
Lookup names support in deployment descriptors and thin clients
Beginning
in Version 8.0, EJB homes are bound under the name, java:global/appName/moduleName/beanName
.
Names of that form are not topology-based and are fully-qualified
already. Similarly, all application resources that are bound with java:global, java:app,
or java:module names need no additional qualification
when the java:global, java:app,
or java:module lookup name is specified. Application
resources include, for example, EJB references, resource references,
and environment entries.
-
managesdk command
Use the
managesdk command
to:
- List the software development kit (SDK) names that are available
to a product installation.
- List the SDK names that a specified profile is currently configured
to use.
- For each profile in a product installation, list the SDK names
that the profile is currently configured to use.
- Enable a profile to use a specified SDK name.
- Enable all profiles in an installation to use a specified SDK
name.
- Get the SDK name that is used to configure new profiles.
- Change the default SDK name that profiles use.
- Get the SDK name that is used by scripts called from a product bin directory.
- Change the SDK name that scripts in a product bin directory
use by default. The SDK name is used when no existing profile name
is specified and the default profile name is not applicable.
-
Managing policy set attachments for service references using the wsadmin tool
In Version 8, you can specify
a policy set and binding for a service reference that is different
from the policy set attachment for the service. In addition, you
can indicate to not attach a policy set to a service reference, even
if a policy set is attached to the service. The default behavior is
that a service reference, as well as its endpoints and operations,
inherits the policy set attachment of the corresponding resources
of the service. Service references are only valid for the client attachment
type.
-
Managing policy sets and bindings for services references using the administrative console
When you configure the
policy set attachments for a service reference, you can override the
policy set attachments that are inherited from the service client
using the administrative console. You can attach a policy set and
binding for a service reference that is different from the policy
set attachment for the service client. You can also specify to not
attach a policy set to a service reference, even if a policy set is
attached to the service client.
-
Managing self-issue SAML token configuration using wsadmin commands
Two command
tasks are available to manage the
SAMLIssuerConfig.properties file-based
SAML issuer configuration. This file can be located at the cell level
and the server level. These two tasks are:
-
listSAMLIssuerConfig
-
updateSAMLIssuerConfig
-
Options for the AdminApp object install, installInteractive, edit, editInteractive, update, and updateInteractive commands using wsadmin scripting
- The clientMode option specifies
whether to deploy client modules to an isolated deployment target
(isolated), a federated node of a deployment manager
(federated), or an application server (server_deployed).
If you specify this option, install the client modules only onto a
Version 8.0 deployment target.
- The enableClientModule
option specifies to deploy client modules. Select this option if the
file to deploy has one or more client modules that you want to deploy.
If you select this option, install the client modules only onto a
Version 8.0 deployment target.
- The validateSchema option
specifies to validate the deployment descriptors against published
Java EE deployment descriptor schemas. When this application deployment
option is selected, the product analyzes each deployment descriptor
to determine the Java EE specification version for the deployment
descriptor, selects the appropriate schema, and then checks the deployment
descriptor against the Java EE deployment descriptor schema. Validation
errors result in error messages.
-
Overview of IBM JAX-RS
JAX-RS is a collection
of interfaces and Java annotations
that simplifies development of server-side REST applications. By using
JAX-RS technology, REST applications are simpler to develop, simpler
to consume, and simpler to scale when compared to other types of distributed
systems. This product supports a Java API
for developing REST-based services. The IBM® implementation
of JAX-RS provides an implementation of the JAX-RS specification.
-
Policy set bindings settings for Custom properties
This product supports
using the Custom properties policy and binding to set generic properties
that are not supported in other policy types. The additional properties
are set in the binding. The Custom properties policy provides an alternative
way to set a binding property instead of using the JAX-WS programming
model to set the property on the BindingProvider object. You cannot
create an empty Custom properties binding. You must define at least
one name and value pair within the binding. Additionally, there are
no predefined properties in the binding because all properties are
user-defined. The CustomProperties binding is only supported for service
clients.
-
Querying web services using wsadmin scripting
Use the listServices command to learn about service
references. You can use the serviceRef property with
the queryProps parameter with the listServices command to query all
service references or a specific service reference. This parameter
is only applicable for service clients. If you specify an asterisk
(*) as a wildcard as the name of the service reference,
all of the service references for the matching service client are
returned. You can also query a specific service reference name by
specifying the name of the service reference that you want. To return
detailed service reference information for endpoints and operations,
specify the expandResource property.
-
Recovering or moving nodes with the addNode -asExistingNode command
Use the -asExistingNode option
of the addNode command to quickly recover a damaged
node, to move a node to a product installation on a different computer
but at the same path, to move a node to a product installation on
a different operating system or with a different path, or to create
cells from a template cell.
-
Resource workload routing
Resource workload
routing includes data source and connection factory fail over and
subsequent fail back from a predefined alternate or backup resource.
This function enables applications to easily recover from resource
outages, such as database failures, without requiring you to embed
alternate resource and configuration information. You can tailor the
resource fail over and failback flexible configuration options to
meet your environment-specific and application needs.
-
Single sign-on settings
The Set security
cookies as HTTPOnly to resist cross-site scripting attacks check box
has been added to the Single sign-on settings page for this release.
The HttpOnly attribute is a browser attribute created to prevent client
side applications (such as Java scripts) from accessing cookies to
prevent some cross-site scripting vulnerabilities. The attribute specifies
that LTPA and WASReqURL cookies include the HTTPOnly field.
-
Submitting Installation Manager jobs
For Version 8.0, centralized installation manager
(CIM) functions are accessed through the job manager. Using the job
manager, you can perform the following functions:
- Install, update, and uninstall
WebSphere Application Server offerings on remote
machines
- Install, update, and uninstall IBM Installation
Manager on remote machines. Not supported on z/OS targets. For z/OS
targets, you must install Installation Manager prior to working with
CIM.
- Collect, distribute, and delete files on remote hosts
- Run scripts on remote hosts
-
Submitting jobs to install Installation Manager on remote hosts
You can
install Installation Manager so that it can be used by a group of
users. Specify the following optional parameter:
installType
Values:
- single: perform a single user installation in non administrative
mode. This option is available for all CIM supported platforms.
- Auto: the command initiates a single user installation in non
administrative mode if your are a non administrative user. If you
are an administrator, this action performs an administrative installation.
-
TargetGroup command group for the AdminTask object using wsadmin scripting
Use the commands and parameters
in the TargetGroup command group to create and manage target groups.
Create target groups to submit jobs from the job manager to one or
many targets. Commands in the TargetGroup command group provide function
that replaces deprecated commands in the ManagedNodeGroup command
group.
-
Task overview: Implementing web services applications
Version 8.0 includes
support for singleton session enterprise beans as JAX-WS endpoints.
Singleton session beans are useful in situations where a single instance
of a web services endpoint implementation bean is needed to process
all requests that are received for a particular web services endpoint.
Perhaps, the single instance of the bean needs to share state information
across requests. Typically, a new instance of a web services endpoint
implementation bean is created to process each request.
-
Using application properties files to install, update, and delete enterprise application files
To enhance the output of application properties,
run the AdminTask
extractConfigProperties command
with the
SimpleOutputFormat option. When the option
is set to
true, the output displays non-hidden columns
of application properties in
columnName=value
pairs.
Hidden columns of application properties are not included in the output.
The enhanced output makes it easier for you to find and edit application
property values. You can use an edited properties file to install
or update an application. The following example specifies the
SimpleOutputFormat option
in the
extractConfigProperties command:
AdminTask.extractConfigProperties('[-propertiesFileName myApp.props -configData Application=MyApplication
-option [[SimpleOutputFormat true]]]')
-
Using Java contexts and dependency injection with JAX-RS
Java Contexts and Dependency Injection (JCDI)
is a new Java Platform, Enterprise
Edition (Java EE) 6 feature.
It can change the programming model to make applications easier to
develop while increasing maintainability. JAX-RS developers can use
JCDI features, such as @javax.inject.Inject support,
in root resource and provider classes.
-
Using WADL to generate service documentation
WADL is a developing standard which helps describe
the services available to users. WADL documents are written in XML.
Using XSTL or XML parsers, developers can generate documentation for
the service. In some cases, users may develop clients to dynamically
understand the RESTful service by inspecting the WADL document.
Using IBM JAX-RS, developers can generate
a JAXB XML representation of a WADL document describing all of the
resources available in the application. The JAXB representation can
be returned from a JAX-RS resource method. Then, the WADL document
resource is treated like any other JAX-RS resource and can be used
by clients.
-
Web container custom properties
- When you configure
server security, you can turn off the X-Powered-By header if you do
not want to reveal which server you are running. Use this custom
property to disable the X-Powered-By header, which prevents the header
from being sent on the HTTP response. The default value is false.
However, set this property to true, if you
want to disable this header.
- When you configure
an application to use a cookie to track the session, the default path
for the cookie is set to the context root of the application. Therefore,
the cookie is only sent to requests that are made to this application.
To change the default path to be "/" (forward slash), such that the
cookie is sent to requests for any application in this domain, set
the ForceDifferentCookiePaths session manager custom property.
- When examining
the classes of an application to see if they match any of the criteria
that is specified by the HandlesTypes annotation of a ServletContainerInitializer,
the container might run into class loading problems if one or more
of the optional application JAR files are missing. Because the container
does not decide whether these types of class loading failures prevent
the application from working correctly, it ignores the failures and
provides a configuration option that logs them.
- This custom property
enables you to configure the value of the X-Powered-By header, which
supplies the implementation information of the server.
-
Web fragments
Web module deployment
descriptor fragments (web fragments) provide the same configuration
metadata that a web.xml file provides, but they exist as a web-fragment.xml
file that is packaged inside a JAR file in the WEB-INF/lib directory.
Framework
developers provide JAR files that are included in a web application
which uses that specific framework. If that framework uses servlets,
filters, or other web module configuration, web fragments provide
the ability to simply drag the JAR file into an application without
requiring changes to the existing web module configuration. Previously,
web application developers were required to augment their configuration
with additional metadata required by the framework. Another use case
is the aforementioned need to use the same components across web modules.
Also, the use of mock objects or stubs might be made easier with Web
fragments.
-
Web service clients and policy configuration to use the service provider policy
In
WebSphere Application Server Version 8.0, a
service reference can be configured to use a different WSDL document
to the WSDL configured for the client service. By default, service
references inherit their policy set and WS-Policy configuration from
their parent service, however, if desired, the policy set and WS-Policy
configuration can be overwritten. See the Using WS-Policy to exchange policies in a standard format topic and its child topics for further details.
-
Web Services Addressing support
The following
features were introduced in the JAX-WS 2.2 specification, which
WebSphere Application Server Version 8 supports:
- You can specify additional binding information within the metadata
of an endpoint reference as part of the JAX-WS 2.2 specification.
This functionality was added to
WebSphere Application Server in version 7,
however as it was not part of the JAX-WS 2.1 specification, you might
have experienced incompatibility issues when interoperating with non-
WebSphere Application Server servers which
did not offer support for additional metadata in endpoint references.
Now that JAX-WS 2.2 supports WSDL metadata in endpoint references,
applications will be compatible with other implementations of this
specification. See the "Web Services Addressing overview" topic for
further information.
- You can enable and configure WS-Addressing
on a client or service
by adding WS-Policy assertions into the WSDL document.
WebSphere Application Server will now process
WS-Addressing information held within the WS-Policy aspect of a WSDL
document and use it in the configuration of that application. See
the "Enabling Web Services Addressing support for JAX-WS applications
using WS-Policy" topic for further information.
- You can specify
whether a synchronous or an asynchronous message
exchange pattern is required by a web service application using the
addressing annotation or the AddressingFeature. Use the new responses parameter
on the addressing annotations or the AddressingFeature class in the
code. See the "Enabling Web Services Addressing support for JAX-WS
applications using addressing annotations" topic and the "Enabling
Web Services Addressing support for JAX-WS applications using addressing
features" topic for further information.
- You can configure
WS-Addressing using deployment descriptors.
Add an <addressing> element and optional child
elements to the deployment descriptor file for the application. See
the "Enabling Web Services Addressing support for JAX-WS applications
using deployment descriptors" topic for further information.
- You
can generate code from a WSDL document and
WebSphere Application Server will now automatically
insert @Action and @FaultAction annotations into the generated Java
code. See the "Web Services Addressing annotations" topic for further
information.
-
What is new for securing web services
The Security
Assertion Markup Language (SAML) is an XML-based OASIS standard for
exchanging user identity and security attributes information. Using
SAML, a client can communicate assertions regarding the identity,
attributes, and entitlements of a SOAP message. Using the SAML function
in
WebSphere Application Server, you can
apply policy sets to JAX-WS applications to use SAML assertions in
web services messages and in web services usage scenarios. Use SAML
assertions to represent user identity and user security attributes,
and optionally, to sign and to encrypt SOAP message elements.
-
Working with web services endpoint URL fragment property files
Version
8.0 supports using property files to manage endpoint URL fragments
for web services accessed through HTTP, SOAP and Java Message Service (JMS), or directly as enterprise
beans.
-
WS-Policy
The following
features were introduced in the JAX-WS 2.2 specification, which
WebSphere Application Server Version 8 supports:
- You can specify transport level security on client WSDL acquisition.
You can now attach a system policy set to either an HTTP GET request
or a WS-MetadataExchange request when obtaining provider policy. See
the "Configuring the client policy to use a service provider policy"
topic for further information.
- You can specify a policy set
and binding for a service reference
that is different from the policy set attachment for the service.
By default, service references inherit their policy set and WS-Policy
configuration from their parent service, however, if desired, the
policy set and WS-Policy configuration can be overwritten. See the
"Using WS-Policy to exchange policies in a standard format" topic
and its child topics for further details.
- You can enable and
configure WS-Addressing support on a client
or service provider by adding WS-Policy assertions into the WSDL document.
WebSphere Application Server will now process
WS-Addressing information held within the WS-Policy aspect of an application's
WSDL document and use it in the configuration of that application.
See the "Enabling Web Services Addressing support for JAX-WS applications
using WS-Policy" topic for further information.
- You can publish
policy configuration relating to WS-Addressing
based on JSR109 deployment descriptors or JAX-WS 2.2 features or annotations,
as well as information based on policy sets. This ensures that the
policy information published matches the run time behavior of the
service. See the "Web service providers and policy configuration sharing"
topic for further information.