IBM WebSphere Application Server (WAS) 7.0 before 7.0.0.41, 8.0 before 8.0.0.13, and 8.5 before 8.5.5.10, when FIPS 140-2 is enabled, misconfigures TLS, which allows man-in-the-middle attackers to obtain sensitive information via unspecified vectors. This course introduces developers and administrators to the WebSphere Application Server 8.5.5 Liberty Profile. The Liberty profile is a lightweight, dynamic profile that enables the server to provide only the features that the deployed application requires.

• Download Websphere Application Server 8.5
• Websphere Application Server 8.5
• Websphere Application Server V7
• Websphere Application Server 8.5.5.9

WebSphere Application Server (WAS) is a software product that performs the role of a web application server. More specifically, it is a software framework and middleware that hosts Java-based web applications. It is the flagship product within IBM's WebSphere software suite. It was initially created by Donald F. Ferguson, who later became CTO of Software for Dell. The first version was launched in 1998. This project was an offshoot from IBM HTTP Server team starting with Domino Go (Web Server).

• 2Version history

WebSphere Application Server (Distributed and IBM i operating systems), Version 8.5.5 documentation View the latest WebSphere® Application Server documentation. This information applies to the Version 8.5.5 full profile and to all subsequent releases and modifications until otherwise indicated in new editions. Install IBM WebSphere Application Server 8.5.5 ND Install IBM WebSphere Application Server 8.5.5 ND In this part you will learn howto Install IBM WebSphere Application Server 8.5.5 ND in RHEL 6.3, but with this knowledge you can install it over others Linux, Unix or Windows. WebSphere Application Server Fix Pack 8.5.5.8 content is provided as below: WebSphere Application Server Full Profile. WebSphere Application Server Liberty Using archives Archives with all features. Convenience ZIP files with Java™ EE 7 content. Edition-specific archives. License upgrade archives. Directory-based repository for working offline. Each queue manager that is a member of the shared queue group has access to any of the shared queues. 32 WebSphere Application Server V8.5 Concepts, Planning, and Design Guide. When a default messaging application sends a message to a WebSphere MQ queue, the message is immediately added to that queue. WebSphere Application Server V8.5 offers the same Java EE 6 and Java SE 6 (by default) as V8.0 and also provides - and can be configured to run on - Java SE 7. The primary new capabilities in V8.5 are the Liberty profile of WebSphere Application Server and the intelligent management features.

Architecture[edit]

WebSphere Application Server (WAS) is built using open standards such as Java EE, XML, and Web Services. It is supported on the following platforms: Windows, AIX, Linux, Solaris, IBM i and z/OS. Beginning with Version 6.1 and now into Version 9.0, the open standard specifications are aligned and common across all the platforms. Platform exploitation, to the extent it takes place, is done below the open standard specification line.

It works with a number of Web servers including Apache HTTP Server, Netscape Enterprise Server, MicrosoftInternet Information Services (IIS), IBM HTTP Server for i5/OS, IBM HTTP Server for z/OS, and IBM HTTP Server for AIX/Linux/Microsoft Windows/Solaris. It uses port 9060 for connection as the default administration port and port 9080 as the default website publication port. In case you install more WebSphere instances these values will be changed.

The 'traditional' (as opposed to the Liberty variant) WebSphere Application Server platform is architected as a distributed computing platform that could be installed on multiple operating system instances, collectively referred to as a WebSphere cell. Management of all the instances could be done from a management node - called the Deployment Manager - within the cell, and deployment of applications - including the ability to perform rolling updates - could be pushed out to a subset of the cell nodes. The configuration information for the entire cell (how many nodes there are, what applications are deployed to each, how the applications are configured, session management and details of other resources, etc) are tracked in XML configuration files that are distributed throughout the cell to every node. Over the product lifetime, the implementation of these configuration details went from files, to database-based (around v3.5), and back again to files (around v5).

Given the distributed install, and given also that management of the entire cell required management of local effects (such as deployment, logging configuration, etc), the overall effect was that WAS security could often override local security if not configured properly. For example, in earlier versions of the management console, there was an option that was available to specify the location of a log file on a remote node. This could be used to read / write to an arbitrary file on that remote node. For this reason, it was not advisable to run the application server / node agent processes with root privileges, and starting with v6, security configuration defaulted out of the box to a secure state (even if this meant that enabling desired functions required manual changing of the defaults). Originally, all nodes of the cell were in a single domain for management as well as application security. However, as of v6.1, support for multiple security domains was introduced and with it, the ability to separate administrative and application security.

