Deployment Guide NexJ CRM Deployment Guide overview The NexJ CRM Deployment Guide shows how to deploy your model to your servers and upgrade NexJ applications. NexJ applications include NexJ CRM and NexJ Admin Console. NexJ system architecture and deployment overview The following topics provide an overview of the NexJ solution architecture of a deployed NexJ solution. Prerequisites and supported platforms NexJ Model Engine, NexJ Studio, and NexJ Customer Relationship Management have hardware and software which is required before installation, as well as software which is supported for integration with NexJ. Creating environment files In NexJ Studio, you work on your model by defining an environment file. Configuring a database environment This chapter outlines how to create a clean database that will contain metadata for NexJ CRM. Use NexJ Studio to configure connections to the database, as well as to create and populate the database. Setting up JBoss application servers Set up a JBoss application server environment on a server where you plan to install NexJ Customer Relationship Management. Logging activity in JBoss environments All NexJ applications running on JBoss application servers use Apache log4j, a Java-based logging utility, to generate log files. Setting up the WebSphere Application Server environment To set up NexJ Customer Relationship Management on WebSphere Application Server (WAS), you need to install and configure WAS and then deploy NexJ CRM on the WAS environment. Logging activity in WebSphere Application Server environments WebSphere Application Server generates log files for NexJ applications that run on the server. Setting up NexJ Server Set up a NexJ Server environment on a server where you plan to install NexJ Customer Relationship Management. Logging activity in NexJ Server environments All NexJ applications running on NexJ Server use Apache log4j, a Java-based logging utility, to generate log files. Push server configuration NexJ applications may require the application server to send or push data to the client in real time as it becomes available. For example, with a telephony integration solution, an incoming phone call triggers an event on the application server that notifies a user of an incoming call and loads details into a workspace about the contact who is calling. Configuring web servers to integrate with JBoss AS You can configure Microsoft Internet Information Services (IIS) or Apache HTTP Server to redirect JSP and Java Servlet requests to JBoss Application Server (JBoss AS). Configuring single sign-on These instructions discuss how to configure single sign-on authentication for NexJ applications. Configuring flexible authentication NexJ Server enables flexible authentication that supports all third-party Single Sign-On (SSO) solutions including SPNEGO with Kerberos. JMS engine integration The Java Message Service (JMS) provides a framework for enterprise messaging systems. The JMS defines a set of specifications for enterprise messaging systems that allow messages to be sent across application components. A number of providers are available for use, including Apache ActiveMQ, Progress SonicMQ, and IBM WebSphere MQ. Deploying Ad Hoc Reports for NexJ CRM Ad Hoc Reports are run-time configurable reports that users generate in NexJ CRM. Configuring audit trails Use NexJ Studio to configure audit trails. Audit trails record actions that users perform in NexJ CRM. Session persistence When a connection between the application server and a client is established, information about the user and the state of the user interface is placed into a session. This session information is temporarily stored in memory, and could be lost when the session times out or the browser is closed. Session persistence allows session information to be stored for a longer period of use. Additional configuration Set the lead mode for your deployment and enable online help. Securing NexJ applications Before you deploy your NexJ application to a production environment, you should ensure that you have taken steps to secure the application. Deploying NexJ applications After you have deployed your NexJ application, you can access it through a supported web browser. Configuring logging and monitoring of NexJ applications After your NexJ application has been deployed, you should monitor it to identify and resolve any issues. Troubleshooting NexJ applications You can use tools in NexJ Admin Console and NexJ System Admin Console to troubleshoot common issues with your NexJ application. Computer telephony integration with NexJ CRM You can integrate your telephony system with NexJ CRM in order to take advantage of the contact center functionality. Reserving servers for specific functions You can configure servers in a cluster to perform specific functions such as batch processing and Exchange synchronization. Deploying Client Insights NexJ CRM provides the Client Insights functionality which allows users to share articles of interest with contacts. Deploying mailer templates System administrators can deploy mailer templates for Document Manager items using an import process in NexJ Admin Console. For example, administrators can import third-party birthday mailer templates along with matching criteria they have written in Scheme expressions. Users can then select the Document Manager folder containing the birthday mailer templates to print birthday messages for contacts. Based on the matching criteria, the system determines the template to be used for each selected contact. Upgrading NexJ Contact from version 4.1 to version 5.1 Use the instructions in this section to upgrade your NexJ Contact from version 4.1 to version 5.1. Upgrading NexJ Contact from version 5.1 to version 6.1 Follow these instructions to upgrade NexJ Contact from version 5.1 to version 6.1. Upgrading to NexJ CRM version 8.8 Follow these instructions to upgrade NexJ Contact version 6.1, 7.0, 7.1, or 7.2 or an earlier version of NexJ CRM to NexJ CRM version 8.8. Troubleshooting deployment issues To diagnose server problems, enable the DEBUG log level. If necessary, enable the ALL log level to turn on all logging. Resources This chapter contains information about third-party software that might be used with NexJ CRM. Configuring the NexJ Studio installer The NexJ Studio installer repository consists of a number of files that, when properly configured and placed on a website or file server, provide an installer and update site for NexJ Studio. Setting up NexJ Studio Before you can use NexJ Studio to develop applications or set deployment information, you need to install NexJ Studio and set required preferences. Example environment settings for NexJ CRM deployment The following are example environment settings for a typical NexJ CRM deployment on IBM WebSphere or NexJ Server. Scheme scripts for local users administration Administrators can use Scheme scripts instead of NexJ Admin Console to create accounts for local users and reset user passwords. These scripts help make these tasks more efficient, especially when you need to create specific users prior to deployment. Push notification architecture overview Push notifications in NexJ CRM rely on two components: the push server and push redirector. Notices
