Starting and Stopping WebSphere Application Servers

OJO:  SI NINGUNA DE ESTAS FUNCIONA MATA EL PROCESO JAVA

Starting and Stopping WebSphere Application Servers

By default, all of the servers of a WebSphere instance are stopped when you install PIA. You need to start the server in order to access the PeopleSoft components.

To start and stop WebSphere servers, use the delivered .BAT and .SH files located in:

PIA_HOME\webserv\<profilename>\bin

Note: During the server startup, the Dynamic runtime provisioning option is enabled by default. This option is used to enable only the necessary containers (servlet container, EJB container, and so on) when a server starts.

Starting the WebSphere Server

To start the WebSphere server, enter the following command:

Operating System	Command
Windows	startServer.bat server_name -profileNameprofilename
UNIX	startServer.sh server_name -profileNameprofilename

Stopping the WebSphere Server

To start the WebSphere server, enter the following command:

Operating System	Command
Windows	stopServer.bat server_name -profileNameprofilename
UNIX	stopServer.sh server_name -profileNameprofilename

Managing WebSphere Server with PSADMIN

Detener IBM WebSphere Application Server (Windows)

Siga este procedimiento para detener los servicios de WebSphere Application Server en una instalación de Microsoft Windows.

Procedimiento

Lleve a cabo una de las tareas siguientes, en función de si la configuración es autónoma o en clúster:

Detener una instalación de WebSphere Application Server Liberty Profile:

1. En el sistema que aloja la capa de servicios, inicie sesión como usuario que tiene privilegios de administrador local.
2. En un indicador de mandatos de Windows, especifique: net stop InfoSvr.

Detener una configuración autónoma de WebSphere Application Server:

1. En el sistema que aloja la capa de servicios, inicie sesión como usuario que tiene privilegios de administrador local.
2. En el escritorio de Windows, pulse Todos los programas > IBM WebSphere > Servidor de aplicaciones > Perfiles > InfoSphere > Detener el servidor. InfoSphere es el nombre de perfil en el que se ha instalado InfoSphere Information Server.
3. Cuando se le solicite, especifique un nombre de usuario y una contraseña que tenga privilegios de administrador de WebSphere Application Server.
4. Verifique que los procesos de WebSphere Application Server se han detenido. Consulte Comprobar el estado de IBM WebSphere Application Server Network Deployment (instalación autónoma).

Detener una configuración en clúster de WebSphere Application Server:

1. Inicie la consola administrativa de WebSphere Application Server.
2. En el árbol de navegación de la consola, pulse Servidores > Clústeres. Aparece la página Clúster de servidor.
   Nota: En función de la versión de WebSphere Application Server, es posible que tenga que pulsar Servidores > Clústeres > Clústeres de WebSphere Application Server para acceder a la página Clúster de servidor.
3. Seleccione el clúster.
4. Pulse Detener. Este mandato permite que todos los servidores de aplicaciones finalicen las solicitudes existentes y permite la migración tras error a otro miembro del clúster. Cuando se inicia la operación de detención, el estado del clúster cambia a parcialmente detenido. Una vez que se han detenido todos los servidores de aplicaciones, el estado del clúster para a ser Detenido.
5. En cada nodo, inicie sesión como usuario con privilegios de administrador local.
6. En el nodo, ejecute el mandato stopNode para detener el agente de nodo:

   C:\IBM\WebSphere\AppServer\profiles\Custom01\bin\stopNode -user wasadmin 
      -password contraseña

   En el mandato, Custom01 es el perfil personalizado de WebSphere Application Server que aloja un nodo del clúster de IBM® InfoSphere Information Server. wasadmin y contraseña son el nombre de usuario y la contraseña del administrador de WebSphere Application Server.
   Una vez que se detiene el agente de nodo, el control pasa de nuevo a la línea de mandatos.
   Nota: Si el agente de nodo se ejecuta como servicio Windows, el mandato stopNode detiene el servicio Windows asociado y el agente de nodo.
7. Verifique que todos los miembros del clúster y los agentes de nodo estén detenidos. Consulte Comprobación del estado de los miembros de clúster de IBM WebSphere Application Server yComprobación del estado de los agentes de nodo de IBM WebSphere Application Server.
8. Detenga el proceso de gestor de Network Deployment. Consulte Detener el Gestor de despliegue de IBM WebSphere Application Server (Windows).