Many IBM products (such as IBM InfoSphere DataStage) use WebSphere Application Server as the base platform for their infrastructure.

Version history[edit]

IBM has shipped several versions and editions of WebSphere Application Server.

In the first beta versions, WebSphere had been called Servlet Express.^[15]

Although the versioning scheme x.1 and x.5 would usually indicate a minor release in the software industry, WebSphere v6.1 and v5.1 are major releases, just like WebSphere v8.5 and v3.5.^[16]

WebSphere Liberty Versions[edit]

WebSphere Liberty was introduced into WebSphere Application Server V8.5, originally referred to as the WebSphere Liberty Profile, with the same version numbering scheme as the rest of WAS. In 2016 IBM introduced a new fix pack numbering scheme for Liberty to reflect a move to continuous delivery of Liberty in a single support stream - after V8.5.5.9, the Liberty numbering scheme was rebased starting at 16.0.0.2 to reflect Year and Quarter of the Liberty fixpack release. A common level of WebSphere Liberty is distributed as part of the both Version 8.5 and Version 9.0 of WebSphere Application Server. The Liberty continuous delivery model was introduced to allow new capabilities and features to be delivered on a more frequent basis.^[17]

Version 9.0[edit]

WebSphere Application Server V9.0^[18] adds Java EE 7 and Java SE 8 (by default) and also provides - and can be configured to run on - Java SE 7. This brought WAS Application Server traditional up to the same level of Java EE as WebSphere Liberty had offered since 2015. This was the first release of WAS to be made simultaneously available as both an on-premises offering and through WebSphere as a Service on IBM Cloud.^[19]

WebSphere Liberty is increasingly the focus for new cloud native applications, with Liberty 16.0.0.2 being the version of Liberty included with WAS Version 9.0.0.0. Liberty 16.0.0.3 adds support for the new MicroProfile programming model^[20] that simplifies cloud native application development using standard Java EE technologies. Flexible access to WebSphere Liberty is provided through additional distributions as a docker image^[21] and Cloud Foundry buildpack.^[22] In September 2017 IBM moved ongoing development of Liberty into a new Open Source project called Open Liberty.^[23] Open Liberty is the source for the Liberty runtime in WebSphere Application Server. Distributions of Open Liberty are supported by the OpenLiberty.io community;^[24] IBM provides commercial support for Liberty through WebSphere Application Server.

Version 8.5.5[edit]

WebSphere Application Server V8.5.5 includes significant enhancements to the Liberty profile including support for Java SE 8, full Java EE 7 compliance since V8.5.5.6, and WebSphere's intelligent management capabilities. WebSphere Liberty's support for Java EE is enabled through the configuration of sets of features, with different sets of Library features available in each edition of WAS. The WAS Liberty Core edition includes the Liberty features required for Java EE WebProfile; all other editions of WAS add Liberty features for full Java EE 7. The WAS Network Deployment Edition adds Liberty features for intelligent management. Beyond this the WAS z/OS edition adds Liberty features to enable z/OS platform capabilities.

Version 8.5[edit]

WebSphere Application Server V8.5 offers the same Java EE 6 and Java SE 6 (by default) as V8.0 and also provides - and can be configured to run on - Java SE 7. The primary new capabilities in V8.5 are the Liberty profile of WebSphere Application Server and the intelligent management features.

The Liberty profile of WebSphere Application Server is included with all the commercial editions of the server, providing a lightweight profile of the server for web, mobile and OSGi applications. In this release it is a functional subset of the full profile of WebSphere Application Server, for both development and production use, with an install size of under 50 MB, a startup time of around 3 seconds and a new XML-based server configuration which can be treated as a development artifact to aid developer productivity. Server capabilities are engaged through the set of features defined in the server configuration; features are added and removed dynamically through internal use of OSGi services. A new model is provided for moving applications through the pipeline from development to production as a packaged server; this is a complete archive of the server, server configuration and application for unzip deploy. A centralized managed install is optionally available through the Job Manager component of WebSphere Application Server Network Deployment edition.

Intelligent management capability is added in the Network Deployment and z/OS editions of WebSphere Application server. This integrates operational features that were previously available in the separate WebSphere Virtual Enterprise (WVE) offering: application editioning, server health management, dynamic clustering and intelligent routing.

Compute Grid is also included in the Network Deployment and z/OS editions of WebSphere Application server. Previously this was the separately priced WebSphere XD Compute Grid feature for scheduling and managing Java batch workloads.^[25]

