Mobile value-added MMS Platform Implementation Plan Scheme (SP Journal group) __cmpp

A, MMS platform Implementation plan

1. 1 Project Information

1. 1. 1 Project Scope

The scope of the project requirements are: the construction of MMS platform to meet the news network, Newspaper group interaction, voting activities, readers feedback, MMS news materials, MMS information order and so on

1. 1.2 Construction Unit

Newspaper group.

1. 1.3 Contractor

Co., Ltd. qq:84401116 Tel 13950404552

1.2. Deployment Scenarios

L Operating System:

Using Microsoft Windows 2000 or Windows 2003 or Linux, or Uinx

L Database:

Microsoft SQL Server 2000

or ORACLE10.0 1.3 Department step 1. 3.1 Program Installation

1 in the gateway Server installed MMS Gateway program, the main role: mainly for the MMS center with China Mobile, connection for information exchange.

2 MMS Platform Management background installed on the Web server, the main role: mainly for business add, business management, business statistics. 1.3.2 Specific Configuration installation method

MMS platform is mainly divided into two parts: Gateway (Application Mmsapp) and background management (Web program Mmsweb). Database SQL Server

Restores the backed up database file Mms.bak (the exact file name to the actual file) to the new database name, such as MMS. Users who are assigned instructions to this database, such as MMS Oracle

Create a new Oracle Tablespace (such as: MMS), user (such as: MMS). Once created, import the mms_oracle.dmp files in the database directory into the databases with imp command, such as Imp MMS/MMS@ORCL. Gateway

MMS Platform is based on the Java environment, so you have to install more than JDK1.5, and set the relevant Java environment variables (specific settings, here no longer do the narration, Baidu or related books can find the relevant settings method).

In the Mmsapp folder, the gateway program runs the Startup.bat in the directory to run the gateway program. Gateway configuration file Description

There are three profiles under the Gateway Mmsapp, Mm7config.xml,connconfig.xml,config.properties, the first two are API provided, and the next one is provided by our platform. Connconfig.xml need not modify mm7config.xml

This profile refers to the "MM7 API user manual. doc" config.properties

Primarily used to configure Gateway database links and the path to save media files

#数据库连接

#SqlServer2000配置

#DBType =0

#DBDriver =com.microsoft.jdbc.sqlserver.sqlserverdriver

#DBUrl =jdbc:microsoft:sqlserver://127.0.0.1:1433;databasename=mms

#DBUser =sa

#DBPass =manager

#SqlServer2005配置

#DBDriver =com.microsoft.sqlserver.jdbc.sqlserverdriver

#DBUrl =jdbc:sqlserver://127.0.0.1:1433;databasename=mms

#DBUser =sa

#DBPass =manager

#Oracle配置

Dbtype=1

Dbdriver=oracle.jdbc.driver.oracledriver

Dbuser=mms

Dbpass=mms

Dburl=jdbc:oracle:thin:@127.0.0.1:1521:orcl

Submitsql=select * TB_SYS_MT where state=0 and time <sysdate and rownum<20

corpid=802043

spnumber=08816

Sendfilepath=f:\\medias\\

Recvfilepath=f:\\medias\\

license=251e1a1c3611505659435341451e0002784b594c6349

Note: Sendfilepath and Recvfilepath are generally set to one to

1.4 Division of Labor Interface

1.4.1 Buyer is responsible for the scope

The buyer is responsible for the implementation of the basic conditions of the project such as space/environment, power supply and transmission circuit dispatching.

The buyer is responsible for the installation of equipment, cabinets and cables for the current period.

The buyer is responsible for providing access to mobile MMS access parameters

1.4.2 Coordination Matters

(1) Confirm the required Management Center deployment server;

(2) When installing the server Management personnel, provide the corresponding server remote login user password;

(3) After the deployment is completed, and mobile testing

1.4.3 Seller is responsible for the scope

The seller is responsible for the installation and commissioning of the MMS platform, submitting the project documentation and implementing the training as planned.

two. Project implementation Plan 2. 1 Project Schedule

My company will provide engineering installation, testing and commissioning of the personnel and materials, installation work by my company's senior engineers. The following is a preliminary schedule of project implementation

Objective: To build mobile value-added services infrastructure platform, MMS platform. Test access to Mobile

Construction method: Remote login Server installation, commissioning.

Our project implementation began to install. Assuming May 1 begins.

Date	Work content	Staff	Duration
May 1	MMS Platform Installation Configuration	We are responsible for installing the configuration You are responsible for the server environment	1 days
May 2	MMS Platform Test Access Mobile MMS Center	We are responsible for debugging mobile MMS Center You are responsible for providing access to mobile MMS parameters. You, with the sending mobile phone MMS, for business debugging	2 days
May 5	MMS Platform Software Training	Our technical training of your technology	2 days
Total			5 days

2.2 Platform installation and debugging

I will provide platform for on-site installation, testing and commissioning of personnel, installation work by our senior engineers. 2.3 Testing of the platform.

After the completion of the project implementation, we will assist your organization to provide platform test access, to complete the platform and Mobile MMS Center test access work. 2. 4 Training Program

In order to build the platform project smoothly and put into use, the system can run well, improve the work efficiency, achieve the expected goal of system construction, the system users and maintenance personnel to carry out the application, operation and technical maintenance training is an essential link. < c19> training methods

To the technical personnel, the user and the management personnel adopts the method and the system which the gradual training.

Training: System software training, training will be in the system before the installation and commissioning, to ensure that the system installation and commissioning, mainly through the network, mail, telephone, training

                                

Third, Service Commitment 3.1 Technical services and support

as a professional MMS platform supplier, I set up a technical maintenance department 24-hour maintenance, technical maintenance personnel 24-hour arrangement qq,msn online at any time to resolve problems. 3.2 Quality assurance

ensure that the software provided within 1 years of normal operation, and in a reliable operation cycle, long-term including technical advice, telephone support, remote fault analysis and other content of the free technical services. 3.3 After-sales service provided by

Remote Installation Services

According to the requirements of the project, provide remote Installation services, according to the end user's technical requirements, the project system Management, assign a special project leader to develop project implementation plan, responsible for the implementation of the project. 3.4 after-sale safety equipment Maintenance

for the user to buy MMS platform products to provide one year free service. 3.5 service mode and troubleshooting response time 3.5.1 Technical support

Telephone, fax, letter consultation: Use of telephone, fax, letter consultation and other means in the working hours by the Professional engineer at any time to answer the user about the purchase, training consulting, answer customer installation, operation, maintenance and other aspects of technical problems, provide 7*24-hour e-mail and telephone advisory services.

After-Sales service hotline:

e- Mail: 3.5.2 Emergency Response time

Major failure--the impact of normal use and system operation of the major fault hidden trouble: 0.5-hour response, technical support engineer 4 hours to arrive at the scene, hardware failure 6-hour replacement processing completed, the failure to deal with the system after the normal operation, 24 hours to submit processing reports.

General fault--------------------0.5-hour response, 7x24-hour remote technical support, 48-hour failure to eliminate or upgrade to a major failure, all in accordance with major fault handling requirements. Failure processing completed 48 hours to submit a report.