• Detener el Gestor de despliegue de IBM WebSphere Application Server (Windows)
  Siga este procedimiento para detener el Gestor de despliegue de IBM WebSphere Application Server Network Deployment en una instalación Microsoft Windows con agrupación en clúster deWebSphere Application Server.

(The instructions below were tested on a Windows 7 machine)

%USER_INSTALL_ROOT% is the directory of a specific ‘profile’. E.g. C:\programs\IBM\WebSphere\AppServer\profiles\AppSrv01

%WAS_CELL% is the name of a specific ‘cell’.

%WAS_NODE% is the name of a specific ‘node’.

%SERVER_NAME% is the name of a specific server instance in the profile.

Start the server

• Open Windows command prompt.

• Enter the following commands:

• cd %USER_INSTALL_ROOT%/bin
• startServer.bat %SERVER_NAME%

In the directory %USER_INSTALL_ROOT%/servers, there exists one sub-directory for each server instance in the profile.

• See the console logs to know if the server started successfully. The console logs also point to a file which contains more detailed logs.

1. Open a command prompt and change to the following directory:
   Note: In a clustered environment, use the dmgr_profile_root directory and not the wp_profile_root directory.
   • Windows: wp_profile_root\bin
   • UNIX: wp_profile_root/bin
   • IBM i: wp_profile_root/bin
   • z/OS®: wp_profile_root/bin
2. Complete the following steps to start the servers, deployment managers, and node agents

   Table 1. Steps to start the servers, deployment managers, and node agents.

   Server	Steps
   Deployment manager	Enter the following command: UNIX: ./startManager.sh Windows: startManager.bat IBM i: startManager z/OS: ./startManager.sh
   Node agent	Enter the following command: UNIX: ./startNode.sh Windows: startNode.bat IBM i: startNode.sh z/OS: ./startNode.sh
   WebSphere Portal server	Enter the following command: Note: If you have a clustered environment or you renamed your WebSphere Portal server, WebSphere_Portal will be the name you defined for your WebSphere Portal server. UNIX: ./startServer.sh WebSphere_Portal Windows: startServer.bat WebSphere_Portal IBM i: startServer WebSphere_Portal z/OS: ./startServer.sh WebSphere_Portal

3. Complete the following steps to stop the servers, deployment managers, and node agents:

   Table 2. Steps to stop the servers, deployment managers, and node agents

   Server	Steps
   WebSphere Portal server	Enter the following command: Note: If you have a clustered environment or you renamed your WebSphere Portal server, WebSphere_Portal will be the name you define for your WebSphere Portal server. UNIX: ./stopServer.sh WebSphere_Portal Windows: stopServer.bat WebSphere_Portal IBM i: stopServer WebSphere_Portal z/OS: ./stopServer.sh WebSphere_Portal
   Node agent	Enter the following command: UNIX: ./stopNode.sh Windows: stopNode.bat IBM i: stopNode.sh z/OS: ./stopNode.sh
   Deployment manager	Enter the following command: UNIX: ./stopManager.sh Windows: stopManager.bat IBM i: stopManager z/OS: ./stopManager.sh

4. In a clustered environment, you can use the deployment manager WebSphere Integrated Solutions Console to stop and start the application servers that are managed by the deployment manager:

   Table 3. Using the deployment manager WebSphere Integrated Solutions Console to stop and start the application servers that are managed by the deployment manager.

   Option	Steps
   Start a specific application server in a cell	Complete the following steps to start a specific application server in a cell: Open the deployment manager WebSphere Integrated Solutions Console. Click Servers > Application Servers. Select the required server and click Start.
   Start the entire cluster	Complete the following steps to start the entire cluster: Open the deployment manager WebSphere Integrated Solutions Console. Click Servers > Clusters. Select the cluster and click Start or Ripple Start.
   Stop a specific server in a cell	Complete the following steps to stop a specific application server in a cell: Open the deployment manager WebSphere Integrated Solutions Console. Click Servers > Application Servers. Select the required server and click Stop or Immediate Stop.
   Stop the entire cluster	Complete the following steps to stop the entire cluster: Open the deployment manager WebSphere Integrated Solutions Console. Click Servers > Clusters. Select the cluster and click Stop or Immediate Stop.