Version 7.0[edit]

This version was released on September 9, 2008. It is a Java EE 5 compliant application server.

Following are the flagship features introduced by WebSphere Application Server Version 7:

• Flexible Management

Flexible Management facilitates administration of a large number of WebSphere Application Server base edition and Network Deployment topologies that might be geographically distributed.

• Business-Level Application

Business-Level Application is used for managing application artifacts independent of packaging or programming models.

• Property Based Configuration

The Property Based Configuration feature simplifies the experience of automating administration: an administrator can update the WebSphere Application Server Version 7 configuration using a simple property file.

Between the general availability of WebSphere Application Server V7 and WebSphere Application Server V8 (in 2011), a number of additional capabilities were made available for V7 in the form of feature packs which are optionally added to a V7 install. Feature Pack content has the same quality and support as main release content - the purpose of a feature pack is to deliver new innovation before the next major release. The following feature packs were provided for WebSphere Application Server V7:

• Feature Pack for Modern Batch
• Feature Pack for OSGi Applications and JPA 2.0
• Feature Pack for SCA
• Feature Pack for Web 2.0 and Mobile
• Feature Pack for XML
• Feature Pack for Communication Enabled Applications

Version 6.1[edit]

This version was released on June 30, 2006. On September 11, 2012, IBM extended the end of service for V6.1 by a full year, to September 30, 2013, and announced new version-to-version migration incentives and assistance.^[26] It is a Java EE 1.4 compliant application server and includes the following function:

• Support for Java Standard Edition 1.5
• Support for running JSR 168Portlets in the application server
• Session Initiation Protocol (SIP) Servlets
• Enhancements to the WebSphere Install Factory
• IBM Support Assistant
• IBM JSF Widget Library
• Simplified Administration
• Improved Certificate and Key Management
• Security Enhancements
• Administration of IBM HTTP Server from WebSphere Admin Console
• Support for (pre-OASIS) WS-Security 1.0
• Support for Web Services Resource Framework and WS-BusinessActivity (WS-BA)
• Support for JSR160 JMX Remote Connections (From IBM Agents Only)
• Administrative Console Jython Command Assistance
• Enhanced scripting. This version started the deprecation process for the Jacl syntax.^[27]
• 64-bit servants and a new Apache-based IBM HTTP Server for z/OS

Support for the EJB 3.0 technology and support for some webservices standards were provided by the EJB feature pack and the webservices feature packs, respectively. These function in these feature packs has been folded into the main product in version 7. Functions in the webservices feature pack include:

• Asynchronous programming model (Limited functional support)
• Multiple Payload structures
• StAX (Streaming API for XML)
• WS-RM (Limited functional support)
• Support for (OASIS specified) WS-Security 1.0.
• WS-Addressing (Limited functional support)
• JAX-B support
• Policy Set (Limited functional support)
• Secured thin client (Limited functional support)
• SOAP (protocol) Message Transmission Optimization Mechanism (MTOM)
• Supports CGI and CORBA

Version 6.0[edit]

• This version was released on December 31, 2004. It is a Java EE 1.4 compliant application server. Security enhancements include support for JACC 1.0 and (pre-OASIS) WS-Security 1.0.
  • Support for Java Standard Edition 1.4

    Many programming model extensions previously found in WebSphere Application Server V5.0 Enterprise Edition were moved out of enterprise and into Express and Base. These APIs included application profile, startup beans, the scheduler, and async beans.

    The JMS engine, now called 'WebSphere Platform Messaging,' was rewritten in 100% Java and its functionality greatly enhanced. (WebSphere MQ is still supported as the JMS provider and is interoperable with WebSphere Platform Messaging.)

    The clustering was rewritten to use the high availability manager. This manages all singletons in the WebSphere environment and can provide hot recovery for those singletons.

    WebSphere was modified so that a shared file system can be used to store transaction logs and this meant that any cluster member with that shared file system mounted can hot recover in-doubt XA transactions with no external HA software.

    The Deployment Manager's role was eliminated from all clustering runtime operations. It's only required for centralized JMX admin and config changes.

    Now supports running mixed version cells (V5 to V6) in production.

  • WebSphere Application Server for z/OS

    Provides the same core functionality as Network Deployment, since it shares a common programming model, but still contains the platform advantages such as:

    • z/OS Workload Manager for prioritized management of mixed workloads
    • Resource Recovery Services (added transactional integrity for complex, critical transactions)
    • Support for security mainframe products such a RACF
    • Advanced vertical scaling for application server by featuring a unique control region (integrated control area) server region (where workloads are completed) separation which enables the control region to open and close server regions as needed by the volume of incoming requests
    • Parallel Sysplex support for full participation in the Sysplex, enabling advanced failover support and a geographically dispersed environment that seamlessly acts as one with a centralized logging and management facility

    WAS XD as it is known increases the functionality of the application server in two main areas - Manageability and Performance. It also allows makes possible new configurations, such as dynamic virtualization between pools of application servers.

    Under the performance header the ObjectGrid component was added, which is a standalone distributed cache that can be used with any application server (any version with a 1.4 JDK) or with any J2SE 1.4 runtime, including zLinux and z/OS support.

  • Community Edition

    Code based on Apache Geronimo project

