Posts tagged JBoss

LiveCycle on JBoss with Oracle having multiple schemas

Sometimes user may face issues while configuring LiveCycle on JBoss with Oracle having multiple schema.  One of the them are TIMERS and HILOSEQUENCES tables not found.

The steps to resolve this issue are discussed in this blog.

Avoiding LiveCycle Kerberos based SSO problems for Active Directory users with large group memberships

Many LiveCycle customers implement kerberos based SSO in their deployments.

We recently came across an interesting customer situation where SSO did not work for some domain users. To recap working scenario – If LiveCycle SSO is configured correctly, when domain user opens workspace URL from  domain machine, workspace should directly open without asking for user credentials again.

In this case, it wasn’t working for some domain users; but worked for others.

Investigating further we found that non-working users were part of 100+ AD groups resulting in a large kerberos token size.

Customer was using JBoss 4.2.1 with LiveCycle ES2.5.

---

Read the complete post at Adobe LiveCycle Blog.

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 Cluster – TCP based JBoss Clustering

- Pankaj Parashar, Lead Softweare Engineer @ Adobe

Adobe LiveCycle comes with pre-configured JBoss (Community Edition only) . The preconfigured JBoss has both standalone and cluster-enabled configurations. All cluster-enabled configurations are based on UDP by default. Various enterprise organizations have very restrictive network policy and don’t allow multicasting in their networks. For such organizations, TCP based clustering is recommended option. JBoss instances belonging to different subnets require TCP based clustering only. In this article, we will go through detailed instructions to configure TCP based JBoss cluster. These instructions are applicable for both preconfigured JBoss and downloaded JBoss (Version 5.1 only).

The Following are the detailed instructions for TCP Clustering:

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle: JBoss stopped logging in server.log

- David McMahon, Senior Technical Account Manager @ Adobe

If you have installed LiveCycle in a JBoss application server the server activity will normally be logged in:

<JBOSS_HOME>server<profile>logserver.log

If the JBoss log is no longer logging activity you should check the following:

---

Read the complete post at David's blog.

JBoss Cluster Discarding Messages

- Pankaj Parashar, Lead Software Engineer @ Adobe

Sometimes while running LiveCycle on JBoss Cluster, you may see the following log messages appearing in server logs. WARN [org.jgroups.protocols.UDP] discarded message from different group “DefaultPartition” (our group is “LIVECYCLE-CLUSTER”). Sender was 10.56.78.90:54356

---

Read the complete post at Adobe LiveCycle Blog.

Quick way to run multiple Jboss 5.x instances on single machine

- Santosh Tatke, Sr. Support Architect @ Adobe 

Use Case:

Often times one runs into use cases where you need to run multiple Jboss instances on same machine. E.g. If you are installing LiveCycle ES3 Correspondence Management solution. It needs two different app server instances for author and publish instance.

Obvious problem  you may run into is port conflicts. Known way of dealing with port conflicts is by manually changing Jboss config files.

Well, not anymore.

---

Read the complete post at Adobe LiveCycle Blog.

Working around a “Turnkey service JBoss for Adobe LiveCycle does not exist” error

- Waldo Smeets

Disease:
After installing a new Jboss turnkey instance of Adobe LiveCycle, some people run into an issue when the LiveCycle Configuration Manager is doing it’s work. At about 40%, the configuration manager might display the following error:

 

Failed on ‘Verifying JBoss for Adobe LiveCycle ES service is installed’
Windows turnkey service JBoss for Adobe LiveCycle ES does not exist

When checking in the Windows Service Panel, indeed there is no such service defined, even though the installer should have created it. I have not been able to replicate this issue, but it happened to me at a customer site and by searching Google it seems that others have run into it as well.

Prescription:
The Google search results tells us that some people forget to set the Java_Home system variable and that you should be using the right version of the JDK. However, this did not seem to be the problem in this case.

Through the install documentation you can find the steps needed to re-create the JBoss for Adobe LiveCycle ES service (page 62). You can use those to try and create the service ‘manually’. For our install, the problem seemed to be in the [LC_INSTALL_ROOT]jbossInstallJBossService.bat script file. Somehow the username / password did not seem to work, whatever we tried it failed. Well, sort off: strangely enought the command prompt output first mentions that there was an error, though still reports that the script was executed succesfully. Still no service created though.

The solution was too simple to come up with: just remove the username / password parameters from the script and execute it. This time the script did not fail and as expected created the service for us. Next thing to do is go into the service panel, select the ‘JBoss for Adobe LiveCycle’ service, right click to go to it’s Properties and in the Log On tab specify Log In As This Account. Then specify the username password (in my case “.administrator” and the password), click OK and you are done.

Now run the LiveCycle Configuration Manager again and most likely it won’t fail anymore cause of the missing service. This seemed to have overcome our issue.

