Skip to end of metadata
Go to start of metadata

A DeployableContainer implementation that can connect and run against a remote (different JVM, different machine) running a WebSphere Application Server V7.0 profile. This implementation has no lifecycle support, so it can not be started or stopped.

This container implementation is currently not available in public maven repositories. If you want to use it, please follow our build instructions.

Container Injection Support Matrix

@EJB @EJB (no-interface) @Inject (CDI) @Inject (MC) @PersistenceContext @PersistenceUnit
       

Prerequisite Version

This DeployableContainer requires WebSphere Application Server fix pack V7.0.0.15 or higher.

Configuration

Default Protocol: Servlet 2.5

Container Configuration Options

Name Type Default Description
remoteServerAddress String localhost Hostname for the target machine where the WAS profile is running.
remoteServerSoapPort Integer 8880 SOAP port of the target WAS profile.
securityEnabled Boolean false Defines whether security is enabled.
Note: When security is enabled you have to use an IBM SDK, otherwise the SSL connection will fail.
username String admin The username to use to connect to the target. - This is required even when security is disabled.
password String admin The password to use to connect to the target.
sslTrustStore String "" The location of the SSL Trust store to use. - This is required when security is enabled.
sslTrustStorePassword String WebAS The password for the SSL Trust store. - This is required when security is enabled.
sslKeyStore String "" The location of the SSL Key store to use.
sslKeyStorePassword String WebAS The password for the SSL Key store.

Example of Container Configuration (arquillian.xml)

Example of Maven profile setup

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jun 14, 2011

    Why exactly is WebSphere Application Server fix pack V7.0.0.15 or higher required? Isn't it possible to use @EJB with version 7.0.0.11 for example?

    1. Jun 14, 2011

      The version requirement is not related to the @EJB annotation, which is part of the EJB3 FeP, but most likely due to APAR PK93844. We haven't investigated down to the fix level what the problem is, so the deployment might also work starting with V7.0.0.7, its just that the oldest version we tested with was V7.0.0.15. If V7.0.0.11 works for you, that's fine. Otherwise, we might ask you to upgrade if we can't reproduce a problem.

      The problem we saw with earlier versions was an IWAE0006E inside an FFDC when we tried to get the DDs from the MBeans.