With Version 6, some of the functionality previously found in WebSphere Business Integration Server Foundation (WBISF) moved into the new IBM WebSphere Process Server. Other function moved into the other editions (Express and above).

Version 5.1[edit]

This version was released on January 16, 2004. It is a J2EE 1.4 compliant application server.

• Express
• Base
• Network Deployment
• WebSphere Application Server for z/OS

  Version 5.1 for z/OS is the first to support zAAP engines.

• WebSphere Business Integration Server Foundation V5.1

  This is the follow on product to WebSphere Application Server Enterprise Edition V5.0. The workflow engine was updated to support BPEL rather than the proprietary FDML format used in V5.0. The product was also repriced and available on all IBM platforms from the Intel environments to the mainframe.

• WebSphere eXtended Deployment (XD)

Version 5.0[edit]

Download Websphere Application Server 8.5

The version released on November 19, 2002. This was a J2EE 1.3 certified application server. It was a major rewrite of the V3/V4 codebase and was the first time WebSphere Application Server was coded from a common codebase. Now WAS across all deployment platforms, from Intel x86 to the mainframe, are substantially the same code. The database-based configuration repository was replaced with a replication XML file-based configuration repository. A service called the Deployment Manager had the master copy of the cell configuration, and nodes had the file(s) they needed copied from this master server whenever they changed. V5 also included a miniature version of MQ 5.3 called the embedded Java Message Service (JMS) server.

• Express Edition replaces the Standard Edition. Express now becomes the term to indicate SME-oriented offerings from IBM, across all its software brands.
• Base
• Network Deployment. This version supports deployment of a cell configuration with cluster and J2EE failover support. It now also includes Edge Components, previously known as Edge Server. This provides a proxy server, load balancing, and content-based routing.
• Enterprise Edition. This version added a workflow engine, called the Process Choreographer, for the first time but predates the BPEL standard. It also added the first fully supported application threading model called WebSphere Asynchronous Beans.
• WebSphere Application Server for z/OS. This version is essentially the same as the Network Deployment product but is optimized to take full advantage of z/OS features, such as Workload Manager, to leverage the key technologies that make the mainframe indispensable for mission-critical, scalable, and secure workloads.

Version 4.0[edit]

This was a J2EE 1.2 certified application server. It inherited the database-based configuration model from V3.x for all but the single-server edition, which already used an XML datastore.

• AE (Advanced Edition)
• AEs (Advanced Edition single). Single-server edition that was not able to run in a cluster configuration.
• AEd (Developer Edition). Functionally equivalent to AEs, but intended only for non-production development use.
• EE (Enterprise Edition)

Version 3.5 (and 3.0)[edit]

WebSphere 3.5 is the first widely used version of WebSphere.

Version 2.0[edit]

IBM adds JavaBean, CORBA and Linux support. Comes in two editions: Standard Edition (SE) and Advanced Edition (AE).

Version 1.0[edit]

Initial release in June 1998. Was primarily a Java Servlet engine.

Security[edit]

The WebSphere Application Server security model is based on the services provided in the operating system and the Java EE security model.WebSphere Application Server provides implementations of user authentication and authorization mechanisms providing support for various user registries:

• Local operating system user registry
• LDAP user registry
• Federated user registry (as of version 6.1)
• Custom user registry

The authentication mechanisms supported by WebSphere are:^[28]

• Lightweight Third Party Authentication (LTPA)

See also[edit]

• zSeries Application Assist Processor zAAP

Other Java EE application servers:

• Apache Geronimo/Tomcat

References[edit]