Parent topic: Administering

Starting and stopping WebSphere Application Server

Several procedures require you to stop or start the instance of WebSphere where you want to deploy LiveCycle ES2 products. If you are unsure whether the application server has started, you can first view the status of the WebSphere Application Server.

View the status of WebSphere Application Server

1. From a command prompt, go to the [appserver root]/bin directory.
2. Enter the following command, replacing server_name with the name of your WebSphere Application Server:
   • (Windows) serverStatus.bat server_name
   • (Linux, UNIX) ./serverStatus.sh server_name

Start WebSphere Application Server

1. From a command prompt, go to the [appserver root]/bin directory.
2. Enter the following command, replacing server_name with the name of your WebSphere Application Server:
   • (Windows) startServer.bat server_name
   • (Linux, UNIX) ./startServer.sh server_name

Stop WebSphere Application Server

1. From a command prompt, go to the [appserver root]/bin directory.
2. Enter the following command, replacing server_name with the name of your WebSphere Application Server:
   • (Windows) stopServer.bat server_name
   • (Linux, UNIX) ./stopServer.sh server_name

[Tutorials] How to set up a horizontal cluster for a Maximo sandbox using WebSphere Application Server 7

[Tutorials] How to set up a horizontal cluster for a Maximo sandbox using WebSphere Application Server 7

[Tutorials] How to set up a horizontal cluster for a Maximo sandbox using WebSphere Application Server 7

Introduction

As described in WebSphere Application Server Information Center: “Clusters are groups of servers that are managed together and participate in workload management. A cluster can contain nodes or individual application servers. Clusters are responsible for balancing workload among servers. Servers that are a part of a cluster are called cluster members. When you install an application on a cluster, the application is automatically installed on each cluster member. You can configure a cluster to provide workload balancing with service integration or with message driven beans in the application server.”

There are two types of clustering: horizontal and vertical. Both of them can be configured in different ways. This document is a guide that shows the easiest version of a horizontal cluster for a Maximo sandbox using WebSphere Application Server 7 (WAS). 

Benefits of a horizontal cluster environment:

• High availability;
• Load balance;
• Performance improvement. 

Pre-requirements

This tutorial is based on WebSphere Application Server 7 and Maximo 7.5. Some specifics steps may differ from version to version, but the overall process is the same.

The user required to execute this tutorial must have administrative privileges in WAS to create nodes, clusters, start and stop servers, among other things.

To simplify the configuration of the horizontal cluster provided by this guide, no directory information services (LDAP), such as IBM Tivoli Directory Server or Microsoft Active Directory, were installed or configured.

It is also necessary to have at least two machines for the horizontal cluster. One of them must have Maximo successfully deployed. The other must have only an Application Server installed, with no Deployment Manager (DM). In order to improve performance of your environment, you may install the database or deployment management in separate machines.

The standalone Application Server that you want to federate must be up and running before starting this guide. 

After executing this guide, you should have a horizontal cluster environment similar to the image below: 

Note: This guide requires readers to have basic WAS and Maximo platform knowledge.

Adding a node

1. Login to the WAS admin console as wasadmin (Maximo server / WAS with DM).

2. Navigate to System administration > Nodes.

3. Click Add Node.

4. Select Managed Node.

5. Click Next.

6. On the next page, provide all the information about the Node you want to federate: 

7. Click OK.

8. On the next page, it will give an option to run the node as a Windows Service. Do not select this option and click OK.

9. The creation node process will start and the logs will be displayed.

10. Once the process has finished, you should see two nodes: one from cell 1 and another for cell 2 that you have just added.

11. If the nodes are not synchronized, select nodes 1 and 2 and click Synchronize.

12. At this point, you will no longer be able to login to WAS from cell 2 since it is now managed by the Deployment Manager.

 Creating the cluster

1. Navigate to Servers > Clusters > WebSphere application server clusters.

2. Click New.

3. On the next page, enter a Cluster Name (e.g. MaximoCluster).