Tip to stay healthy:
When installing the turnkey solution, it is highly recommended to keep the right documentation at hand: Installing and Deploying LiveCycle® ES Using Turnkey.

Did you run into this issue as well? Please let us know if this worked for you or if you have additional tips for our readers.

—-
Original article at http://www.drflex.eu/2009/03/turnkey-service-jboss-for-adobe-livecycle-does-not-exist/?utm_source=rss&utm_medium=rss&utm_campaign=turnkey-service-jboss-for-adobe-livecycle-does-not-exist.

Enabling XA Transactions in SQL Server 2008 for ADEP Interactive Statements

The Adobe Customer Experience solution “Correspondence Management” (formerly Interactive Statements Solution Accelerator) requires an XA-type JDBC data source. XA is a specification for distributed transaction processing that involves multiple resources such as a database, or a JMS queue. More here.

In the JBoss Turnkey as well as in the pre-configured JBoss EAP tree, it is defined in the file adobe-sa-ds.xml in %JBOSS_HOME%aep_sqlserverdeploy. The JNDI name is “AdobeDefaultSA_DS“. It uses a different driver class (com.microsoft.sqlserver.jdbc.SQLServerXADataSource) compared to the other ADEP Document Services JDBC data sources (IDP_DS and EDC_DS) which are non-XA (com.microsoft.sqlserver.jdbc.SQLServerDriver). Both these classes are available in version 3 of Microsoft’s SQL Server JDBC Driver which supports SQL Server 2008.

Default SQL Server 2008 installs are not configured for XA transactions. If you have a JBoss 5.1 EAP instance running ADEP Document Services against Microsoft SQL Server 2008, you will get the following error messages every 2 minutes in JBoss server.log:

[com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: com.microsoft.sqlserver.jdbc.SQLServerException: Failed to create the XA control connection. Error: “Could not find stored procedure ‘master..xp_sqljdbc_xa_init_ex’.”, XAException.XAER_RMERR

To configure a SQL Server 2008 instance for XA, your SQL Server 2008 DBA has to perform several steps server-side, on the SQL Server machine:

1) Download the Microsoft SQL Server JDBC Driver 3.0 from here and install it somewhere (run the .exe)

2) Copy sqljdbc_xa.dll from %JDBC_DRIVER_INSTALL_ROOT%sqljdbc_3.0enuxax64 (assuming the SQL Server 2008 instance is 64-bit) to %SQLSERVER_INSTALL_ROOT%Instance_rootMSSQL10.MSSQLSERVERMSSQLBinn

CREATE XA STORED PROCEDURES and ROLES

3) Copy-paste the contents of the script xa_install.sql in %JDBC_DRIVER_INSTALL_ROOT%sqljdbc_3.0enuxa and execute it using SQL Server Management Studio’s Query Editor.

4) Confirm the creation of new stored procedures in SQL Server Management Studio. In the left pane, navigate to Programmability->Extended Stored Procedures for the “master” database – it should look something like this:

APPLY ROLE TO J2EE APPSERVER JDBC USER

5) Using SQL Server Management Studio’s Query Editor, assign the ‘SqlJDBCXAUser’ role to the SQL Server user that the JDBC connection pool uses for authentication and execute it. The following script assigns the role to the user ADEPJBoss:

USE master
GO
EXEC sp_grantdbaccess 'ADEPJBoss', 'ADEPJBoss'
GO
EXEC sp_addrolemember [SqlJDBCXAUser], 'ADEPJBoss'

“Command(s) completed successfully.”

CONFIGURE THE DISTRIBUTED TRANSACTION COORDINATOR (DTC)

6) Choose the Windows menu Administrative Tools->Component Services.

7) In the left navigation pane, navigate to Console Root->Component Services->Computers->My Computer->Distributed Transaction Coordinator->Local DTC.

8) Highlight ‘Local DTC’, right-click the mouse and choose ‘Properties’.

9) Choose the ‘Security’ tab. Ensure that the checkbox for ‘Enable XA Transactions’ is checked. Please see screenshot below.

10) Click Apply, then OK.

CONFIGURE REQUIRED WINDOWS SERVICES TO START AUTOMATICALLY

11) Choose the Windows menu Administrative Tools->Services. In it, make sure that the “Distributed Transaction Coordinator” service is set to start automatically. Start it.

12) Also make sure that the other services it depends on, namely ‘Remote Procedure Call‘, ‘Security Accounts Manager‘ are also set to start automatically.

13) Re-start the SQL Server instance

14) Re-start the appserver instance hosting ADEP Document Services and make sure that the error messages no longer appear.

——-
Original article at http://blogs.adobe.com/ADEP/2011/08/enabling-xa-transactions-in-sql-server-2008-for-adep-interactive-statements.html.

Go to Top