Configuring application with the Setup wizard

From the Setup wizard, you enter information about your license, database connection, user identity system, email system, and system admin credentials.

After you've installed the application, the Setup wizard runs automatically. Here you can find an overview of the setup process.

You can rerun the Setup wizard if required, as described in Starting Setup wizard manually.

License Settings

On the License Settings page, you enter the license key you purchased (you can retrieve your purchased keys by logging into or click Continue to accept the local system license.

Next, on the License page, you select the type of deployment environment: production or development.

Encryption Key Management

All customer data is encrypted anywhere it is at rest. On the Encryption Key Management page, you can choose how you want to manage keys.

Figure: An Encryption Key Management page

An Encryption Key Management page in the Setup wizard.

If you choose Local Key Provider, Jive stores a master key used to encrypt and decrypt data on the server's file system. This is the default option.

Alternatively, you can choose to leverage an Amazon Web Services (AWS) account to use AWS Key Management Service (KMS) to encrypt and decrypt the secondary keys — Amazon KMS Key Provider. If you choose this option, you need to configure the following settings:

  • Customer Master Key ID: The ID of the CMK previously generated on AWS KMS. It needs to be a symmetric key.
  • Region: The AWS Region where the AWS KMS service is configured.
  • Data Key Strength: AES encryption strength. You can choose to use 128 or 256-bits encryption. We recommend to use AES-256; this is the default option.
  • Use AWS IAMROLE: If Jive is running on AWS EC2, you can configure an IAM instance role on the server and Jive will automatically pick it up. In this case, set this property to true. Otherwise, leave it as false and configure the IAM access keys.
  • Access Key ID and Secret Key ID: The keys provided by AWS IAM to access AWS services programmatically. The IAM user requires read access to the appropriate AWS KMS Customer Master Key. These keys are used if you do not use a pre-configured IAM instance role.

After you specify the parameters, click Test Connection with KMS to ensure that details provided are appropriate and that the connection can be established successfully.

Database settings

On the Database Settings page, you specify how to connect to the application database. You can use the included local system database, or you can choose an external database. If you choose the standard database connection or JNDI datasource, you are prompted for required settings after you click Continue.

Figure: An example of a standard connection configuration

Database setup

User settings

On the User Settings page, you specify the system that the application should use for the user and group data. By default, the Setup wizard uses the user and group database tables from the application database.

  • If you choose Default and then click Continue, you go to the User Profile Name Configuration page. There, you are prompted to specify whether user profiles should provide combined or separate fields for a user to enter their name. For a new installation, we recommend that you specify separate fields. If you're upgrading from an instance that used one field, you should probably keep one field.
  • Next, on the Username Case Sensitivity Configuration page, choose whether case sensitivity should be used to look up user names during account creation or login. For a new installation using the default user system, you should choose case-insensitive lookups. Note that with this option, user name values must differ from one another in ways other than case alone.

Activity engine settings

On the Activity Engine Settings page, you specify the endpoints and database settings for the Activity Engine.

Other settings

You should specify defaults for feeds (such as RSS) and email sent and received by the application.

You can change these settings later in the Admin Console.

  1. Set site basics, including its URL and name.
    Setting Description
    Site URL The URL that people can enter in the browser address bar to reach the community.
    Space Name The name that should be displayed as the name of the community, such as on the home page.
  2. If this node is an application server node that's part of a cluster, use these settings to enable clustering for this node and to specify the address of the cache server that the cluster will use. For more information on clustering, see Clustering in Jive and In-memory caching.
    Setting Description
    Clustering Enabled or Disabled Select Enabled to indicate that this node is part of a cluster of application server nodes. If you enable clustering, you need to specify at least one cache server address.
    Cache Server Addresses For clustered installations, enter the domain name or IP address of at least one cache server.
  3. Connect to your Search service. You have the option of either connecting to Jive's Cloud Search service or installing and connecting to an On-Premise Search service. Use these settings to connect to your Search service.
    Setting Options Description
    On-Premise Search On-Premise Search Service Host Enter the host name that Jive can use to connect to the Search service. For On-Premise Search, this is the host name for the node where you installed Search. The default is localhost. Refer to system requirements for information on Search node size.
    On-Premise Search Service Port Enter the TCP port that Jive can use to connect to the Search service. The default is 30000.
    Cloud Search Search Endpoint For Cloud Search, select the public cloud search endpoint in your area. For connection information, see Search service.
  4. The application can send and receive email. Configure these settings here.
    1. Enter information to be used outgoing emails sent from the community, typically to users.
      Setting Description
      Server Email Name The name displayed in the From box in email sent from the community, such as to welcome new users.
      Server Email Address The email address for the sender in email sent from the community.
    2. Set details for handling outgoing email. For more information on mail server configuration, see Configuring outgoing (SMTP) email.
      Setting Description
      Email Host Host name of an SMTP email server that the community will use to send email.
      Email Port Port to be used for sent email.
    3. Set details for handling incoming email. For more information, see Configuring incoming email.
      Setting Description
      Client Protocol Select the protocol used by the incoming email server that the community will use when receiving email to post discussion replies.
      Client Account Host Host name of the incoming email server.
      Client Account Port Port of the incoming email server.
      Username Username for authenticating with the incoming email server.
      Password Password for authenticating with the incoming email server.

Administrator account

You should specify the system administrator's name, email, and password.

Note: The default user name and password is admin.

Restarting your application

After you finish with the Setup wizard, you are prompted to restart the application. You can do this by using the following commands from a command prompt as the jive user on the target computer:
[root@targethost ~]# sudo su - jiver
[1016][jive@targethost:~]$ jive restart webapp
When the application restarts, the following notification is displayed:
sbs restarted successfully.

Finishing up

After you've successfully finished with the Setup wizard, the application is ready to run. When you next log in to the user interface, you can continue setting it up. For example, you can create your user profile, update the interface theme, start creating simple space hierarchy. You can also send invitations to people to join the community. For more information about community setup, see Setting up community.