NexJ deployment overview

The NexJ solution is deployed on a Java EE container, such as JBoss Application Server, WebSphere Application Server, or NexJ Server. It requires a relational database to store both NexJ metadata and client data.

This minimal configuration might be sufficient for a sample deployment used for development. A production deployment in an enterprise environment has a large number of optional components, depending both on the existing environment and on the desired NexJ application functionality.

NexJ CRM end-user interfaces

End users can access NexJ CRM using an Internet browser on their computer. In addition, mobile versions of NexJ CRM are available.

Ensure that the end users who will access the product you deployed have one of the browsers or mobile devices listed in the Release Notes document for your version of the product.

In addition, for users accessing NexJ CRM using an Internet browser, you can install NexJ Add-In for Microsoft Office to allow interaction with Microsoft Word and Microsoft Outlook. For more information about NexJ Add-In, see the NexJ Add-In for Microsoft Office User Guide.

HTTP servers

One or more HTTP servers (or web servers) are used to host the web sites that represent the NexJ solution, including NexJ CRM, NexJ Admin Console, and NexJ System Admin Console.

The web servers can be configured to provide user authentication, so that information between the user interface and the application server that serves the NexJ CRM application is sent securely. They can also be used to distribute requests from the user interfaces across multiple application servers.

The IBM WebSphere Application Server is distributed with the IBM HTTP Server, so their integration is seamless. JBoss Application Server can be integrated with the Apache HTTP Server or the Internet Information Services (IIS) for Windows Server. For instructions on how to configure these web servers to securely redirect JSP and servlet requests to the JBoss AS, see Configuring web servers to integrate with JBoss AS.

Push redirector

The push redirector is used to push data, such as messages and notifications, from the application server to the NexJ CRM client. For more information about the push redirector functionality and instructions for deploying the push redirector, see Push server configuration.

Java EE container

The deployed NexJ solution runs on an application server or an application server cluster.

For information on installing and configuring JBoss Application Server, see Setting up JBoss application servers.

For information on installing and configuring WebSphere Application Server, see Setting up the WebSphere Application Server environment.

For information on installing and configuring NexJ Server, see Setting up NexJ Server.

Online help

Online help for your NexJ solution can be deployed on the same web server as the applications or a separate web server, which may allow easier updates. For more information, see Enabling online help.

Microsoft Exchange Server

Use Microsoft Exchange Server to synchronize Microsoft Outlook email and calendar information with NexJ CRM. For information about deploying Microsoft Exchange Server and about NexJ integration with Microsoft Exchange Server, see the NexJ CRM Administration Guide for Synchronization with Microsoft Exchange Server.

Simple Mail Transfer Protocol (SMTP)

To enable sending mail using NexJ CRM, you need to create a mail channel using NexJ Studio.

Relational databases

NexJ requires a clean default relational database to contain metadata for NexJ CRM. You need to configure one or more database servers to contain this default relational database as well as any other database with client data required by NexJ CRM users. For more information, see Configuring a database environment.

Authentication configuration

You can configure single sign-on authentication for NexJ applications so that users are able to access other enterprise applications without having to again log in until their session has expired. NexJ uses Windows Authentication and the SPNEGO negotiation mechanism to securely authenticate users and determine their level of authorization. If Windows Authentication is not an option, Java Kerberos can be used as an alternative. For more information, see Configuring user browsers for silent single sign-on.

BI and ad hoc report configuration

To enable end users to generate reports using NexJ CRM and to add Business Intelligence (BI) functionality, you need to synchronize the operational database with a dedicated reporting database, create a new BI model, and create a new reporting environment. For more information, see Enabling Ad Hoc Reports and BI functionality.

Session persistence configuration

Session persistence allows server-side load balancing, as well as storing information about the user and the state of the user interface to create persisted sessions. This information can be stored in a database or a file in the file system. For more information, see Session persistence.

Enterprise Component Registry

The Enterprise Component Registry contains information about the portlets included in your NexJ solution. It also includes the User Registry, which contains information about NexJ users and user permissions. The functionality for ECR is packaged with your deployed model. The data for ECR is stored in a database, whose details are defined as a datasource connection file using NexJ Studio.

Attachment storage

In NexJ CRM, users can add computer files, such as Microsoft Word documents, to activities, campaigns, batch emails, or documents. Use a datasource connection file in NexJ Studio to indicate whether you want the attachments saved in a separate database or file system to improve performance.

Messaging configuration

NexJ supports internal message queues using ObjectQueue channels. However, it can also support third-party Java Message Service (JMS) providers such as Apache ActiveMQ, Progress SonicMQ, and IBM WebSphere MQ. For more information, see JMS engine integration.