4. Select Prefer local, if it is not selected already.

5. Click Next.

6. On the Create first cluster member page, enter a member name (e.g. cluster_member_1).

7. Select Node 1.

8. Select Generate unique HTTP ports, if it is not selected already.

9. Select Create the member using an existing application server as a template > MXServer.

10. Click Next.

11. On the next page, add another member to the cluster (e.g. cluster_member_2).

12. Select Node 2.

13. Select Generate unique HTTP ports, if it is not selected already.

14. Click Add Member.

15. Click Next and Finish.

16. Your cluster is down at this point but it will be started later.

 Creating new ports

1. Navigate to Environment > Virtual hosts.

2. Select maximo_host.

3. Click New and enter the following:

Host Name: *

Port: 9081

4. Click OK and save changes.

5. Create more ports if needed. 

 Deploying Maximo

1. Navigate to Servers > Server Types > WebSphere application servers.

2. Select MXServer and the server from cell 2, if not stopped yet, and click Stop.

3. Navigate to Applications > Application Types > WebSphere enterprise applications.

4. You should see the Maximo installed but it is not running in the cluster yet.

5. Select Maximo and click Uninstall.

6. Click Install.

7. Select the maximo.ear file. 

8. Click Next.

9. Select Fast Path.

10. On the Step 1 page, select Deploy web services and click Next.

11. On the Step 2 page, hold Ctrl key and select MAXIMOCLUSTER and webserver1 from Cluster and servers section.

12. Select all the modules and click Apply. 

13. Click Next.

14. On Step 3, select all the Web modules with maximo_host as Virtual host.

15. Click Next and Finish.

16. You should have Maximo deployed in the cluster at this point.

Starting the Cluster 

1. Navigate to Servers > Clusters > WebSphere application server clusters.

2. Select MaximoCluster and click Start. The cluster might take several minutes to start.

3. Navigate to Servers > Server Types > WebSphere application servers. 

4. The cluster members should be up and running.

5. Navigate to Applications > Application Types > WebSphere enterprise applications.

6. Verify that Maximo should also be running at this point.

7. Navigate to Environment > Update global Web server plug-in configuration.

8. Click OK.

9. At this point, you should be able to login to Maximo.

Testing the Cluster

To ensure that the cluster configuration is working properly, execute the following steps:

1. Navigate to Servers > Server Types > WebSphere application servers.

2. Stop cluster_member_1.

3. You should be able to login to Maximo even when one of the cluster members is down.

4. Start  cluster_member_1.

5. Stop cluster_member_2.

6. You should be able to login to Maximo even when one of the cluster members is down.

7. Start  cluster_member_2. 

Tags:  maximo cluster websphere desk was control sccd smartcloud

HOW TO FIX A JDBC ERROR IN WAS SERVER websphere application server 8.5.5

WHEN YOU HAVE THE FOLLOWING ERROR IN WEBSPHERE APPLICATION SERVER V8.5.5:

[6/11/15 22:00:43:918 PDT] 00000069 SQLServerConn E   Java Runtime Environment (JRE) version 1.6 is not supported by this driver. Use the sqljdbc4.jar class library, which provides support for JDBC 4.0.
[6/11/15 22:00:43:918 PDT] 00000069 DataSourceCon E   DSRA8040I: Failed to connect to the DataSource.  Encountered "": java.lang.UnsupportedOperationException: Java Runtime Environment (JRE) version 1.6 is not supported by this driver. Use the sqljdbc4.jar class library, which provides support for JDBC 4.0.
at com.microsoft.sqlserver.jdbc.SQLServerConnection.<init>(SQLServerConnection.java:304)
at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnectionInternal(SQLServerDataSource.java:620)

SOLUTION:

FIRST: VERIFY THE FOLLOWING CONFIGURATION IN THE JDBC DRIVER:
AS FOLLOWS:

open the environment variables and set the folder here as follows:

verify the connection test the connection, we are using Java JRE 1.6

Then you need to verify the systemout.log of the was server

SYSTEMOUT.log

