Previous Topic

Book Contents

Book Index

Next Topic

Chat without Backend

Example content of the 'chat.properties' file for Chat used without any back end application:

chat.authenticationByUsernameEnabled=false

chat.lb.logLevel=debug

chat.jpa.javax.persistence.jdbc.url=jdbc:oracle:thin:@pv03srv:1521:orcl

chat.jpa.javax.persistence.jdbc.user=CHAT

chat.jpa.javax.persistence.jdbc.password=CHAT

chat.jpa.javax.persistence.jdbc.driver=oracle.jdbc.OracleDriver

chat.jpa.eclipselink.target-database=Oracle11

chat.userProvider=de.usu.v4u.backend.none.UserProvider

chat.ticketProvider=de.usu.v4u.backend.none.TicketProvider

Notes:

In this scenario, the Chat does not synchronize its users with any external database and no ticket creation is performed.

  • chat.authenticationByUsernameEnabled=false

    This parameter enables the possibility for the users to log in under different persons. It is intended for testing purposes only and MUST BE SET to FALSE in live production environments.

  • chat.lb.logLevel=debug

    Log level, keep the default value.

  • chat.jpa.javax.persistence.jdbc.url=jdbc:oracle:thin:@pv03srv:1521:orcl
  • chat.jpa.javax.persistence.jdbc.user=CHAT
  • chat.jpa.javax.persistence.jdbc.password=CHAT
  • chat.jpa.javax.persistence.jdbc.driver=oracle.jdbc.OracleDriver

    Parameters defining the database connection (same as in other scenarios).

  • chat.userProvider=de.usu.v4u.backend.none.UserProvider
  • chat.ticketProvider=de.usu.v4u.backend.none.TicketProvider

    These lines specify zero back end connection.

See Also

Installation Properties

Chat with Valuemation

Chat with ServiceConnector