Push4Free

iPush BackOffice is a web-based management system. It is developed in JSP and java servlet. So JDK and Tomcat are requested to run with it, and MySQL too.

iPush administrator can proceed following management items in iPush BackOffice:

• System Monitor
• License Management
• Admin. Management
• Service Management
• User Management
• CGI Access Management
• Report Generator
• Database Backup
• Cluster Management (only for iPush Server Cluster version)

Following 3rd-party software packages are required for running iPush BackOffice:

• JDK: v1.3.x or above (v1.4.x recommended), for Tomcat running
• Tomcat: v4.1
• MySQL: v4.1.x or above (v5.0.x recommended)
• ODBC for MySQL: v3.51.x

The administrator need use any web browser with JVM to access the iPush BackOffice.

iPush BackOffice can be automatically installed and configured during the installation of iPush Server (for Windows and Linux both). There is no any standalone package for iPush BackOffice.

But if you want the iPush BackOffice to run with your existing Tomcat which had been configured (file server.xml changed, exactly) for other application(s), then you can't choose automatical configuration during the installation of iPush Server. You must proceed the Tomcat manual configuration after the iPush Server installation completed. Please check the respective chapter in installation guide of iPush Server for detail.

We show some snapshots of the iPush BackOffice for your reference.

1. Login
2. System Monitor
3. Service Management
4. User Management
5. Report Generator

The most common administration works for iPush BackOffice should be Service Management and User Management before or after your iPush application goes-live. We illustrate these works as following scenario.

Jason is writing a chatroom application (service) with iPush. When user runs the application, it will connect to iPush Server with these information:

• Server IP: <IPUSH_SERVER_IP>
• Port: <IPUSH_SERVER_PORT>
• Group: wildcat
• Product: chatroom
• User ID: foo
• Password: bar

As system design, Jason planned to let all users of the application use the same user ID foo which should be set subject root lobby for both read permission and write permission. Of course, each user can has it's own nickname in application level.

Jason also decided the number of limited concurrent connections for the application (service) and the user ID foo to be 100.

Base on the scenario above, Jason would manipulate his iPush BackOffice as following steps for developing and operating the application:

Step 1. login to iPush BackOffice with administrator account

Step 2. add a service in Service Management

Click the [Add New] in System Management main page.

Then fill the information as Jason's plan:

• Group: wildcat
• Product: chatroom
• Expiration Date: (leave it as default 0000-00-00, means never get expired)
• Limited Connections: 100
• Kick Forerunner: (leave it as default 0, means disabled)
• Lock on Login Error: (leave it as default 0, means disabled)

Click [OK] to create this new service.

Step 3. add an user in User Management

Click the [Add/Import Users] in User Management main page.

Then fill or select the information as Jason's plan:

• Group: wildcat
• Product: chatroom
• User ID: foo
• Password: bar
• Re-Enter Password: bar
• Start Date: (leave it as default 0000-00-00, means account activated anytime)
• Expiration Date: (leave it as default 0000-00-00, means never get expired)
• Read Permission: lobby
• Write Permission: lobby
• Default Permission: (leave it as default -, means no default permission)
• Concurrent Use: 100
• others: (leave them as default)

Click [OK] to create this new user account.

That's it. Jason now can proceed the connecting function call in his program with the information illustrated:

ipushTCPConnect(<IP>, <PORT>, "wildcat", "chatroom", "foo", "bar")

After the connection between the application and iPush Server is established, proceed the function call for subscribing chatting message from chatroom1:

ipushSubSubject("lobby.chatroom1")

Proceed the function call for sending a chatting message "hello" to iPush Server on chatroom1:

ipushSendNPSubjectData("lobby.chatroom1", "hello")

The iPush Server will push the message "hello" to all subscribers of chatroom1.

There are three iPush BackOffice CGIs (JSP files) are provided for outside system or application to access the iPush user database. Any program can call these CGIs with HTTP PUT or GET methods to get response from iPush BackOffice for respective request.

Here are the CGIs brief:

1. auto_adduser.jsp provides the following functions:
   • add new user account
   • edit specific user account information
   • delete specific user account
   • suspend specific user account
   • restart specific user account
   • check specific user status
   • check iPush BackOffice version number
2. edit_permission.jsp provides the following functions:
   • edit the read permission of specific user (permission for receiving message)
   • edit the write permission of specific user (permission for sending message)
   • edit the default permission of specific user (default permission for receiving message)
3. check_permission.jsp provides the following functions:
   • check the password of specific user.
   • check the read permission of specific user
   • check the write permission of specific user
   • check the default permission of specific user

More details of using respective CGI, please refer to the programming guide for each CGI.

For security reason, administrator must grant any CGI access in iPush BackOffice before it gets invoked. Please check the CGI Management section in iPush BackOffice User Manual.