FINALLY THE VALIDATION:
***************************************
[6/11/15 22:10:35:408 PDT] 00000067 DSConfigurati I   DSRA8205I: JDBC driver name  : Microsoft SQL Server JDBC Driver 3.0
[6/11/15 22:10:35:408 PDT] 00000067 DSConfigurati I   DSRA8206I: JDBC driver version  : 3.0.1301.101
[6/11/15 22:10:35:408 PDT] 00000067 DSConfigurati I   DSRA8025I: Successfully connected to DataSource.
[6/11/15 22:10:35:439 PDT] 00000067 DSConfigurati I   DSRA8203I: Database product name : Microsoft SQL Server



THE CONNECTION WAS SUCCESFULL, IS MIPORTANT TO NOTE TO USE JDBC DRIVER 3 NOT 4

Unable to Login to WebSphere Console after enabling LDAP Security Technote (troubleshooting)

http://www-01.ibm.com/support/docview.wss?uid=swg21404357

Problem(Abstract)

Enabling Global Security in WebSphere as part of the Application Server Security setup the Administrator is no
longer able to log in to the WebSphere Administrative Console after restarting WebSphere services.

Cause

The WebSphere Security mechanism is not able to validate any user credentials due to incorrect configuration
of the Global Security settings.

Environment

This document only applies to customers using IBM WebSphere version 6.0.x or 6.1 as their Application
Server. If there is no active connection to the Directory Server configured in WebSphere,
this issue may occur as well.

Resolving the problem

To temporarily disable Global Security in WebSphere perform the following tasks.

-Stop all WebSphere services if they are running. If the services will not stop, this is likely due to the
Global Security being enabled, you will need to restart the server after making these changes.

-Locate and edit the Security.xml files in the following directories:

\..\WebSphere\AppServer\profiles\<maximo_profile_name>\config\cells\<cell_name>\security.xml

and

\..\WebSphere\AppServer\profiles\<dmgr_profile_name>\config\cells\<cell_name>\security.xml

In a text editor, on line 2 of the XML file, locate the following text:
useLocalSecurityServer="true" useDomainQualifiedUserNames="false" enabled="true" cacheTimeout="600"

Change both useLocalSecurityServer and enabled to "false":

useLocalSecurityServer="false" useDomainQualifiedUserNames="false" enabled="false" cacheTimeout="600"

Save the files then start the WebSphere Services or Restart the Server.

When the WebSphere services are restarted, you will be able to access the console with any username. This allows any incorrect configurations to be changed and re-tested.

Ensure that these file changes are reverted once the issue is resolved.

WAS troubleshooting

[5/18/15 11:01:32:341 BDT] 000000cd LocalTranCoor E   WLTC0017E: Resources rolled back due to setRollbackOnly() being called.
 Error
FNRAC1008E
Unable to get data from server

User response: Check the error details for more information and contact IBM Software Support if necessary.

Exception details:
[FNRPE0911843060E]Error executing the CA RPC call configEventExportStoreProperties
Root cause:java.lang.NullPointerException: null

http://daciwsappuat:9080/acce/

****
[5/18/15 11:01:32:341 BDT] 000000cd LocalTranCoor E   WLTC0017E: Resources rolled back due to setRollbackOnly() being called.
[5/18/15 11:34:17:832 BDT] 000000d7 BusinessExcep E   CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "getConfiguration" on bean "BeanId(FileNetEngine#peengine-ejb.jar#PECARPC, null)". Exception data: [FNRPE0911843060E]Error executing the CA RPC call configEventExportStoreProperties
 Root cause:java.lang.NullPointerException: null