1. ^ ^ab'IBM Support - WebSphere software lifecycle'. www-01.ibm.com. September 27, 2017. Retrieved September 29, 2017.
2. ^'WebSphere Application Server detailed system requirements'. Retrieved September 29, 2017.
3. ^'IBM Knowledge Center: Programming model APIs and specifications'.
4. ^'WebSphere product lifecycle dates'.
5. ^'IBM US Announcement Letter'. www-01.ibm.com. April 24, 2012. Retrieved September 29, 2017.
6. ^'To 16.0.0.2 and beyond: Liberty continuous, single-stream fix pack delivery - WASdev'. WASdev. June 24, 2016. Retrieved August 10, 2017.
7. ^'IBM support - Software lifecycle - WebSphere Application Server 8.0.x'. www-01.ibm.com. September 29, 2017. Retrieved September 29, 2017.
8. ^'IBM support - Software lifecycle - WebSphere Application Server 7.0.x'. www-01.ibm.com. September 29, 2017. Retrieved September 29, 2017.
9. ^'Extension of end-of-service date: IBM WebSphere Application Server V6.1'. www-01.ibm.com. September 11, 2012. Retrieved September 29, 2017.
10. ^'IBM 8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 - United States'. www-01.ibm.com. September 8, 2017. Retrieved September 29, 2017.
11. ^'IBM Knowledge Center'. pic.dhe.ibm.com. Retrieved September 29, 2017.
12. ^'IBM Knowledge Center'. www.ibm.com. Retrieved August 10, 2017.
13. ^'IBM Utility: Feature Pack for EJB 3.0 for WebSphere Application Server V6.1 - United States'. www-01.ibm.com. December 3, 2007. Retrieved September 29, 2017.
14. ^'IBM Knowledge Center'. www.ibm.com. Retrieved August 10, 2017.
15. ^'Whatever Happened to ... WebSphere?'. www.serverwatch.com. Retrieved September 29, 2017.
16. ^'IBM Update Strategy for WebSphere Application Server V6.1 - United States'. www-01.ibm.com. September 14, 2007. Retrieved September 29, 2017.
17. ^[1], To 16.0.0.2 and beyond: Liberty continuous, single-stream fix pack delivery.
18. ^'What's new in WebSphere Application Server V9?'.
19. ^[2], WebSphere Application Server on Cloud
20. ^[3], Eclipse MicroProfile
21. ^[4], websphere-liberty docker image
22. ^[5], Liberty for Java buildpack
23. ^[6], IBM open sources WebSphere Liberty code to support Java microservices and cloud-native apps
24. ^[7], OpenLiberty.io community]
25. ^'Improve Your Availability, Scalability and z/OS Mobile Access With WebSphere Application Server V8.5'. Retrieved August 3, 2015.
26. ^'IBM WebSphere Migration Knowledge Collection: Why Migrate? - United States'. www-01.ibm.com. November 22, 2016. Retrieved September 29, 2017.
27. ^SG24-7304-00 WebSphere Application Server V6.1: System Management and Configuration, p. 250
28. ^'IBM Redbooks - IBM WebSphere Application Server V6.1 Security Handbook'. www.redbooks.ibm.com. September 30, 2016. Retrieved September 29, 2017.

External links[edit]

• WASdev Community Site - WebSphere developer site for downloads and news

You're viewing help content for version:

• 6.3

This section includes the following steps to configureSSL with your IBM WebSphere Application Server.

For enabling SSL, WebSphere needs access to a user accountin the local OS user registry that has permission to administerthe system:

• (Windows) Create a new Windows user who is part of theAdministrators group and has the privilege to act as part of theoperating system. (See Create aWindows user for WebSphere.)

• (Linux, UNIX) The user can be a root user or another userwho has root privileges. When you enable SSL on WebSphere, use theserver identification and password of this user.

Create a user by entering the following command in a commandprompt:

Set the password of the new user by entering passwd inthe command prompt.

(Linux and Solaris) Create a shadow password file by entering pwconv (with noparameters) in the command prompt.

Note:

(Linuxand Solaris) For WebSphere Application Server Local OS security registryto work, a shadow password file must exist. The shadow passwordfile is usually named /etc/shadow and is based on the /etc/passwd file. If the shadow password file does not exist, an error occurs after enabling global security and configuring the user registry as Local OS.

Open the group file from the /etc directory in a text editor.

Add the user who you created in step 2 to the root group.

(UNIX with SSL enabled) Start and stop WebSphere as the rootuser.

Log in to Windows by using an administrator useraccount.

