Posts tagged WebSphere

LiveCycle – Application Server Clustering Verification

When running Adobe LiveCycle in cluster mode, it is important to verify that the cluster is configured and started successfully. LiveCycle deployment has has twoclustering layers

  • Application Server Clustering
  • LiveCycle Clustering

LiveCycle runs on J2EE stack. J2EE level clustering should be configured as mentioned in LiveCycle cluster documentation. In this article we will go through each application server and based on logs determine if the clustering is successful or not, LiveCycle Clustering is described in the article – LiveCycle Cluster Verification.

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle Cluster Verification

On top of J2EE clustering, LiveCycle is clustered using Gemfire Distributed Cache. In cluster deployments, it is important that all the members of a LiveCycle cluster are able to find each other so that they can keep their individual caches in synchronization with one another. LiveCycle Cluster is configured properly or not can be identified based on two key indicators. The following are the key indicators.

  • Clustered Scheduler Service
  • Gemfire Logs

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle XMLForms Native Process and WebSphere Global Security

- Santosh Tatke, Sr. Support Architect @ Adobe

Debugging form rendering issues related to XMLforms native process could be challenging. In one of the earlier blogs I’ve put together a few points those could help narrow down problem areas. Blog post is available here.

We recently encountered a situation with another customer which was another manifestation of form rendering related problem and root cause was very different.

They were using LiveCycle ES2 SP2 + AIX 6.1 + WAS 7.0.0.17 + Oracle 11g.

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle PDF Generator – Configuring WebSphere AppServer Instance to Run As Windows Service

Jayan Kandathil

If you get exceptions such as follows in WebSphere SystemOut.log when you try LiveCycle PDF Generator document conversions, you might need to run the WebSphere appserver instance as a Windows service running as the ‘SYSTEM’ account:

ERROR: API = CreateProcessAsUser
INFO [STDOUT] ERROR CODE = 1314
MESSAGE = A required privilege is not held by the client.

Download the utility WASServiceCmd.exe from here. Copy it to %WAS_HOME%bin and run it to create a Windows service for the WebSphere appserver instance that hosts LiveCycle.

Eg:
WASService.exe -add “Adobe_LiveCycle” -serverName “server1″ -profilePath “C:ProgramsIBMWebSphereAppServerprofilesAppSrv01″ -logRoot “C:ProgramsIBMWebSphereAppServerprofilesAppSrv01logsserver1″ -logFile “C:ProgramsIBMWebSphereAppServerprofilesAppSrv01logsserver1SystemOut.log” -encodeParams -stopArgs “-username SYSTEM” -startType manual -restart false

If it worked, you should get a response similar to this:

Adding Service: Adobe_LiveCycle
Config Root: C:ProgramsIBMWebSphereAppServerprofilesAppSrv01config
Server Name: server1
Profile Path: C:ProgramsIBMWebSphereAppServerprofilesAppSrv01
Was Home: C:ProgramsIBMWebSphereAppServer
Start Args:
Restart: 0
IBM WebSphere Application Server V7.0 - Adobe_LiveCycle service successfully added.

Start the service and try the document conversion again. If you still have problems, see this.

——-
Original article at http://blogs.adobe.com/livecycle/2011/04/livecycle-pdf-generator-configuring-websphere-appserver-instance-to-run-as-windows-service.html.

Content Services: WebSphere stops responding when many concurrent threads are running

Samartha Vashishtha 

When the storeContent operation for Content Services 9 is invoked with more than 30 threads, the WebSphere application server may stop responding.

Follow these steps to resolve the issue:

  1. In WebSphere Administrative Console, click Servers > Server Types > WebSphere application servers and then click a server name.
  2. In the right pane, click Thread pools under Additional Properties.
  3. Click WebContainer and, on the Configuration page, increase the value of the Maximum Size field by double the number of threads that you need to run. For example, increase the value of the Maximum Size field by 80 if you want to run 40 threads.
  4. Click Apply or OK.
  5. Click Save directly to the master configuration.
  6. Restart the WebSphere application server.

——-
Original article at http://blogs.adobe.com/livecycledocs/2011/02/content-services-websphere-stops-responding-when-many-concurrent-threads-are-running.html.

Go to Top