at filenet.eventexporter.ca.sql.DBType.verifyState(DBType.java:44)
at filenet.eventexporter.ca.sql.DBString.getValue(DBString.java:41)
at filenet.eventexporter.ca.sql.SchemaInfo.getSchemaInfo(SchemaInfo.java:76)
at filenet.eventexporter.ca.sql.SchemaInfo.getSchemaInfo(SchemaInfo.java:40)
at filenet.eventexporter.ca.main.DataStore.validateStore(DataStore.java:511)
at filenet.eventexporter.rpc.BaseRPC.setContext(BaseRPC.java:59)
at filenet.eventexporter.rpc.CARPC.setContext(CARPC.java:45)
at filenet.eventexporter.rpc.CARPC.setContext(CARPC.java:39)
at filenet.eventexporter.rpc.CARPC.setContext(CARPC.java:34)
at filenet.eventexporter.rpc.CARPCRepositoryConfiguration.getCAConfig(CARPCRepositoryConfiguration.java:239)
at filenet.eventexporter.rpc.CARPCImpl.getConfiguration(CARPCImpl.java:568)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.ibm.ejs.container.EJSContainer.invokeProceed(EJSContainer.java:6304)
at com.ibm.ejs.container.interceptors.InvocationContextImpl.proceed(InvocationContextImpl.java:568)
at filenet.jpe.rpc.common.RequestInterceptor.getMyUser(RequestInterceptor.java:93)
at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.ibm.ejs.container.interceptors.InterceptorProxy.invokeInterceptor(InterceptorProxy.java:227)
at com.ibm.ejs.container.interceptors.InvocationContextImpl.proceed(InvocationContextImpl.java:548)
at com.ibm.ejs.container.interceptors.InvocationContextImpl.doAroundInvoke(InvocationContextImpl.java:229)
at com.ibm.ejs.container.EJSContainer.invoke(EJSContainer.java:6195)
at filenet.vw.server.rpc.carpc.EJSRemote0SLPECARPC_b8739aea.getConfiguration(EJSRemote0SLPECARPC_b8739aea.java)
at filenet.vw.server.rpc.carpc._ICARPCRemote_Stub.getConfiguration(_ICARPCRemote_Stub.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at filenet.pe.ejb.client.PERPCProxyBase.ejbInvokeNormal(PERPCProxyBase.java:422)
at filenet.vw.server.rpc.carpc.PECARPCProxy.ejbInvoke(PECARPCProxy.java:52)
at filenet.pe.ejb.client.PERPCProxyBase.privateInvokeRPC(PERPCProxyBase.java:448)
at filenet.pe.ejb.client.PERPCProxyBase.access$000(PERPCProxyBase.java:89)
at filenet.pe.ejb.client.PERPCProxyBase$EJBExecuteAction.run(PERPCProxyBase.java:127)
at java.security.AccessController.doPrivileged(AccessController.java:314)
at javax.security.auth.Subject.doAs(Subject.java:573)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:195)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:152)
at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.filenet.apiimpl.util.J2EEUtilWS.doAs(J2EEUtilWS.java:220)
at com.filenet.api.util.UserContext.doAs(UserContext.java:143)
at filenet.pe.ejb.client.PERPCProxyBase.invokeRPC(PERPCProxyBase.java:478)
at filenet.vw.server.rpc.BaseCHASession.executeRPC(BaseCHASession.java:164)
at filenet.vw.server.rpc.carpc.CASession.getConfiguration(CASession.java:192)
at com.filenet.acce.mediator.process.P8CAMediator.executeGet(P8CAMediator.java:135)
at com.filenet.acce.mediator.process.P8CAMediator.execute(P8CAMediator.java:116)
at com.filenet.acce.AccePluginService$1.run(AccePluginService.java:100)
at java.security.AccessController.doPrivileged(AccessController.java:314)
at javax.security.auth.Subject.doAs(Subject.java:573)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:195)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:152)
at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.filenet.apiimpl.util.J2EEUtilWS.doAs(J2EEUtilWS.java:220)
at com.filenet.api.util.UserContext.doAs(UserContext.java:143)
at com.filenet.acce.AccePluginService.doPrivileged(AccePluginService.java:118)
at com.filenet.acce.AccePluginService.execute(AccePluginService.java:76)
at com.ibm.ecm.util.PluginUtil.invokeService(PluginUtil.java:595)
at com.ibm.ecm.struts.actions.PluginAction.executeBaseAction(PluginAction.java:109)
at com.ibm.ecm.struts.actions.BaseAction.execute(BaseAction.java:166)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.ibm.ecm.struts.controller.ControllerServlet.process(ControllerServlet.java:238)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1214)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:774)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:456)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:125)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:77)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:926)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1023)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3703)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:962)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:522)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:311)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:87)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1783)

[5/18/15 11:34:17:832 BDT] 000000d7 LocalTranCoor E   WLTC0017E: Resources rolled back due to setRollbackOnly() being called.