Select Start > Control Panel > Administrative Tools > Computer Management > Local Users and Groups.

Type a user name and password in the appropriate boxes, andtype any other information you require in the remaining boxes.

Deselect User Must Change Password At Next Login,click Create, and then click Close.

Click Users, right-click the user you just createdand select Properties.

In the Enter The Object Names To Select box, type Administrators,click Check Names to ensure that the group name is correct.

Select Start > Control Panel > Administrative Tools > Local Security Policy > Local Policies.

Click User Rights Assignment, and then right-click Act asPart of the Operating System and select Properties.

In the Enter The Object Names To Select box, type the nameof the user you created in step 4, click Check Names to ensurethat the name is correct, and then click OK.

Click OK to close the Act As Part Of The OperatingSystem Properties dialog box.

In WebSphere Administrative Console, select Security > Global Security.

Under Administrative security, select Administrative user roles.

Add the newly created user to Mapped to role and map it toAdministrator.

In WebSphere Administrative Console, select Security > Global Security.

Ensure Enable Application Security checkbox is enabled.Click Next.

Specify the credentials you want to set and click Next.

Restart the WebSphere profile.

WebSphere will startusing the default keystore and truststore.

Truststores and keystores can be created using ikeymanutility or admin console. To make ikeyman work properly, enure thatthe WebSphere installation path does not contain parentheses.

In WebSphere Administrative Console, select Security > SSL certificate and key management.

Click Keystores and certificates under Related items.

In the Key store usages dropdown, ensure that SSL Keystores isselected. Click New.

Specify the path where you want your keystore to be created.If you have already created a keystore through ikeyman, specifythe path to the keystore file.

If you had added already created a keystore using ikeyman,your certificate will appear. Otherwise, you need to add a new self-signedcertificate by performing the following steps:

Specify appropriate values on the certificate form. Ensurethat you keep Alias and common name as fully-qualified domain nameof the machine.

Repeat steps 2 through 10 for creating a truststore.

Apply custom keystore and truststoreto the server

In WebSphere Administrative Console, select Security > SSL certificate and key management.

Click Manage endpoint security configuration. Thelocal topology map opens.

From the truststore name and keystore name drop-down lists,select the custom truststore and keystore that you created.

Restart the WebSphere profile.

Your profile now runson custom SSL settings and your certificate.

In WebSphere Administrative Console, select Security > Global Security.

In the Authentication section, expand RMI/IIOP security andclick CSIv2 inbound communications.

Ensure that SSL-supported is selected in the Transportdrop down list.

Configuring WebSphere to convertURLs that begins with https

To convert a URL that begins with https, add a Signer certificatefor that URL to the WebSphere server.

Createa Signer certificate for a https enabled site

In WebSphere Administrative Console, navigate to Signer certificatesand then click Security > SSL Certificate and Key Management> Key Stores and Certificates > NodeDefaultTrustStore >Signer Certificates.

Click Retrieve From Port and perform these tasks:

• In the Host box, type the URL. For example, type www.paypal.com.

• In the Port box, type 443. This port isthe default SSL port.

• In the Alias box, type an alias.

Click Retrieve Signer Information and then verify that theinformation is retrieved.

HTML-to-PDFconversion from the site whose certificate is added will now work fromthe Generate PDF service.

Websphere Application Server 8.5

Note:

For an applicationto connect to SSL sites from inside WebSphere, a Signer certificateis required. It is used by Java Secure Socket Extensions (JSSE)to validate certificates that the remote side of the connectionsent during an SSL handshake.

Websphere Application Server V7

IBM WebSphere does not allow multiple calls to ORB.init()when Global Security is enabled. You can read about the permanentrestriction at http://www-01.ibm.com/support/docview.wss?uid=swg1PK58704.

Perform the following steps to set the port to be dynamic andresolve the issue:

In WebSphere Administrative Console, select Servers > Server Types > WebSphere application server.

In the Configuration tab, under Communications section,expand Ports, and click Details.

Click the following port names, change the port number to0, and click OK.

• ORB_LISTENER_ADDRESS

• SAS_SSL_SERVERAUTH_LISTENER_ADDRESS

• CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS

• CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS

Open [aem-forms_root]crx-repositorylaunchpadsling.propertiesfile for editing.

Locate the sling.bootdelegation.ibm propertyand add com.ibm.websphere.ssl.* to its value field.The updated field look like the following:

Websphere Application Server 8.5.5.9

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices | Online Privacy Policy