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.
While almost all of the values are configurable, you must replace the value in italics for the example to be valid.
Application server settings
The following properties in the server or environment file must be configured for IBM WebSphere, or NexJ Server. Depending on your configuration, you may also need to deploy additional settings which are also described in this section. The XML Attribute and Notes column in the following tables show the attribute names that are used in the environment file.
Overview settings for a typical NexJ CRM deployment
Attribute | XML Attribute and Notes | Value |
---|---|---|
Anonymous HTTP Server URL | httpAnonymousURL HTTP server anonymous content URL. | <http://server.example.com:port/ nexj/anon> |
Authentication Domain | authDomain Authentication domain or Kerberos realm, usually DOMAIN.EXT in capital letters. | <EXAMPLE.COM> |
Authentication Service | authService The Kerberos service principal name (SPN) for the environment. | <HTTP/localhost.example.com> |
Batch Email Recipient List Enabled | batchEmailRecipientListEnabled Enables users to view a list of selected email recipients and modify the list. | false |
Batch Notifications | batchNotifications Enables batch task and document creation notifications. | false |
Birthday Mailers Batch Printing Enabled | birthdayMailerEnabled Enables batch printing of birthday mailers for contacts. | false |
Call Records Enabled | callRecordsEnabled Enables call records functionality. | false |
Client Performance Status Enabled | clientPerfStatusEnabled Enables the client performance banner. | true |
Client Performance Status Mobile Red Criteria | clientPerfStatusMobileRedCriteria Specifies performance banner mobile red criteria space separated values: TOTAL_TIME TOTAL_SQL MAX_RESPONSE_SIZE_IN_KB MAX_LAZY_LOAD . | 1500 45 400 30 |
Client Performance Status Mobile Yellow Criteria | clientPerfStatusMobileYellowCriteria Specifies performance banner mobile yellow criteria space separated values: TOTAL_TIME TOTAL_SQL MAX_RESPONSE_SIZE_IN_KB MAX_LAZY_LOAD . | 750 45 200 15 |
Currency Conversion Enabled | currencyConversionEnabled Enables currency conversion to allow developers to convert values between currencies for the NexJ application. | false |
Debug | debug Enables debugging. | true |
Deployment Location | location The location where you want to deploy NexJ CRM. |
|
Description | description A meaningful description of what is being deployed. | <Local machine with the bootstrap container in the default location> |
Email Draft Enabled | emailDraftEnabled Enables users to preview batch emails before sending them to recipients. | false |
Email Signature Enabled | emailSignatureEnabled Enables users to include email signatures when sending batch emails. | false |
Hierarchy Security Enabled | hierarchySecurityEnabled Enables hierarchy based access for entities, opportunities, and activities. | false |
HTTP Forbidden Enabled | httpForbiddenEnabled Enables the HTTP 403 Forbidden response for a permanent authentication failure. Otherwise, HTTP 404 Not Found is used to hide the existence of an HTTP resource, as a deterrent. | true |
HTTP Report URL | httpReportURL Provides the HTTP URL for reports. | <http://server.example.com:port/nexj/reports> |
HTTP Server URL | httpURL HTTP server URL. | <http://server.example.com:port/nexj/> |
Journal Directory | journalDirectory The directory in which to store the transactional journal. If a relative path is specified then the journal directory is placed under the server data directory. The journal files are placed in a subdirectory named after the node name. | tx${test.clone} |
Name Change Context Audit | nameChangeContextAudit Enables automatic context auditing of changes to the name attribute for audited instances. | true |
Password | password The password corresponding to the deployment user ID. | <Deployment_Password> |
Persistent Session | persistentSession Enables session persistence. Session information is stored using a file system or a database. | true |
Preview Threshold | previewThreshold Maximum document size, in bytes, for automatic preview. | 202,400 |
Push Password | pushPassword Specifies the password of the push user when used with the Push User property or the keystore password when used with the Push Certificate property. | <Push_Password> |
Push Redirector URL | pushRedirectorURL Specifies the host, port, and context path of the push redirector. | <http://localhost:port/nexj/pushRedirect> |
Push Server URLs | pushServerURLs Specifies the list of full paths to each instance of the push server running on each node of the application cluster. Multiple servers are separated with a space. | <http://app1.local:8080/nexj/push> <http://app2.local:8080/nexj/push> |
Push Type | pushType Specifies the Comet mode that the NexJ application users for push notifications. If the selected type isn't supported by the client web browser, polling is used. | streaming |
Push User | pushUser Specifies the user that authenticates with the NexJ application when connecting to the push server. | <Push_ID> |
Read Audit | readAudit Specifies whether to log read actions by users in NexJ CRM based on attributes selected for read audit in the NexJ model. | none |
RPC Privilege | rpcPrivilege The privilege required for access to generic Remote Procedure Call (RPC) protocols. If not set, the access is unrestricted and a validation warning is generated. Generic RPC protocols are HTTP/soap, HTTP/text, HTTP/web, HTTP/xml and EJB. Generic RPC is used by all the clients except for the flat page client. | InternalManage |
Rules for Service Level Agreements | ruleSLA Enables service level agreements functionality for service requests. | false |
Secure Transport Protocol (use SSL) | secureTransport Enables encrypted SSL communication and server authentication. | false |
Type |
|
|
Unit of Work Listener Enabled | uowListenerEnabled Enables the unit of work listener component that shares NexJ CRM transactional data with registered listeners. | false |
Update Audit | updateAudit Determines whether create, update, and delete actions that users perform on objects are logged, for example, changing a contact name. | false |
User | user The ID that will be provided if the server that you deploy to requests an ID and password before allowing metadata to be copied. | <Deployment_ID> |
Additional settings for a typical NexJ CRM deployment
Attribute | XML Attribute and Notes | Value |
---|---|---|
Authentication Group | authGroup The Group ID used for coarse grained authentication. Application users must be part of the group. | nexjusers |
Authentication Protocol | authProtocol The authentication protocol. | custom or spegno |
Cluster Discovery Port | clusterDiscoveryPort The Cluster Manager’s discovery port. | 39001 |
Cluster Discovery Protocol |
| unicast |
Configuration |
The template environment file that is used. | |
Distributed | distributed Enables clustering services. | true |
Keystore Password | keystorePassword The password used for the application server's ssl.keystore file. | text:keypass |
Material Design | materialDesign Reserved for future use. Do not enable. | false |
Message Port | messagePort TCP/IP port used for intra-cluster communication with the Object Queue engine. | 1111 |
Message User | messageUser The user ID used for Object Queue messaging. | <adminID> |
Sample Data | sampleData Specifies whether sample data is generated. | false |
Test | test Specifies whether the server may be used for testing. | false |
LDAP settings for a typical NexJ CRM deployment
Attribute | XML Attribute and Notes | Value |
---|---|---|
Authentication Protocol | ldapAuthProtocol The authentication protocol for connecting the LDAP server. | simple |
Group Context DN | ldapGroupContextDN The distinguished name (DN) used to search for groups. | <LDAP_Group_Context_DN> |
Group Filter | ldapGroupFilter The LDAP filter used to identify objects that are groups. | (objectCategory=group) |
Group Name Attribute | ldapGroupNameAttribute The group attribute that holds the group's name. | sAMAccountName |
Password | ldapPassword The password corresponding to the LDAP user ID. | <LDAP_Password> |
URL | ldapURL The LDAP server URL for determining the user group membership. | <LDAP_URL> |
User | ldapUser The user ID to use to connect to the LDAP server. | <LDAP_User_ID> |
User Context DN | ldapUserContextDN The DN used to search for users. | <LDAP_User_Context_DN> |
User Filter | ldapUserFilter The LDAP filter used to identify objects that are users. | (objectCategory=user) |
User Login Attribute | ldapUserLoginAttribute The login name that is used to authenticate users. | userPrincipalName |
MSSQL database settings
A typical deployment of NexJ CRM requires the following data sources to be configured with the following properties.
The SessionDatabase is required when using session persistence.
The following data sources are required for a typical deployment with MSSQL database:
- AuditLogDatabase
- BI_1_BI_Database
- call:Call
- Conversation
- DefaultRelationalDatabase
- ecr:ECR
- flow:Flow
- LockDatabase
- msg:Messaging
- ObjectQueueDatabase
- rules:Rules
- SessionDatabase
- sso:SSO
- StagingDatabase
- StatDatabase
- uicomp:UIComponent
The suggested properties and values are the same for all data sources.
Data source settings for a typical MSSQL NexJ CRM deployment
Attribute | Value | Notes |
---|---|---|
DataSource | <datasourcename> | |
Adapter | MSSQL | Data source adapter |
Host | <localhost> | Database server host name |
User | <Database_User_ID> | The ID used by the application to access the database |
Path | jtds-1.2.2-7.jar | Name of the JDBC driver JAR file |
Port | 1433 | Database server port number |
Database | <Database_Name> | The name of the database the application will access |
Password | <Database_Password> | The password corresponding to the database user ID |
Oracle database settings
A typical deployment of NexJ CRM requires the following data sources to be configured with the following properties.
The SessionDatabase is required when using session persistence.
The following data sources are required for a typical deployment with Oracle database:
- AuditLogDatabase
- BI_1_BI_Database
- call:Call
- Conversation
- DefaultRelationalDatabase
- ecr:ECR
- flow:Flow
- LockDatabase
- msg:Messaging
- ObjectQueueDatabase
- rules:Rules
- SessionDatabase
- sso:SSO
- StagingDatabase
- StatDatabase
- uicomp:UIComponent
The suggested properties and values are the same for all data sources.
Data source settings for a typical Oracle NexJ CRM deployment
Attribute | Value | Notes |
---|---|---|
Data Source | <datasourcename> | |
Adapter | Oracle11g | Data source adapter. |
Host | <localhost> | Dababase server host name. |
User | <Database_User_ID> | The ID used by the application to access the database. |
Path | ojdbc6-11.2.0.3.jar | Name of the JDBC driver JAR file. |
Port | 1521 | Database server port number. |
Database | <Database_Name> | The name of the database the application will access. |
Password | <Database_Password> | The password corresponding to the database user ID. |
Query Timeout | 10 | Number of seconds before queries timeout. |
Warning Timeout | 250 | Number of milliseconds before a timeout warning occurs for longrunning queries. |
Channel connection settings
A typical deployment of NexJ CRM requires that you add certain channels to the environment file.
File channel connection settings
AddressLookup channel connection settings for a typical NexJ CRM deployment
Attribute | Value | Notes |
---|---|---|
Channel | AddressLookup | |
Type | FileConnection | The type of channel connection to use. |
Incoming Directory | <\\server.domain.ext\AddressLookup \incoming> | The full path to the incoming directory. In XML, this attribute is named incomingDirectory . |
Outgoing Directory | <\\server.domain.ext\AddressLookup \outgoing> | The full path to the outgoing directory. In XML, this attribute is named outgoingDirectory . |
Temporary Directory | <\\server.domain.ext\AddressLookup \temporary> | The full path to the temporary directory. In XML, this attribute is named temporaryDirectory . |
Processed Directory | <\\server.domain.ext\AddressLookup \processed> | The full path to the processed directory. In XML, this attribute is named processedDirectory . |
Pattern | *.zip | Indicates the file pattern to search for in the lookup. |
Transaction Timeout | 7200 | Indicates the number of milliseconds before the lookup times out. |
HTTP channel connection settings
ExchangeEWSNotificationReceiver channel connection settings for a typical NexJ CRM deployment
Attribute | Value | Notes |
---|---|---|
Channel | ExchangeEWSNotificationReceiver | |
Type | HTTPConnection | The type of channel connection to use. |
Authentication | none | The type of authentication to use. |
ExchangeEWSSender channel connection settings for a typical NexJ CRM deployment
Attribute | Value | Notes |
---|---|---|
Channel | ExchangeEWSSender | |
Type | HTTPConnection | The type of channel connection to use. |
URL | http://<host>/ews/Exchange.asmx | The host must be that of the Exchange Web Service for the target server. |
User | <HTTP_User_ID> | The user name used to connect to remote HTTP servers. |
Password | <HTTP_User_Password> | The password corresponding to the HTTP User ID. |
Trust | <certificatefile> | The certificate file. |
Authentication | basic | The type of authentication to use. |
readTimeout | 180000 | Timeout (in milliseconds) for outbound HTTP requests. |
Use HTTPS Communication | true | Uses HTTPS communication in the receiver. In XML this attribute is secure . |
Info
ExchangeEWSSender2 and ExchangeEWSSender3 channels are duplicates of ExchangeEWSSender and are also optional channel connections when there is only one entry point for Exchange EWS communication; just one ExchangeEWSSender channel is sufficient in that event.
HelpChannel channel connection settings for a typical NexJ CRM deployment
Attribute | Value | Notes |
---|---|---|
Channel | HelpChannel | For online help functionality. |
Type | HTTPConnection | The type of channel connection to use. |
URL | <https://intranet.example.com:8080/nexj-help/> | The secure user-accessible URL for the server that hosts the help, including the port number, if required. |
InfluxDB channel connection settings for a typical NexJ CRM deployment
Attribute | Value | Notes |
---|---|---|
Channel | monitor:influxdb:HTTPSenderchannel | For persisting performance statistics to InfluxDB. |
Type | HTTPConnection | The type of channel connection to use. |
URL | <https://intranet.example.com:8086/write? db=database/> | The secure user-accessible URL for the server that writes to the specified InfluxDB database, including the port number, if required. |
Kafka channel connection settings
Kafka channel connection settings for a typical NexJ CRM deployment
Attribute | Value | Notes |
---|---|---|
Channel | kafkaChannel | For sending and receiving messages through Apache Kafka. |
Type | KafkaConnection | The type of channel connection to use. |
Encoding | UTF-8 | Character set for serializing and deserializing string messages. |
Topic | kafkaTopic1 | For sender channels, the Kafka topic to send to. If the channel receives input from multiple topics, you can enter a space-separated list of topics. If the channel is used for both sending and receiving, it sends messages to the first topic in the list and receives messages from all the topics in the list including the first one. |
Servers | localhost:9092 | A space-separated list of host/port pairs to use for establishing the initial connection with the Kafka cluster. The client will make use of all available servers irrespective of which servers are specified. |
Max Senders | 16 | Maximum Kafka producers (senders) per server. For unlimited producers, enter -1 as the value. Applies to sender channels only. |
Request Timeout | 25000 | Timeout (in milliseconds) for Kafka requests. |
Warning Timeout | 2000 | Number of milliseconds before a timeout warning occurs for longrunning queries. For infinite timeout, specify 0 as the value. |
Use SSL Security | true | If set to true, requires SSL security. If set to <auto>, defaults to the value of the |
Authentication | basic | Authentication mode. The options are:
|
User | user | Kafka user ID. |
Password | password | The password corresponding to the Kafka user ID. |
Certificate | <certificate> | The certificate and private key for logging in to the remote system. The certificate must be in base64-encoded PKCS #12 representation. |
Trust | <trust> | The X.509 certificate, or the signer's certificate thereof, for the remote system. If unspecified, the server will trust the global trust certificate if it is specified in the environment file. |
Sender Properties | senderPropertyName | Additional Kafka producer properties to be added to the sender channel. For a list of these properties, see http://kafka.apache.org/documentation.html#producerconfigs. |
Receiver Properties | receiverPropertyName | Additional Kafka consumer properties to be added to the receiver channel. For more information, see http://kafka.apache.org/documentation.html#consumerconfigs. |
You can define some attributes both at the channel level and the channel connection level. Channel connection settings override any individual channel settings.
If your NexJ application uses the Avro format to send Kafka messages, the Kafka channel requires additional configuration. For more information, see Additional configuration for sending Avro messages .
Mail channel connection settings
Mail channel connection settings for a typical NexJ CRM deployment
Attribute | Value | Notes |
---|---|---|
Channel | ||
Type | MailConnection | |
Email Account | <user.name@example.com> | User name used to connect to the mail server. In the XML, this attribute is named user . |
Password | <Email_Password> | The password corresponding to the Email Account. |
Folder | INBOX | The incoming messages folder. In XML, this folder is named inFolder . |
Receiver Protocol | pop3 | The protocol to use for incoming messages. In XML, this attribute is named inProtocol . |
Receiver Host | <mailserver.example.com> | The mail server host for incoming messages. In XML, this attribute is named inHost . |
Receiver Encryption | SSL | The type of channel connection to use. In XML, this attribute is named inEncryption . |
Sender Email | <outmail@example.com> | The default email address for the sender. In XML, this attribute is named from . |
Sender Protocol | smtp | The protocol to use for outgoing messages. In XML, this attribute is named outProtocol . |
Sender Host | <outmailserver.example.com> | The mail server host for outgoing messages. In XML, this attribute is named outHost . |
Message queue channel connection settings
CustomBatchProcessQueue channel connection settings for a typical NexJ CRM deployment
Attribute | Value | Notes |
---|---|---|
Channel | CustomBatchProcessQueue | |
User | <JMS_Queue_User_ID> | User name used to connect to the JMS queue. |
Password | <JMS_Queue_Password> | The password corresponding to the JMS queue user ID. |
TCP channel connection settings
IOSNotificationSender channel connection settings for a typical NexJ CRM deployment
Attribute | Value | Notes |
---|---|---|
Channel | IOSNotificationSender | |
Type | TCPConnection | The type of channel connection to use. |
Certificate | <certificate> | The contents of the push certificate. |
Password | <password> | The password used when exporting the private key. |
Use SSL/TLS | true | In XML, this attribute is namedsecure . |
Sender Read Timeout | 2000 |
SOA connection settings
A typical deployment of NexJ CRM requires that you add certain SOA connections to the environment file.
The following SOA connections are required for a typical deployment:
- nexj:act:ActTemplate:1.0
- nexj:act:ActivityPlan:1.0
- nexj:act:ApprovalObject:1.0
- nexj:act:DocumentService:1.0
- nexj:act:Task:1.0
- nexj:call:CallScriptTemplate:1.0
- nexj:call:InboundCall:1.0
- nexj:call:InboundCallComponentClient:1.0
- nexj:crm:AssignmentModel:1.0
- nexj:crm:Contact:1.0
- nexj:crm:EntityParticipation:1.0
- nexj:crm:Household:1.0
- nexj:crm:Interaction:1.0
- nexj:crm:Note:1.0
- nexj:crm:Person:1.0
- nexj:crm:RelatedObjectWorkQueue:1.0
- nexj:crm:ScheduleItem:1.0
- nexj:crm:Task:1.0
- nexj:crm:User:1.0
- nexj:crm:UserPerson:1.0
- nexj:flow:FlowObject:1.0
- nexj:flow:QuestionnaireService:1.0
- nexj:flow:SecurityDelegateService:1.0
- nexj:ilm:DistributeActionCommandClient:1.0
- nexj:ilm:Lead:1.0
- nexj:ilm:LeadCallScriptTemplate:1.0
- nexj:ilm:LeadComponentClient:1.0
- nexj:leaf:Leaflet:1.0
- nexj:rules:CreateActivityPlanCommandClient:1.0
- nexj:rules:CreateTaskCommandClient:1.0
- nexj:rules:MessageActionCommandClient:1.0
- nexj:rules:Rule:1.0
- nexj:rules:SetActionCommandClient:1.0
- nexj:soa:Audit:1.0 nexj:soa:Bulletin:1.0
- nexj:soa:ConversationService:1.0
- nexj:soa:DataMatchService:1.0
- nexj:soa:DataMatchServiceConfiguration:1.0
- nexj:soa:DesktopBeaconPushService:1.0
- nexj:soa:DesktopPushService:1.0
- nexj:soa:DesktopStreamRefreshPushService:1.0
- nexj:soa:EmailNotificationService:1.0
- nexj:soa:MobilePushService:1.0
- nexj:soa:PortletRegistry:1.0
- nexj:soa:Registry:1.0
- nexj:soa:SubscriptionEngineService:1.0
- nexj:soa:UserRegistry:1.0
- nexj:soa:UserRegistryClient:1.0
- nexj:sso:Authentication:1.0
- nexj:ui:ActTemplateComponentClient:1.0
- nexj:ui:ApprovalPlanStepComponentClient:1.0
- nexj:ui:ApprovalPlanTemplateComponentClient:1.0
- nexj:ui:AssignmentModelComponentClient:1.0
- nexj:ui:AssignmentModelRoleComponentClient:1.0
- nexj:ui:ClientKYCComponentClient:1.0
- nexj:ui:DocumentMgrItemComponentClient:1.0
- nexj:ui:EntityComponentClient:1.0
- nexj:ui:PersonComponentClient:1.0
- nexj:ui:TaskComponentClient:1.0
- nexj:ui:UIComponent:1.0
- nexj:ui:UIComponentClient:1.0
- nexj:ui:UserComponentClient:1.0
- nexj:ui:WorkQueueComponentClient:1.0
- nexj:ui:WorkQueueItemRelatedObject:1.0
The suggested attributes and values are the same for all SOA connections.
Generic SOA connection settings for a typical NexJ CRM deployment
Attribute | Value | Notes |
---|---|---|
Service | <servicename> | |
Address | <http://hostname:port/nexj/text> | The host (and port if applicable) must be that of the target service server. |
Binding | context | The binding for connecting to the service. Overrides the binding from the registry. |
Authentication | basic | The authentication mode for connecting to the service. Overrides the authentication mode from the registry. |
User | <Service_User_ID> | User name used to log into the service. |
Password | <Service_Password> | The password corresponding to the service user ID. |
The following table contains additional properties.
Attribute | Value | Notes |
---|---|---|
system | #t (or true) | Determines that the source service runs in an elevated privileges mode. |
Example XML environment file for NexJ CRM deployment on NexJ Server
The settings from the previous sections are reflected in the following example environment file:
<Environment authDomain="<EXAMPLE.COM>" authService="<HTTP/localhost.example.com>" batchEmailRecipientListEnabled="false" batchNotifications="false" birthdayMailerEnabled="false" callRecordsEnabled="false" clientPerfStatusEnabled="true" clientPerfStatusMobileRedCriteria="1500 45 400 30" clientPerfStatusMobileYellowCriteria="750 45 200 15" currencyConversionEnabled="false" debug="true" description="Local machine with the bootstrap container in the default location" emailDraftEnabled="false" emailSignatureEnabled="false" hierarchySecurityEnabled="false" httpForbiddenEnabled="true" httpReportURL="<http://server.example.com:port/nexj/reports>" httpURL="<http://server.example.com:port/nexj/>" journalDirectory="tx${test.clone}" ldapAuthProtocol="simple" ldapGroupContextDN="<LDAP_Group_Context_DN>" ldapGroupFilter="(objectCategory=group)" ldapGroupNameAttribute="sAMAccountName" ldapPassword="<LDAP_Password>" ldapURL="<LDAP_URL>" ldapUser="<LDAP_User_ID>" ldapUserContextDN="<LDAP_User_Context_DN>" ldapUserFilter="(objectCategory=user)" ldapUserLoginAttribute="userPrincipalName" location="c:\java\container\deploy" nameChangeContextAudit="true" password="<Deployment_Password>" persistentSession="true" previewThreshold="202400" pushPassword="<Push_Password>" pushRedirectorURL="<http://localhost:port/nexj/pushRedirect>" pushServerURLs="<http://app1.local:8080/nexj/push http://app2.local:8080/nexj/push>" pushType="streaming" pushUser="<Push_ID>" readAudit="none" rpcPrivilege="InternalManage" ruleSLA="false" secureTransport="false" type="Generic" updateAudit="false" uowListenerEnabled="false" user="<Deployment_ID>"> <PKIKeyPairs> <PKIKeyPair keystore="<keystore>" name="<adminID>" password="testPass"/> </PKIKeyPairs> <DataSourceConnections> <RelationalDatabaseConnection adapter="MSSQL" database="<Database_Name>" host="<localhost>" password="<Database_Password>" path="jtds-1.2.2-7.jar" port="1433" user="<Database_User_ID>"> <DataSource name="DefaultRelationalDatabase"/> <DataSource name="rules:Rules"/> <DataSource name="uicomp:UIComponent"/> <DataSource name="Conversation"/> <DataSource name="ecr:ECR"/> <DataSource name="msg:Messaging"/> <DataSource name="SessionDatabase"/> <DataSource name="flow:Flow"/> <DataSource name="StagingDatabase"/> <DataSource name="call:Call"/> <DataSource name="sso:SSO"/> <DataSource name="StatDatabase"/> <DataSource name="ObjectQueueDatabase"/> <DataSource name="AuditLogDatabase"/> <DataSource name="LockDatabase"/> </RelationalDatabaseConnection> <RelationalDatabaseConnection adapter="MSSQL" database="<Database_Name_BI>" host="<localhost>" password="<Database_Password>" path="jtds-1.2.2-7.jar" port="1433" user="<Database_User_ID>"> <DataSource name="BI_1_BI_Database"/> </RelationalDatabaseConnection> <FileStorageConnection adapter="Generic" dataDirectory="C:\file\attachment\data" temporaryDirectory="C:\file\attachment\temp"> <DataSource name="Attachment"/> <DataSource name="FileExport"/> </FileStorageConnection> </DataSourceConnections> <ChannelConnections> <MessageQueueConnection channel="CustomBatchProcessQueue" password="<JMS_Queue_Password>" user="<JMS_Queue_User_ID>"/> <MailConnection channel="Mail" from="<outmail@example.com>" inFolder="INBOX" inHost="<mailserver.example.com>" inProtocol="pop3" outHost="<outmailserver.example.com>" outProtocol="smtp" password="<Email_Password>" user="<user.name@example.com>"/> <HTTPConnection authentication="basic" channel="ExchangeEWSSender" password="<HTTP_User_Password>" secure="true" trust="<certificateFile>" url="https://<host>/ews/Exchange.asmx" user="<HTTP_User_ID>"/> <HTTPConnection authentication="credential" channel="ExchangeEWSSender2" password="<HTTP_User_Password>" secure="true" trust="<certificateFile>" url="https://<host>/ews/Exchange.asmx" user="<HTTP_User_ID>"/> <HTTPConnection authentication="basic" channel="ExchangeEWSSender3" password="<HTTP_User_Password>" secure="true" trust="<certificateFile>" url="https://<host>/ews/Exchange.asmx" user="<HTTP_User_ID>"/> <HTTPConnection authentication="none" channel="ExchangeEWSNotificationReceiver"/> <HTTPConnection channel="BESNotificationSender" password="<HTTP_User_Password>" secure="true" trust="<certificateFile>" user="BESPushTest"/> <HTTPConnection authentication="none" channel="JasperReportData"/> <HTTPConnection authentication="perimeter" channel="JasperServer"/> <HTTPConnection authentication="none" channel="NotificationUnsubscribeChannel" password="<HTTP_User_Password>"/> <FileConnection channel="ReportingOutputFileChannel" outgoingDirectory="C:\<file>\fileChannels\reporting\"/> </ChannelConnections <SOAConnections> <SOAConnection auth="perimeter" binding="context" service="nexj:act:ActivityPlan:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:act:ActTemplate:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:act:ApprovalObject:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:act:DocumentService:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:act:Task:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:call:InboundCall:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:crm:AssignmentModel:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:crm:EntityParticipation:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:crm:UserPerson:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:flow:FlowObject:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:flow:QuestionnaireService:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:flow:SecurityDelegateService:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:ilm:DistributeActionCommandClient:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:ilm:Lead:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:leaf:Leaflet:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:rules:CreateActivityPlanCommandClient:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:rules:CreateTaskCommandClient:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:rules:MessageActionCommandClient:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:rules:Rule:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:rules:SetActionCommandClient:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:Audit:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:Bulletin:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:ConversationService:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:DataMatchService:1.0"> <Properties> <Property name="system" value="#t"/> </Properties> </SOAConnection> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:DataMatchServiceConfiguration:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:DesktopBeaconPushService:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:DesktopPushService:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:DesktopStreamRefreshPushService:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:EmailNotificationService:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:MobilePushService:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:PortalIntegration:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:PortletRegistry:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:Registry:1.0"> <Properties> <Property name="system" value="#t"/> </Properties> </SOAConnection> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:SubscriptionEngineService:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:UserRegistry:1.0"> <Properties> <Property name="system" value="#t"/> </Properties> </SOAConnection> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:UserRegistryClient:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:ui:ObjectComponentClient:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:ui:UIComponent:1.0"> <Properties> <Property name="system" value="#t"/> </Properties> </SOAConnection> <SOAConnection auth="perimeter" binding="context" service="nexj:sso:Authentication:1.0"> <Properties> <Property name="system" value="#t"/> </Properties> </SOAConnection> <SOAConnection auth="perimeter" binding="context" service="nexj:crm:Person:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:crm:User:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:crm:Household:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:crm:Task:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:ui:WorkQueueItemRelatedObject:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:crm:ScheduleItem:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:crm:Note:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:crm:Interaction:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:soa:NotificationService:1.0"/> <SOAConnection auth="perimeter" binding="context" service="nexj:ui:UIComponentClient:1.0"/> </SOAConnections> </Environment>