You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@inlong.apache.org by gi...@apache.org on 2021/07/07 08:06:35 UTC
[incubator-inlong-website] branch asf-site updated: Automated
deployment: Wed Jul 7 08:06:24 UTC 2021
0ee3dc949a88ee24ec8571bd940d829c21610104
This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-inlong-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new efc95b8 Automated deployment: Wed Jul 7 08:06:24 UTC 2021 0ee3dc949a88ee24ec8571bd940d829c21610104
efc95b8 is described below
commit efc95b8c73b76c0a002486dafd7d7d22c2242386
Author: gosonzhang <go...@users.noreply.github.com>
AuthorDate: Wed Jul 7 08:06:24 2021 +0000
Automated deployment: Wed Jul 7 08:06:24 UTC 2021 0ee3dc949a88ee24ec8571bd940d829c21610104
---
.../modules/manager/img/image-1624431177918.png | Bin 0 -> 182769 bytes
.../modules/manager/img/image-1624431271642.png | Bin 0 -> 28296 bytes
.../modules/manager/img/image-1624431306077.png | Bin 0 -> 19793 bytes
.../modules/manager/img/image-1624431333949.png | Bin 0 -> 18348 bytes
.../modules/manager/img/image-1624431416449.png | Bin 0 -> 11219 bytes
.../modules/manager/img/image-1624431435574.png | Bin 0 -> 32810 bytes
.../modules/manager/img/image-1624431594406.png | Bin 0 -> 11069 bytes
.../modules/manager/img/image-1624431617259.png | Bin 0 -> 22671 bytes
.../modules/manager/img/image-1624431713360.png | Bin 0 -> 22250 bytes
.../modules/manager/img/image-1624431787323.png | Bin 0 -> 32927 bytes
.../modules/manager/img/image-1624432002615.png | Bin 0 -> 417736 bytes
.../modules/manager/img/image-1624432022859.png | Bin 0 -> 261703 bytes
.../modules/manager/img/image-1624432076857.png | Bin 0 -> 82036 bytes
.../modules/manager/img/image-1624432092795.png | Bin 0 -> 128241 bytes
.../modules/manager/img/image-1624432114765.png | Bin 0 -> 59740 bytes
.../modules/manager/img/image-1624432235900.png | Bin 0 -> 82818 bytes
.../modules/manager/img/image-1624432254118.png | Bin 0 -> 49442 bytes
.../modules/manager/img/image-1624432286674.png | Bin 0 -> 28724 bytes
.../modules/manager/img/image-1624432445002.png | Bin 0 -> 173921 bytes
.../modules/manager/img/image-1624432458971.png | Bin 0 -> 102406 bytes
.../modules/manager/img/image-1624432474526.png | Bin 0 -> 68181 bytes
.../modules/manager/img/image-1624432496461.png | Bin 0 -> 157363 bytes
.../modules/manager/img/image-1624432515850.png | Bin 0 -> 119282 bytes
.../modules/manager/img/image-1624432535541.png | Bin 0 -> 78171 bytes
.../modules/manager/img/image-1624432652141.png | Bin 0 -> 111394 bytes
.../modules/manager/img/image-1624432668340.png | Bin 0 -> 81948 bytes
.../modules/manager/img/image-1624432740241.png | Bin 0 -> 43740 bytes
.../modules/manager/img/image-1624432759224.png | Bin 0 -> 36743 bytes
.../modules/manager/img/image-1624432778845.png | Bin 0 -> 49630 bytes
.../modules/manager/img/image-1624432797226.png | Bin 0 -> 41212 bytes
.../modules/manager/img/image-1624432829313.png | Bin 0 -> 38842 bytes
.../modules/manager/img/image-1624433272455.png | Bin 0 -> 29913 bytes
docs/en-us/modules/manager/user_manual.md | 282 +++++++++++++++++++++
docs/zh-cn/modules/manager/user_manual.md | 241 ++++++++++++------
.../modules/manager/img/image-1624431177918.png | Bin 0 -> 182769 bytes
.../modules/manager/img/image-1624431271642.png | Bin 0 -> 28296 bytes
.../modules/manager/img/image-1624431306077.png | Bin 0 -> 19793 bytes
.../modules/manager/img/image-1624431333949.png | Bin 0 -> 18348 bytes
.../modules/manager/img/image-1624431416449.png | Bin 0 -> 11219 bytes
.../modules/manager/img/image-1624431435574.png | Bin 0 -> 32810 bytes
.../modules/manager/img/image-1624431594406.png | Bin 0 -> 11069 bytes
.../modules/manager/img/image-1624431617259.png | Bin 0 -> 22671 bytes
.../modules/manager/img/image-1624431713360.png | Bin 0 -> 22250 bytes
.../modules/manager/img/image-1624431787323.png | Bin 0 -> 32927 bytes
.../modules/manager/img/image-1624432002615.png | Bin 0 -> 417736 bytes
.../modules/manager/img/image-1624432022859.png | Bin 0 -> 261703 bytes
.../modules/manager/img/image-1624432076857.png | Bin 0 -> 82036 bytes
.../modules/manager/img/image-1624432092795.png | Bin 0 -> 128241 bytes
.../modules/manager/img/image-1624432114765.png | Bin 0 -> 59740 bytes
.../modules/manager/img/image-1624432235900.png | Bin 0 -> 82818 bytes
.../modules/manager/img/image-1624432254118.png | Bin 0 -> 49442 bytes
.../modules/manager/img/image-1624432286674.png | Bin 0 -> 28724 bytes
.../modules/manager/img/image-1624432445002.png | Bin 0 -> 173921 bytes
.../modules/manager/img/image-1624432458971.png | Bin 0 -> 102406 bytes
.../modules/manager/img/image-1624432474526.png | Bin 0 -> 68181 bytes
.../modules/manager/img/image-1624432496461.png | Bin 0 -> 157363 bytes
.../modules/manager/img/image-1624432515850.png | Bin 0 -> 119282 bytes
.../modules/manager/img/image-1624432535541.png | Bin 0 -> 78171 bytes
.../modules/manager/img/image-1624432652141.png | Bin 0 -> 111394 bytes
.../modules/manager/img/image-1624432668340.png | Bin 0 -> 81948 bytes
.../modules/manager/img/image-1624432740241.png | Bin 0 -> 43740 bytes
.../modules/manager/img/image-1624432759224.png | Bin 0 -> 36743 bytes
.../modules/manager/img/image-1624432778845.png | Bin 0 -> 49630 bytes
.../modules/manager/img/image-1624432797226.png | Bin 0 -> 41212 bytes
.../modules/manager/img/image-1624432829313.png | Bin 0 -> 38842 bytes
.../modules/manager/img/image-1624433272455.png | Bin 0 -> 29913 bytes
en-us/docs/modules/manager/user_manual.html | 212 ++++++++++++++++
en-us/docs/modules/manager/user_manual.json | 6 +
en-us/docs/modules/manager/user_manual.md | 282 +++++++++++++++++++++
zh-cn/docs/modules/manager/user_manual.html | 221 ++++++++--------
zh-cn/docs/modules/manager/user_manual.json | 2 +-
zh-cn/docs/modules/manager/user_manual.md | 241 ++++++++++++------
72 files changed, 1212 insertions(+), 275 deletions(-)
diff --git a/docs/en-us/modules/manager/img/image-1624431177918.png b/docs/en-us/modules/manager/img/image-1624431177918.png
new file mode 100644
index 0000000..2014e8c
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624431177918.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624431271642.png b/docs/en-us/modules/manager/img/image-1624431271642.png
new file mode 100644
index 0000000..9dac2ec
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624431271642.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624431306077.png b/docs/en-us/modules/manager/img/image-1624431306077.png
new file mode 100644
index 0000000..c70ee18
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624431306077.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624431333949.png b/docs/en-us/modules/manager/img/image-1624431333949.png
new file mode 100644
index 0000000..0569bc6
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624431333949.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624431416449.png b/docs/en-us/modules/manager/img/image-1624431416449.png
new file mode 100644
index 0000000..9d53a39
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624431416449.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624431435574.png b/docs/en-us/modules/manager/img/image-1624431435574.png
new file mode 100644
index 0000000..724e535
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624431435574.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624431594406.png b/docs/en-us/modules/manager/img/image-1624431594406.png
new file mode 100644
index 0000000..c133174
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624431594406.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624431617259.png b/docs/en-us/modules/manager/img/image-1624431617259.png
new file mode 100644
index 0000000..eaa10b1
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624431617259.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624431713360.png b/docs/en-us/modules/manager/img/image-1624431713360.png
new file mode 100644
index 0000000..fb8658e
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624431713360.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624431787323.png b/docs/en-us/modules/manager/img/image-1624431787323.png
new file mode 100644
index 0000000..23621be
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624431787323.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432002615.png b/docs/en-us/modules/manager/img/image-1624432002615.png
new file mode 100644
index 0000000..b3d4a1e
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432002615.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432022859.png b/docs/en-us/modules/manager/img/image-1624432022859.png
new file mode 100644
index 0000000..25eede7
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432022859.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432076857.png b/docs/en-us/modules/manager/img/image-1624432076857.png
new file mode 100644
index 0000000..3215186
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432076857.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432092795.png b/docs/en-us/modules/manager/img/image-1624432092795.png
new file mode 100644
index 0000000..9a00a88
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432092795.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432114765.png b/docs/en-us/modules/manager/img/image-1624432114765.png
new file mode 100644
index 0000000..380506e
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432114765.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432235900.png b/docs/en-us/modules/manager/img/image-1624432235900.png
new file mode 100644
index 0000000..78fc1e5
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432235900.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432254118.png b/docs/en-us/modules/manager/img/image-1624432254118.png
new file mode 100644
index 0000000..c8bbe2b
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432254118.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432286674.png b/docs/en-us/modules/manager/img/image-1624432286674.png
new file mode 100644
index 0000000..338f2e3
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432286674.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432445002.png b/docs/en-us/modules/manager/img/image-1624432445002.png
new file mode 100644
index 0000000..e22b613
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432445002.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432458971.png b/docs/en-us/modules/manager/img/image-1624432458971.png
new file mode 100644
index 0000000..b7b7ec0
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432458971.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432474526.png b/docs/en-us/modules/manager/img/image-1624432474526.png
new file mode 100644
index 0000000..1893b8f
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432474526.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432496461.png b/docs/en-us/modules/manager/img/image-1624432496461.png
new file mode 100644
index 0000000..70e6404
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432496461.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432515850.png b/docs/en-us/modules/manager/img/image-1624432515850.png
new file mode 100644
index 0000000..e36a3c0
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432515850.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432535541.png b/docs/en-us/modules/manager/img/image-1624432535541.png
new file mode 100644
index 0000000..7fa323f
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432535541.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432652141.png b/docs/en-us/modules/manager/img/image-1624432652141.png
new file mode 100644
index 0000000..471a9b5
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432652141.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432668340.png b/docs/en-us/modules/manager/img/image-1624432668340.png
new file mode 100644
index 0000000..b86aae9
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432668340.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432740241.png b/docs/en-us/modules/manager/img/image-1624432740241.png
new file mode 100644
index 0000000..e6d2ab9
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432740241.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432759224.png b/docs/en-us/modules/manager/img/image-1624432759224.png
new file mode 100644
index 0000000..4c42d3e
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432759224.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432778845.png b/docs/en-us/modules/manager/img/image-1624432778845.png
new file mode 100644
index 0000000..435c7d9
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432778845.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432797226.png b/docs/en-us/modules/manager/img/image-1624432797226.png
new file mode 100644
index 0000000..f2309d4
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432797226.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624432829313.png b/docs/en-us/modules/manager/img/image-1624432829313.png
new file mode 100644
index 0000000..a502c0c
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624432829313.png differ
diff --git a/docs/en-us/modules/manager/img/image-1624433272455.png b/docs/en-us/modules/manager/img/image-1624433272455.png
new file mode 100644
index 0000000..4ae71bc
Binary files /dev/null and b/docs/en-us/modules/manager/img/image-1624433272455.png differ
diff --git a/docs/en-us/modules/manager/user_manual.md b/docs/en-us/modules/manager/user_manual.md
new file mode 100644
index 0000000..40c8384
--- /dev/null
+++ b/docs/en-us/modules/manager/user_manual.md
@@ -0,0 +1,282 @@
+# 1. User login
+
+Requires the user to enter the account name and password of the system.
+
+
+
+# 2. Data access
+
+The data access module displays a list of all tasks connected to the system within the current user authority, and can
+view, edit, update and delete the details of these tasks.
+
+Click [Data Access], there are two steps to fill in data access information: business information, data stream.
+
+
+
+## 2.1 Business Information
+
+### 2.1.1 Business Information
+
+You are required to fill in basic business information for access tasks.
+
+
+
+- Business English ID: Unified lowercase English name, please try to include the product name and concise
+ specifications, such as pay_base
+- Business Chinese name: Chinese description of the business, easy to use and retrieve, up to 128 characters
+- Business responsible person: at least 2 people, the business responsible person can view and modify business
+ information, add and modify all access configuration items
+- Business introduction: Cut SMS to introduce the business background and application of this access task:
+
+### 2.1.2 Access requirements
+
+Access requirements require users to choose message middleware: high throughput (TUBE):
+
+
+
+High-throughput-Tube: high-throughput message transmission component, suitable for log message transmission.
+
+### 2.1.3 Access scale
+
+The scale of access requires users to judge the scale of access data in advance, to allocate computing and storage
+resources later.
+
+
+
+## 2.2 Data stream
+
+Click [Next] to enter the data flow information filling step. There are four modules for data flow information filling:
+basic information, data source, data information, and data stream.
+
+In the data flow process, you can click [New Data Stream] to create a new data stream page:
+
+
+
+### 2.2.1 Basic information
+
+You are required to fill in the basic information of the data stream in the access task:
+
+
+
+- Data stream ID: The prefix is automatically generated according to the product/project, the unique identifier of the
+ data in the business, the unique identifier defined by a certain business, the data stream ID in the data source, and
+ the entry in the Hive information table The data stream ID is the same
+- Data stream name: interface information description, the length is limited to varchar (64), 32 Chinese
+- Data stream owner: The data stream owner can view and modify data stream information, add and modify all access
+ configuration items
+- Introduction to data flow: simple text introduction to data flow
+
+### 2.2.2 Data source
+
+You are required to select the source of the data stream.
+
+Currently, three methods of file and independent push are supported, and the detailed information of the data source can
+be supplemented in the advanced options.
+
+- File: The business data is in the file, and the business machine deploys InLong Agent, which is read according to
+ customized policy rules
+- Autonomous push: Push data to the messaging middleware through the SDK
+
+
+
+### 2.2.3 Data Information
+
+You are required to fill in the data-related information in the data stream.
+
+
+
+- Data Format
+- Data encoding: If the data source contains Chinese, you need choose UTF-8 or GBK, otherwise the encoding format is
+ incorrect and garbled characters after storage
+- Source field separator: the format of data sent to MQ
+- Source data field: attributes with different meanings divided by a certain format in MQ
+
+### 2.2.4 Data storage
+
+You are required to select the final flow direction of this task, this part is not currently supports both hive storage
+and autonomous push.
+
+
+
+Add HIVE storage:
+
+
+
+- Target database: hive database name (prepared to create in advance)
+- Target table: hive table name
+- First-level partition: the field name of the first-level subdirectory of hdfs data divided by hive data
+- Secondary partition: the field name of the first-level subdirectory of hdfs data divided by hive data
+- Username: hive server connection account name
+- User password: hive server connection account password
+- HDFS url: Hive bottom HDFS connection
+- JDBC url: jdbc url of hive server
+- Field related information: source field name, source field type, HIVE field name, HIVE field type, field description,
+ and support deletion and addition-
+
+# 3. Access details
+
+## 3.1 Execution log
+
+When the status of the data access task is "approved successfully" or "configuration failed", the "execution log"
+function can be used to allow users to view the progress and details of the task.
+
+
+
+Click [Execution Log] to display the details of the task execution log in a pop-up window.
+
+
+
+The execution log will display the task type, execution result, execution log content, end time, and the end time of the
+execution of the access process. If the execution fails, you can "restart" the task and execute it again.
+
+## 3.2 Task details
+
+The business person in charge/following person can view the access details of the task, and can modify and update part
+of the information under the status of [Waiting Applying], [Configuration Successful], and [Configuration Failed].
+
+There are three modules in the access task details: business information, data stream and data storage.
+
+### 3.2.1 Business Information
+
+Display the basic business information in the access task, click [Edit] to modify part of the content
+
+
+
+### 3.2.2 Data stream
+
+Display the basic information of the data flow under the access task, click [New Data Flow] to create a new data flow
+information
+
+
+
+### 3.2.3 Data Storage
+
+Display the basic information of the data flow in the access task, select different flow types through the drop-down
+box, and click [New Flow Configuration] to create a new data storage.
+
+
+
+# 4. Data consumption
+
+Data consumption currently does not support direct consumption access to data, and data can be consumed normally after
+the approval process.
+
+Click [New Consumption] to enter the data consumption process, and you need to fill in information related to
+consumption.
+
+
+
+## 4.1 Consumer Information
+
+Applicants need to gradually fill in the basic consumer business information related to data consumption applications in
+the information filling module
+
+
+
+- Consumer group name: The prefix is automatically generated according to the product/project. The brief name of the
+ consumer must be composed of lowercase letters, numbers, and underscores. The final approval will assign the consumer
+ name based on the abbreviation splicing
+- Consumer Responsible Person: At least 2 persons are required to choose the responsible person; the responsible person
+ can view and modify the consumption information
+- Consumer target business ID: you need to select the business ID of the consumer data, you can click [Query] and select
+ the appropriate business ID in the pop-up window
+ 
+- Data usage: select data usage usage
+- Data usage description: The applicant needs to briefly explain the items used and the purpose of the data according to
+ their own consumption scenarios After completing the information, click [Submit], and the data consumption process
+ will be formally submitted to the approver before it will take effect.
+
+# 5. Approval management
+
+The approval management function module currently includes my application and my approval, and all tasks of data access
+and consumption application approval in the management system.
+
+## 5.1 My application
+
+Display the current task list submitted by the applicant for data access and consumption in the system, click [Details]
+to view the current basic information and approval process of the task.
+
+
+
+### 5.1.1 Data access details
+
+Data access task detailed display The current basic information of the application task includes: applicant-related
+information, basic information about application access, and current approval process nodes.
+
+
+
+### 5.1.2 Data consumption details
+
+Data consumption task details display basic information of current application tasks including: applicant information,
+basic consumption information, and current approval process nodes.
+
+
+
+## 5.2 My approval
+
+As a data access officer and system member with approval authority, have the responsibility for data access or
+consumption approval.
+
+
+
+### 5.2.1 Data Access Approval
+
+New data access approval: currently it is a first-level approval, which is approved by the system administrator.
+
+The system administrator will review whether the access process meets the access requirements based on the data access
+business information.
+
+
+
+### 5.2.2 New data consumption approval
+
+New data consume approval: currently it is a first-level approval, which is approved by the person in charge of the
+business.
+
+Business approval: The person in charge of the data access business judges whether the consumption meets the business
+requirements according to the access information:
+
+
+
+# 6. System Management
+
+Only users with the role of system administrator can use this function. They can create, modify, and delete users:
+
+
+
+## 6.1 New user
+
+Users with system administrator rights can create new user accounts
+
+
+
+- Account types: Ordinary users (with data access and data consumption permissions, but without data access approval and
+ account management permissions); system administrators (with data access and data consumption permissions, data access
+ approval and account management permissions)
+- username: username for login
+- user password:
+ -Effective duration: the account can be used in the system
+ 
+
+## 6.2 Delete user
+
+The system administrator can delete the account of the created user. After the deletion, the account will stop using:
+
+
+
+## 6.3 User Edit
+
+The system administrator can modify the created account:
+
+
+
+The system administrator can modify the account type and effective duration to proceed:
+
+
+
+## 6.4 Change password
+
+The user can modify the account password, click [Modify Password], enter the old password and the new password, after
+confirmation, the new password of this account will take effect:
+
+
diff --git a/docs/zh-cn/modules/manager/user_manual.md b/docs/zh-cn/modules/manager/user_manual.md
index e2023ad..4e0bb87 100644
--- a/docs/zh-cn/modules/manager/user_manual.md
+++ b/docs/zh-cn/modules/manager/user_manual.md
@@ -1,65 +1,93 @@
-## 1.用户登录
-需系统使用用户输入账号名称和密码
+# 1. 用户登录
+
+需系统使用用户输入账号名称和密码。
-## 2.数据接入
-数据接入模块展示目前用户权限内接入系统所有任务列表，可以对这些任务详情查看、编辑更新和删除操作
-点击【数据接入】接入流程，数据接入信息填写有两个步骤：业务信息、数据流
+# 2. 数据接入
+
+数据接入模块展示目前用户权限内接入系统所有任务列表，可以对这些任务详情查看、编辑更新和删除操作。
+
+点击【数据接入】接入流程，数据接入信息填写有两个步骤：业务信息、数据流。
+
-### 2.1 业务信息
-#### 2.1.1 业务信息
-需要用户对接入任务填写基础业务信息
+## 2.1 业务信息
+
+### 2.1.1 业务信息
+
+需要用户对接入任务填写基础业务信息。
+
-- 业务ID：统一小写英文名称，请尽量包含产品名和简洁规范，如wechat_pay_base
+
+- 业务ID：统一小写英文名称，请尽量包含产品名和简洁规范，如pay_base
- 业务中文名称：业务的中文描述，便于使用与检索，最多128个字
- 业务责任人：至少2人，业务责任人可查看、修改业务信息，新增和修改所有接入配置项
- 业务介绍：剪短信对此次接入任务进行业务背景和应用介绍：
-#### 2.1.2 接入要求
-接入要求需要用户进行选择消息中间件： 高吞吐（TUBE）
+### 2.1.2 接入要求
+
+接入要求需要用户进行选择消息中间件：高吞吐（TUBE）：
+
-高吞吐—Tube ：高吞吐消息传输组件，适用于日志类的消息传递
-#### 2.1.3 接入规模
-接入规模需要用户预先针对接入数据进行规模判断，以便后续分配计算和存储资源
+高吞吐—Tube ：高吞吐消息传输组件，适用于日志类的消息传递。
+
+### 2.1.3 接入规模
+
+接入规模需要用户预先针对接入数据进行规模判断，以便后续分配计算和存储资源。
+
-### 2.2 数据流
-点击【下一步】进入到数据流信息填写步骤，数据流信息填写有四个模块：基础信息、数据来源、数据信息、数据流向
-在数据流流程中可以点击【新建数据流】，创建一个新的数据流信息填写页面
+## 2.2 数据流
+
+点击【下一步】进入到数据流信息填写步骤，数据流信息填写有四个模块：基础信息、数据来源、数据信息、数据流向。
+
+在数据流流程中可以点击【新建数据流】，创建一个新的数据流信息填写页面：
+
-#### 2.2.1 基础信息
-需用户对该接入任务中数据流的基础信息进行填写
+### 2.2.1 基础信息
+
+需用户对该接入任务中数据流的基础信息进行填写：
+
-- 数据流ID：前缀根据BG/产品/项目自动生成，数据在业务中的唯一标识，TDBank中某个业务数据定义的唯一标识，跟数据源中的数据流ID、入TDW库信息表中的数据流ID一致
+
+- 数据流ID：前缀根据BG/产品/项目自动生成，数据在业务中的唯一标识，InLong中某个业务数据定义的唯一标识，跟数据源中的数据流ID、入库信息表中的数据流ID一致
- 数据流名称：接口信息说明,长度限制为varchar(64)，32个中文
- 数据流责任人：数据流责任人可查看、修改数据流信息，新增和修改所有接入配置项
- 数据流介绍：数据流简单文本介绍
-#### 2.2.2 数据来源
-需用户选择该数据流的消息来源，目前支持文件、自主推送三种方式，并且可以在高级选项中补充该数据来源详细信息；
-- 文件：业务数据以文件形式存放，业务机器部署TDBank Agent,根据定制的策略规则进行读取，详细说明链接
-- 自主推送：文案待定，技术实现与109消息中间件类型有关联
-
+### 2.2.2 数据来源
+
+需用户选择该数据流的消息来源，目前支持文件、自主推送三种方式，并且可以在高级选项中补充该数据来源详细信息：
+- 文件：业务数据以文件形式存放，业务机器部署 InLong Agent，根据定制的策略规则进行读取
+- 自主推送：通过 SDK 向消息中间件推送数据
+
+ 
+
+### 2.2.3 数据信息
+
+需用户填写该数据流中数据相关信息：
-#### 2.2.3 数据信息
-需用户填写该数据流中数据相关信息
+
- 数据格式：数据来源格式，是普通文本类型，或者KV键值对数据
-- 数据编码：如数据源含中文，需要选UTF-8或GBK,否则编码格式不对，入库为乱码
-- 源字段分隔符：数据发送到mq里面的格式
-- 源数据字段：数据在mq里按某种格式划分的不同含义的属性
+- 数据编码：如数据源含中文，需要选UTF-8或GBK，否则编码格式不对，入库后会乱码
+- 源字段分隔符：数据发送到 MQ 里的格式
+- 源数据字段：数据在 MQ 里按某种格式划分的不同含义的属性
+
+### 2.2.4 数据流向
+
+需用户对此任务的流向终流向进行选择，此部分为非必填项，目前支持Hive和自主推送两种：
-#### 2.2.4 数据流向
-需用户对此任务的流向终流向进行选择，此部分为非必填项
-目前支持hive流向和自主推送两种
-HIVE流向
+
+HIVE流向：
+
+
- 目标库：hive数据库名（需要提前准备创建好）
- 目标表：hive表名
- 一级分区：hive数据划分hdfs数据一级子目录的字段名
@@ -70,95 +98,144 @@ HIVE流向
- JDBC url：hiveserver 的jdbcurl
- 字段相关信息： 源字段名、源字段类型、HIVE字段名、HIVE字段类型、字段描述，并支持删除和新增字段
-## 3.接入详情
-### 3.1 执行日志
-当数据接入任务状态为”批准成功“和”配置失败“状态，可通过”执行日志“功能，以便用户查看任务执行进程进程和详情
+# 3. 接入详情
+
+## 3.1 执行日志
+
+当数据接入任务状态为”批准成功“和”配置失败“状态，可通过”执行日志“功能，以便用户查看任务执行进程进程和详情：
+
-点击【执行日志】将以弹窗形式展示该任务执行日志详情
+点击【执行日志】将以弹窗形式展示该任务执行日志详情：
+
-执行日志中将展示该接入流程执行中任务类型、执行结果、执行日志内容、结束时间、如果执行失败可以”重启“该任务再次执行
-### 3.2 任务详情
-业务负责人/关注人可以查看该任务接入详情，并在【待提交】、【配置成功】、【配置失败】状态下可对部分信息进行修改更新
-接入任务详情中具有业务信息、数据流、流向、三个模块
+执行日志中将展示该接入流程执行中任务类型、执行结果、执行日志内容、结束时间、如果执行失败可以”重启“该任务再次执行。
+
+## 3.2 任务详情
+
+业务负责人/关注人可以查看该任务接入详情，并在【待提交】、【配置成功】、【配置失败】状态下可对部分信息进行修改更新接入任务详情中具有业务信息、数据流、流向三个模块。
+
+### 3.2.1 业务信息
+
+展示接入任务中基础业务信息，点击【编辑】可对部分内容进行修改更改：
-#### 3.2.1 业务信息
-展示接入任务中基础业务信息，点击【编辑】可对部分内容进行修改更改
-#### 3.2.2 数据流
-展示该接入任务下数据流基础信息，点击【新建数据流】可新建一条数据流信息
+### 3.2.2 数据流
+
+展示该接入任务下数据流基础信息，点击【新建数据流】可新建一条数据流信息：
+
-#### 3.2.3 流向
-展示该接入任务中数据流向基础信息，通过通过下拉框选择不同流向类型，点击【新建流向配置】可新建一条数据流向信息
+### 3.2.3 流向
+
+展示该接入任务中数据流向基础信息，通过通过下拉框选择不同流向类型，点击【新建流向配置】可新建一条数据流向：
+
-## 4 数据消费
-数据消费目前不支持直接消费接入数据，需走数据审批流程后方可正常消费数据；
-点击【新建消费】，进入数据消费流程，需要对消费信息相关信息进行填写；
+# 4. 数据消费
+
+数据消费目前不支持直接消费接入数据，需走数据审批流程后方可正常消费数据； 点击【新建消费】，进入数据消费流程，需要对消费信息相关信息进行填写：
-### 4.1 消费信息
-申请人需在该信息填写模块中逐步填写数据消费申请相关基础消费业务信息
+## 4.1 消费信息
+
+申请人需在该信息填写模块中逐步填写数据消费申请相关基础消费业务信息：
+
+
- 消费组名称：前缀根据BG/产品/项目自动生成，消费者的简要名称，必须是小写字母、数字、下划线组成，最后审批会根据简称拼接分配出消费者名称
- 消费责任人：自行选择责任人，必须至少2人；责任人可查看、修改消费信息
- 消费目标业务ID：需要选择消费数据的业务ID，可以点击【查询】后，在弹窗页面中选择合适的业务ID，如下图所示：
- 数据用途：选择数据使用用途
- 数据用途说明：需申请人根据自身消费场景，简要说明使用的项目和数据的用途
-信息填完完成后，点击【提交】后，会将次数据消费流程正式提交待审批人审批后方可生效
+
+信息填完完成后，点击【提交】后，会将次数据消费流程正式提交待审批人审批后方可生效。
-## 5.审批管理
-审批管理功能模块目前包含了我的申请和我的审批，管理系统中数据接入和数据消费申请审批全部任务
-### 5.1 我的申请
-展示目前申请人在系统中数据接入、消费提交的任务列表，点击【详情】可以查看目前该任务基础信和审批进程
+# 5. 审批管理
+
+审批管理功能模块目前包含了我的申请和我的审批，管理系统中数据接入和数据消费申请审批全部任务。
+
+## 5.1 我的申请
+
+展示目前申请人在系统中数据接入、消费提交的任务列表，点击【详情】可以查看目前该任务基础信和审批进程：
+
-#### 5.1.1 数据接入详情
-数据接入任务详细展示目前该申请任务基础信息包括：申请人相关信息、申请接入基础信息、资源预估信息、以及目前审批进程节点
+### 5.1.1 数据接入详情
+
+数据接入任务详细展示目前该申请任务基础信息包括：申请人相关信息、申请接入基础信息，以及目前审批进程节点：
+
-#### 5.1.2 数据消费详情
-数据消费任务详情展示目前申请任务基础信息包括：申请人信息、基础消费信息、资源预估、以及目前审批进程节点
+
+### 5.1.2 数据消费详情
+
+数据消费任务详情展示目前申请任务基础信息包括：申请人信息、基础消费信息，以及目前审批进程节点：
+
-### 5.2 我的审批
-作为具有审批权限的数据接入员和系统成员，具备对数据接入或者消费审批职责
+
+## 5.2 我的审批
+
+作为具有审批权限的数据接入员和系统成员，具备对数据接入或者消费审批职责：
+
-#### 5.2.1 数据接入审批
-新建数据接入审批：目前为一级审批，由系统管理员审批
-系统管理员将根据数据接入业务信息审核此次接入流程是否符合接入要求
+
+### 5.2.1 数据接入审批
+
+新建数据接入审批：目前为一级审批，由系统管理员审批。
+
+系统管理员将根据数据接入业务信息，审核此次接入流程是否符合接入要求：
+
-#### 5.2.2 新建数据消费审批
-新建数据消费审批：目前为一级审批，由业务负责人审批
-业务审批：主要由数据接入业务负责人根据接入参数信息判断是否符合接入要求，以此依据审批该申请消费任务
+
+### 5.2.2 新建数据消费审批
+
+新建数据消费审批：目前为一级审批，由业务负责人审批。
+
+业务审批：由数据接入业务负责人根据接入信息判断此消费是否符合业务要求：
+
-## 6 系统管理
-系统管理目前针对于具有系统管理员身份用户，可以进行账号创建、修改、删除操作
+# 6. 系统管理
+
+角色为系统管理员的用户才可以使用此功能，他们可以创建、修改、删除用户：
+
-### 6.1 新建用户
-具有系统管理员权限用户，可以进行创建新用户账号
+
+## 6.1 新建用户
+
+具有系统管理员权限用户，可以进行创建新用户账号：
+
-- 账号类型： 普通用户（具有数据接入和数据消费权限，不具有数据接入审批和账号管理权限）； 系统管理员（具有数据接入和数据消费权限、同时也需要对数据接入审批和账号管理权限）
+
+- 账号类型： 普通用户（具有数据接入和数据消费权限，不具有数据接入审批和账号管理权限）；系统管理员（具有数据接入和数据消费权限、数据接入审批和管理账号的权限）
- 用户名称：用户登录账号ID
- 用户密码：用户登录密码
- 有效时长：该账号可在系统使用期限
-### 6.2 删除用户
-系统管理员可以对已创建的用户进行账户删除，删除后次账号将停止使用
+## 6.2 删除用户
+
+系统管理员可以对已创建的用户进行账户删除，删除后此账号将停止使用：
+
-### 6.3 用户编辑
-系统管理员可以对以已创建账号，进行二次编辑
+## 6.3 修改用户
+
+系统管理员可以修改已创建的账号：
+
-目前对于系统管理员支持对已有账号中：账号类型和有效时长进行修改
+
+系统管理员可以修改账号类型和有效时长进行：
+
-### 6.4 更改密码
-用户可以自行更改账号密码，点击【修改密码】，用户需要输入旧密码和新密码，确认后次账号新密码将生效
+## 6.4 更改密码
+
+用户可以修改账号密码，点击【修改密码】，输入旧密码和新密码，确认后此账号新密码将生效：
+
diff --git a/en-us/docs/modules/manager/img/image-1624431177918.png b/en-us/docs/modules/manager/img/image-1624431177918.png
new file mode 100644
index 0000000..2014e8c
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624431177918.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624431271642.png b/en-us/docs/modules/manager/img/image-1624431271642.png
new file mode 100644
index 0000000..9dac2ec
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624431271642.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624431306077.png b/en-us/docs/modules/manager/img/image-1624431306077.png
new file mode 100644
index 0000000..c70ee18
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624431306077.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624431333949.png b/en-us/docs/modules/manager/img/image-1624431333949.png
new file mode 100644
index 0000000..0569bc6
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624431333949.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624431416449.png b/en-us/docs/modules/manager/img/image-1624431416449.png
new file mode 100644
index 0000000..9d53a39
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624431416449.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624431435574.png b/en-us/docs/modules/manager/img/image-1624431435574.png
new file mode 100644
index 0000000..724e535
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624431435574.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624431594406.png b/en-us/docs/modules/manager/img/image-1624431594406.png
new file mode 100644
index 0000000..c133174
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624431594406.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624431617259.png b/en-us/docs/modules/manager/img/image-1624431617259.png
new file mode 100644
index 0000000..eaa10b1
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624431617259.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624431713360.png b/en-us/docs/modules/manager/img/image-1624431713360.png
new file mode 100644
index 0000000..fb8658e
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624431713360.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624431787323.png b/en-us/docs/modules/manager/img/image-1624431787323.png
new file mode 100644
index 0000000..23621be
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624431787323.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432002615.png b/en-us/docs/modules/manager/img/image-1624432002615.png
new file mode 100644
index 0000000..b3d4a1e
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432002615.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432022859.png b/en-us/docs/modules/manager/img/image-1624432022859.png
new file mode 100644
index 0000000..25eede7
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432022859.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432076857.png b/en-us/docs/modules/manager/img/image-1624432076857.png
new file mode 100644
index 0000000..3215186
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432076857.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432092795.png b/en-us/docs/modules/manager/img/image-1624432092795.png
new file mode 100644
index 0000000..9a00a88
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432092795.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432114765.png b/en-us/docs/modules/manager/img/image-1624432114765.png
new file mode 100644
index 0000000..380506e
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432114765.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432235900.png b/en-us/docs/modules/manager/img/image-1624432235900.png
new file mode 100644
index 0000000..78fc1e5
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432235900.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432254118.png b/en-us/docs/modules/manager/img/image-1624432254118.png
new file mode 100644
index 0000000..c8bbe2b
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432254118.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432286674.png b/en-us/docs/modules/manager/img/image-1624432286674.png
new file mode 100644
index 0000000..338f2e3
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432286674.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432445002.png b/en-us/docs/modules/manager/img/image-1624432445002.png
new file mode 100644
index 0000000..e22b613
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432445002.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432458971.png b/en-us/docs/modules/manager/img/image-1624432458971.png
new file mode 100644
index 0000000..b7b7ec0
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432458971.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432474526.png b/en-us/docs/modules/manager/img/image-1624432474526.png
new file mode 100644
index 0000000..1893b8f
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432474526.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432496461.png b/en-us/docs/modules/manager/img/image-1624432496461.png
new file mode 100644
index 0000000..70e6404
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432496461.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432515850.png b/en-us/docs/modules/manager/img/image-1624432515850.png
new file mode 100644
index 0000000..e36a3c0
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432515850.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432535541.png b/en-us/docs/modules/manager/img/image-1624432535541.png
new file mode 100644
index 0000000..7fa323f
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432535541.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432652141.png b/en-us/docs/modules/manager/img/image-1624432652141.png
new file mode 100644
index 0000000..471a9b5
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432652141.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432668340.png b/en-us/docs/modules/manager/img/image-1624432668340.png
new file mode 100644
index 0000000..b86aae9
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432668340.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432740241.png b/en-us/docs/modules/manager/img/image-1624432740241.png
new file mode 100644
index 0000000..e6d2ab9
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432740241.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432759224.png b/en-us/docs/modules/manager/img/image-1624432759224.png
new file mode 100644
index 0000000..4c42d3e
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432759224.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432778845.png b/en-us/docs/modules/manager/img/image-1624432778845.png
new file mode 100644
index 0000000..435c7d9
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432778845.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432797226.png b/en-us/docs/modules/manager/img/image-1624432797226.png
new file mode 100644
index 0000000..f2309d4
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432797226.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624432829313.png b/en-us/docs/modules/manager/img/image-1624432829313.png
new file mode 100644
index 0000000..a502c0c
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624432829313.png differ
diff --git a/en-us/docs/modules/manager/img/image-1624433272455.png b/en-us/docs/modules/manager/img/image-1624433272455.png
new file mode 100644
index 0000000..4ae71bc
Binary files /dev/null and b/en-us/docs/modules/manager/img/image-1624433272455.png differ
diff --git a/en-us/docs/modules/manager/user_manual.html b/en-us/docs/modules/manager/user_manual.html
new file mode 100644
index 0000000..7527066
--- /dev/null
+++ b/en-us/docs/modules/manager/user_manual.html
@@ -0,0 +1,212 @@
+<!DOCTYPE html>
+<html lang="en">
+
+<head>
+ <meta charset="UTF-8">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
+ <meta name="keywords" content="user_manual" />
+ <meta name="description" content="user_manual" />
+ <!-- 网页标签标题 -->
+ <title>user_manual</title>
+ <link rel="shortcut icon" href="/img/apache.ico"/>
+ <link rel="stylesheet" href="/build/documentation.css" />
+</head>
+<body>
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><img class="logo tube" style="width:120px;top:12px;position:absolute" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class= [...]
+<p>Requires the user to enter the account name and password of the system.</p>
+<p><img src="img/image-1624433272455.png" alt=""></p>
+<h1>2. Data access</h1>
+<p>The data access module displays a list of all tasks connected to the system within the current user authority, and can
+view, edit, update and delete the details of these tasks.</p>
+<p>Click [Data Access], there are two steps to fill in data access information: business information, data stream.</p>
+<p><img src="img/image-1624431177918.png" alt=""></p>
+<h2>2.1 Business Information</h2>
+<h3>2.1.1 Business Information</h3>
+<p>You are required to fill in basic business information for access tasks.</p>
+<p><img src="img/image-1624431271642.png" alt=""></p>
+<ul>
+<li>Business English ID: Unified lowercase English name, please try to include the product name and concise
+specifications, such as pay_base</li>
+<li>Business Chinese name: Chinese description of the business, easy to use and retrieve, up to 128 characters</li>
+<li>Business responsible person: at least 2 people, the business responsible person can view and modify business
+information, add and modify all access configuration items</li>
+<li>Business introduction: Cut SMS to introduce the business background and application of this access task:</li>
+</ul>
+<h3>2.1.2 Access requirements</h3>
+<p>Access requirements require users to choose message middleware: high throughput (TUBE):</p>
+<p><img src="img/image-1624431306077.png" alt=""></p>
+<p>High-throughput-Tube: high-throughput message transmission component, suitable for log message transmission.</p>
+<h3>2.1.3 Access scale</h3>
+<p>The scale of access requires users to judge the scale of access data in advance, to allocate computing and storage
+resources later.</p>
+<p><img src="img/image-1624431333949.png" alt=""></p>
+<h2>2.2 Data stream</h2>
+<p>Click [Next] to enter the data flow information filling step. There are four modules for data flow information filling:
+basic information, data source, data information, and data stream.</p>
+<p>In the data flow process, you can click [New Data Stream] to create a new data stream page:</p>
+<p><img src="img/image-1624431416449.png" alt=""></p>
+<h3>2.2.1 Basic information</h3>
+<p>You are required to fill in the basic information of the data stream in the access task:</p>
+<p><img src="img/image-1624431435574.png" alt=""></p>
+<ul>
+<li>Data stream ID: The prefix is automatically generated according to the product/project, the unique identifier of the
+data in the business, the unique identifier defined by a certain business, the data stream ID in the data source, and
+the entry in the Hive information table The data stream ID is the same</li>
+<li>Data stream name: interface information description, the length is limited to varchar (64), 32 Chinese</li>
+<li>Data stream owner: The data stream owner can view and modify data stream information, add and modify all access
+configuration items</li>
+<li>Introduction to data flow: simple text introduction to data flow</li>
+</ul>
+<h3>2.2.2 Data source</h3>
+<p>You are required to select the source of the data stream.</p>
+<p>Currently, three methods of file and independent push are supported, and the detailed information of the data source can
+be supplemented in the advanced options.</p>
+<ul>
+<li>File: The business data is in the file, and the business machine deploys InLong Agent, which is read according to
+customized policy rules</li>
+<li>Autonomous push: Push data to the messaging middleware through the SDK</li>
+</ul>
+<p><img src="img/image-1624431594406.png" alt=""></p>
+<h3>2.2.3 Data Information</h3>
+<p>You are required to fill in the data-related information in the data stream.</p>
+<p><img src="img/image-1624431617259.png" alt=""></p>
+<ul>
+<li>Data Format</li>
+<li>Data encoding: If the data source contains Chinese, you need choose UTF-8 or GBK, otherwise the encoding format is
+incorrect and garbled characters after storage</li>
+<li>Source field separator: the format of data sent to MQ</li>
+<li>Source data field: attributes with different meanings divided by a certain format in MQ</li>
+</ul>
+<h3>2.2.4 Data storage</h3>
+<p>You are required to select the final flow direction of this task, this part is not currently supports both hive storage
+and autonomous push.</p>
+<p><img src="img/image-1624431713360.png" alt=""></p>
+<p>Add HIVE storage:</p>
+<p><img src="img/image-1624431787323.png" alt=""></p>
+<ul>
+<li>Target database: hive database name (prepared to create in advance)</li>
+<li>Target table: hive table name</li>
+<li>First-level partition: the field name of the first-level subdirectory of hdfs data divided by hive data</li>
+<li>Secondary partition: the field name of the first-level subdirectory of hdfs data divided by hive data</li>
+<li>Username: hive server connection account name</li>
+<li>User password: hive server connection account password</li>
+<li>HDFS url: Hive bottom HDFS connection</li>
+<li>JDBC url: jdbc url of hive server</li>
+<li>Field related information: source field name, source field type, HIVE field name, HIVE field type, field description,
+and support deletion and addition-</li>
+</ul>
+<h1>3. Access details</h1>
+<h2>3.1 Execution log</h2>
+<p>When the status of the data access task is "approved successfully" or "configuration failed", the "execution log"
+function can be used to allow users to view the progress and details of the task.</p>
+<p><img src="img/image-1624432002615.png" alt=""></p>
+<p>Click [Execution Log] to display the details of the task execution log in a pop-up window.</p>
+<p><img src="img/image-1624432022859.png" alt=""></p>
+<p>The execution log will display the task type, execution result, execution log content, end time, and the end time of the
+execution of the access process. If the execution fails, you can "restart" the task and execute it again.</p>
+<h2>3.2 Task details</h2>
+<p>The business person in charge/following person can view the access details of the task, and can modify and update part
+of the information under the status of [Waiting Applying], [Configuration Successful], and [Configuration Failed].</p>
+<p>There are three modules in the access task details: business information, data stream and data storage.</p>
+<h3>3.2.1 Business Information</h3>
+<p>Display the basic business information in the access task, click [Edit] to modify part of the content</p>
+<p><img src="img/image-1624432076857.png" alt=""></p>
+<h3>3.2.2 Data stream</h3>
+<p>Display the basic information of the data flow under the access task, click [New Data Flow] to create a new data flow
+information</p>
+<p><img src="img/image-1624432092795.png" alt=""></p>
+<h3>3.2.3 Data Storage</h3>
+<p>Display the basic information of the data flow in the access task, select different flow types through the drop-down
+box, and click [New Flow Configuration] to create a new data storage.</p>
+<p><img src="img/image-1624432114765.png" alt=""></p>
+<h1>4. Data consumption</h1>
+<p>Data consumption currently does not support direct consumption access to data, and data can be consumed normally after
+the approval process.</p>
+<p>Click [New Consumption] to enter the data consumption process, and you need to fill in information related to
+consumption.</p>
+<p><img src="img/image-1624432235900.png" alt=""></p>
+<h2>4.1 Consumer Information</h2>
+<p>Applicants need to gradually fill in the basic consumer business information related to data consumption applications in
+the information filling module</p>
+<p><img src="img/image-1624432254118.png" alt=""></p>
+<ul>
+<li>Consumer group name: The prefix is automatically generated according to the product/project. The brief name of the
+consumer must be composed of lowercase letters, numbers, and underscores. The final approval will assign the consumer
+name based on the abbreviation splicing</li>
+<li>Consumer Responsible Person: At least 2 persons are required to choose the responsible person; the responsible person
+can view and modify the consumption information</li>
+<li>Consumer target business ID: you need to select the business ID of the consumer data, you can click [Query] and select
+the appropriate business ID in the pop-up window
+<img src="img/image-1624432286674.png" alt=""></li>
+<li>Data usage: select data usage usage</li>
+<li>Data usage description: The applicant needs to briefly explain the items used and the purpose of the data according to
+their own consumption scenarios After completing the information, click [Submit], and the data consumption process
+will be formally submitted to the approver before it will take effect.</li>
+</ul>
+<h1>5. Approval management</h1>
+<p>The approval management function module currently includes my application and my approval, and all tasks of data access
+and consumption application approval in the management system.</p>
+<h2>5.1 My application</h2>
+<p>Display the current task list submitted by the applicant for data access and consumption in the system, click [Details]
+to view the current basic information and approval process of the task.</p>
+<p><img src="img/image-1624432445002.png" alt=""></p>
+<h3>5.1.1 Data access details</h3>
+<p>Data access task detailed display The current basic information of the application task includes: applicant-related
+information, basic information about application access, and current approval process nodes.</p>
+<p><img src="img/image-1624432458971.png" alt=""></p>
+<h3>5.1.2 Data consumption details</h3>
+<p>Data consumption task details display basic information of current application tasks including: applicant information,
+basic consumption information, and current approval process nodes.</p>
+<p><img src="img/image-1624432474526.png" alt=""></p>
+<h2>5.2 My approval</h2>
+<p>As a data access officer and system member with approval authority, have the responsibility for data access or
+consumption approval.</p>
+<p><img src="img/image-1624432496461.png" alt=""></p>
+<h3>5.2.1 Data Access Approval</h3>
+<p>New data access approval: currently it is a first-level approval, which is approved by the system administrator.</p>
+<p>The system administrator will review whether the access process meets the access requirements based on the data access
+business information.</p>
+<p><img src="img/image-1624432515850.png" alt=""></p>
+<h3>5.2.2 New data consumption approval</h3>
+<p>New data consume approval: currently it is a first-level approval, which is approved by the person in charge of the
+business.</p>
+<p>Business approval: The person in charge of the data access business judges whether the consumption meets the business
+requirements according to the access information:</p>
+<p><img src="img/image-1624432535541.png" alt=""></p>
+<h1>6. System Management</h1>
+<p>Only users with the role of system administrator can use this function. They can create, modify, and delete users:</p>
+<p><img src="img/image-1624432652141.png" alt=""></p>
+<h2>6.1 New user</h2>
+<p>Users with system administrator rights can create new user accounts</p>
+<p><img src="img/image-1624432668340.png" alt=""></p>
+<ul>
+<li>Account types: Ordinary users (with data access and data consumption permissions, but without data access approval and
+account management permissions); system administrators (with data access and data consumption permissions, data access
+approval and account management permissions)</li>
+<li>username: username for login</li>
+<li>user password:
+-Effective duration: the account can be used in the system
+<img src="img/image-1624432740241.png" alt=""></li>
+</ul>
+<h2>6.2 Delete user</h2>
+<p>The system administrator can delete the account of the created user. After the deletion, the account will stop using:</p>
+<p><img src="img/image-1624432759224.png" alt=""></p>
+<h2>6.3 User Edit</h2>
+<p>The system administrator can modify the created account:</p>
+<p><img src="img/image-1624432778845.png" alt=""></p>
+<p>The system administrator can modify the account type and effective duration to proceed:</p>
+<p><img src="img/image-1624432797226.png" alt=""></p>
+<h2>6.4 Change password</h2>
+<p>The user can modify the account password, click [Modify Password], enter the old password and the new password, after
+confirmation, the new password of this account will take effect:</p>
+<p><img src="img/image-1624432829313.png" alt=""></p>
+</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/incubator-logo.svg"/><div class="cols-container"><div class="col col-24"><p>Apache InLong (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with [...]
+ <script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
+ <script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
+ <script src="https://buttons.github.io/buttons.js"></script>
+ <script>
+ window.rootPath = '';
+ </script>
+ <script src="/build/documentation.js"></script>
+</body>
+</html>
diff --git a/en-us/docs/modules/manager/user_manual.json b/en-us/docs/modules/manager/user_manual.json
new file mode 100644
index 0000000..3ea7f4f
--- /dev/null
+++ b/en-us/docs/modules/manager/user_manual.json
@@ -0,0 +1,6 @@
+{
+ "filename": "user_manual.md",
+ "__html": "<h1>1. User login</h1>\n<p>Requires the user to enter the account name and password of the system.</p>\n<p><img src=\"img/image-1624433272455.png\" alt=\"\"></p>\n<h1>2. Data access</h1>\n<p>The data access module displays a list of all tasks connected to the system within the current user authority, and can\nview, edit, update and delete the details of these tasks.</p>\n<p>Click [Data Access], there are two steps to fill in data access information: business information, dat [...]
+ "link": "/en-us/docs/modules/manager/user_manual.html",
+ "meta": {}
+}
\ No newline at end of file
diff --git a/en-us/docs/modules/manager/user_manual.md b/en-us/docs/modules/manager/user_manual.md
new file mode 100644
index 0000000..40c8384
--- /dev/null
+++ b/en-us/docs/modules/manager/user_manual.md
@@ -0,0 +1,282 @@
+# 1. User login
+
+Requires the user to enter the account name and password of the system.
+
+
+
+# 2. Data access
+
+The data access module displays a list of all tasks connected to the system within the current user authority, and can
+view, edit, update and delete the details of these tasks.
+
+Click [Data Access], there are two steps to fill in data access information: business information, data stream.
+
+
+
+## 2.1 Business Information
+
+### 2.1.1 Business Information
+
+You are required to fill in basic business information for access tasks.
+
+
+
+- Business English ID: Unified lowercase English name, please try to include the product name and concise
+ specifications, such as pay_base
+- Business Chinese name: Chinese description of the business, easy to use and retrieve, up to 128 characters
+- Business responsible person: at least 2 people, the business responsible person can view and modify business
+ information, add and modify all access configuration items
+- Business introduction: Cut SMS to introduce the business background and application of this access task:
+
+### 2.1.2 Access requirements
+
+Access requirements require users to choose message middleware: high throughput (TUBE):
+
+
+
+High-throughput-Tube: high-throughput message transmission component, suitable for log message transmission.
+
+### 2.1.3 Access scale
+
+The scale of access requires users to judge the scale of access data in advance, to allocate computing and storage
+resources later.
+
+
+
+## 2.2 Data stream
+
+Click [Next] to enter the data flow information filling step. There are four modules for data flow information filling:
+basic information, data source, data information, and data stream.
+
+In the data flow process, you can click [New Data Stream] to create a new data stream page:
+
+
+
+### 2.2.1 Basic information
+
+You are required to fill in the basic information of the data stream in the access task:
+
+
+
+- Data stream ID: The prefix is automatically generated according to the product/project, the unique identifier of the
+ data in the business, the unique identifier defined by a certain business, the data stream ID in the data source, and
+ the entry in the Hive information table The data stream ID is the same
+- Data stream name: interface information description, the length is limited to varchar (64), 32 Chinese
+- Data stream owner: The data stream owner can view and modify data stream information, add and modify all access
+ configuration items
+- Introduction to data flow: simple text introduction to data flow
+
+### 2.2.2 Data source
+
+You are required to select the source of the data stream.
+
+Currently, three methods of file and independent push are supported, and the detailed information of the data source can
+be supplemented in the advanced options.
+
+- File: The business data is in the file, and the business machine deploys InLong Agent, which is read according to
+ customized policy rules
+- Autonomous push: Push data to the messaging middleware through the SDK
+
+
+
+### 2.2.3 Data Information
+
+You are required to fill in the data-related information in the data stream.
+
+
+
+- Data Format
+- Data encoding: If the data source contains Chinese, you need choose UTF-8 or GBK, otherwise the encoding format is
+ incorrect and garbled characters after storage
+- Source field separator: the format of data sent to MQ
+- Source data field: attributes with different meanings divided by a certain format in MQ
+
+### 2.2.4 Data storage
+
+You are required to select the final flow direction of this task, this part is not currently supports both hive storage
+and autonomous push.
+
+
+
+Add HIVE storage:
+
+
+
+- Target database: hive database name (prepared to create in advance)
+- Target table: hive table name
+- First-level partition: the field name of the first-level subdirectory of hdfs data divided by hive data
+- Secondary partition: the field name of the first-level subdirectory of hdfs data divided by hive data
+- Username: hive server connection account name
+- User password: hive server connection account password
+- HDFS url: Hive bottom HDFS connection
+- JDBC url: jdbc url of hive server
+- Field related information: source field name, source field type, HIVE field name, HIVE field type, field description,
+ and support deletion and addition-
+
+# 3. Access details
+
+## 3.1 Execution log
+
+When the status of the data access task is "approved successfully" or "configuration failed", the "execution log"
+function can be used to allow users to view the progress and details of the task.
+
+
+
+Click [Execution Log] to display the details of the task execution log in a pop-up window.
+
+
+
+The execution log will display the task type, execution result, execution log content, end time, and the end time of the
+execution of the access process. If the execution fails, you can "restart" the task and execute it again.
+
+## 3.2 Task details
+
+The business person in charge/following person can view the access details of the task, and can modify and update part
+of the information under the status of [Waiting Applying], [Configuration Successful], and [Configuration Failed].
+
+There are three modules in the access task details: business information, data stream and data storage.
+
+### 3.2.1 Business Information
+
+Display the basic business information in the access task, click [Edit] to modify part of the content
+
+
+
+### 3.2.2 Data stream
+
+Display the basic information of the data flow under the access task, click [New Data Flow] to create a new data flow
+information
+
+
+
+### 3.2.3 Data Storage
+
+Display the basic information of the data flow in the access task, select different flow types through the drop-down
+box, and click [New Flow Configuration] to create a new data storage.
+
+
+
+# 4. Data consumption
+
+Data consumption currently does not support direct consumption access to data, and data can be consumed normally after
+the approval process.
+
+Click [New Consumption] to enter the data consumption process, and you need to fill in information related to
+consumption.
+
+
+
+## 4.1 Consumer Information
+
+Applicants need to gradually fill in the basic consumer business information related to data consumption applications in
+the information filling module
+
+
+
+- Consumer group name: The prefix is automatically generated according to the product/project. The brief name of the
+ consumer must be composed of lowercase letters, numbers, and underscores. The final approval will assign the consumer
+ name based on the abbreviation splicing
+- Consumer Responsible Person: At least 2 persons are required to choose the responsible person; the responsible person
+ can view and modify the consumption information
+- Consumer target business ID: you need to select the business ID of the consumer data, you can click [Query] and select
+ the appropriate business ID in the pop-up window
+ 
+- Data usage: select data usage usage
+- Data usage description: The applicant needs to briefly explain the items used and the purpose of the data according to
+ their own consumption scenarios After completing the information, click [Submit], and the data consumption process
+ will be formally submitted to the approver before it will take effect.
+
+# 5. Approval management
+
+The approval management function module currently includes my application and my approval, and all tasks of data access
+and consumption application approval in the management system.
+
+## 5.1 My application
+
+Display the current task list submitted by the applicant for data access and consumption in the system, click [Details]
+to view the current basic information and approval process of the task.
+
+
+
+### 5.1.1 Data access details
+
+Data access task detailed display The current basic information of the application task includes: applicant-related
+information, basic information about application access, and current approval process nodes.
+
+
+
+### 5.1.2 Data consumption details
+
+Data consumption task details display basic information of current application tasks including: applicant information,
+basic consumption information, and current approval process nodes.
+
+
+
+## 5.2 My approval
+
+As a data access officer and system member with approval authority, have the responsibility for data access or
+consumption approval.
+
+
+
+### 5.2.1 Data Access Approval
+
+New data access approval: currently it is a first-level approval, which is approved by the system administrator.
+
+The system administrator will review whether the access process meets the access requirements based on the data access
+business information.
+
+
+
+### 5.2.2 New data consumption approval
+
+New data consume approval: currently it is a first-level approval, which is approved by the person in charge of the
+business.
+
+Business approval: The person in charge of the data access business judges whether the consumption meets the business
+requirements according to the access information:
+
+
+
+# 6. System Management
+
+Only users with the role of system administrator can use this function. They can create, modify, and delete users:
+
+
+
+## 6.1 New user
+
+Users with system administrator rights can create new user accounts
+
+
+
+- Account types: Ordinary users (with data access and data consumption permissions, but without data access approval and
+ account management permissions); system administrators (with data access and data consumption permissions, data access
+ approval and account management permissions)
+- username: username for login
+- user password:
+ -Effective duration: the account can be used in the system
+ 
+
+## 6.2 Delete user
+
+The system administrator can delete the account of the created user. After the deletion, the account will stop using:
+
+
+
+## 6.3 User Edit
+
+The system administrator can modify the created account:
+
+
+
+The system administrator can modify the account type and effective duration to proceed:
+
+
+
+## 6.4 Change password
+
+The user can modify the account password, click [Modify Password], enter the old password and the new password, after
+confirmation, the new password of this account will take effect:
+
+
diff --git a/zh-cn/docs/modules/manager/user_manual.html b/zh-cn/docs/modules/manager/user_manual.html
index dad7fde..4700e90 100644
--- a/zh-cn/docs/modules/manager/user_manual.html
+++ b/zh-cn/docs/modules/manager/user_manual.html
@@ -12,65 +12,68 @@
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/zh-cn/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><img class="logo tube" style="width:120px;top:12px;position:absolute" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class= [...]
-<p>需系统使用用户输入账号名称和密码</p>
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/zh-cn/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><img class="logo tube" style="width:120px;top:12px;position:absolute" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class= [...]
+<p>需系统使用用户输入账号名称和密码。</p>
<p><img src="img/image-1624433272455.png" alt=""></p>
-<h2>2.数据接入</h2>
-<p>数据接入模块展示目前用户权限内接入系统所有任务列表，可以对这些任务详情查看、编辑更新和删除操作
-点击【数据接入】接入流程，数据接入信息填写有两个步骤：业务信息、数据流
-<img src="img/image-1624431177918.png" alt=""></p>
-<h3>2.1 业务信息</h3>
-<h4>2.1.1 业务信息</h4>
-<p>需要用户对接入任务填写基础业务信息
-<img src="img/image-1624431271642.png" alt=""></p>
+<h1>2. 数据接入</h1>
+<p>数据接入模块展示目前用户权限内接入系统所有任务列表，可以对这些任务详情查看、编辑更新和删除操作。</p>
+<p>点击【数据接入】接入流程，数据接入信息填写有两个步骤：业务信息、数据流。</p>
+<p><img src="img/image-1624431177918.png" alt=""></p>
+<h2>2.1 业务信息</h2>
+<h3>2.1.1 业务信息</h3>
+<p>需要用户对接入任务填写基础业务信息。</p>
+<p><img src="img/image-1624431271642.png" alt=""></p>
<ul>
-<li>业务ID：统一小写英文名称，请尽量包含产品名和简洁规范，如wechat_pay_base</li>
+<li>业务ID：统一小写英文名称，请尽量包含产品名和简洁规范，如pay_base</li>
<li>业务中文名称：业务的中文描述，便于使用与检索，最多128个字</li>
<li>业务责任人：至少2人，业务责任人可查看、修改业务信息，新增和修改所有接入配置项</li>
<li>业务介绍：剪短信对此次接入任务进行业务背景和应用介绍：</li>
</ul>
-<h4>2.1.2 接入要求</h4>
-<p>接入要求需要用户进行选择消息中间件： 高吞吐（TUBE）
-<img src="img/image-1624431306077.png" alt="">
-高吞吐—Tube ：高吞吐消息传输组件，适用于日志类的消息传递</p>
-<h4>2.1.3 接入规模</h4>
-<p>接入规模需要用户预先针对接入数据进行规模判断，以便后续分配计算和存储资源
-<img src="img/image-1624431333949.png" alt=""></p>
-<h3>2.2 数据流</h3>
-<p>点击【下一步】进入到数据流信息填写步骤，数据流信息填写有四个模块：基础信息、数据来源、数据信息、数据流向
-在数据流流程中可以点击【新建数据流】，创建一个新的数据流信息填写页面
-<img src="img/image-1624431416449.png" alt=""></p>
-<h4>2.2.1 基础信息</h4>
-<p>需用户对该接入任务中数据流的基础信息进行填写
-<img src="img/image-1624431435574.png" alt=""></p>
+<h3>2.1.2 接入要求</h3>
+<p>接入要求需要用户进行选择消息中间件：高吞吐（TUBE）：</p>
+<p><img src="img/image-1624431306077.png" alt=""></p>
+<p>高吞吐—Tube ：高吞吐消息传输组件，适用于日志类的消息传递。</p>
+<h3>2.1.3 接入规模</h3>
+<p>接入规模需要用户预先针对接入数据进行规模判断，以便后续分配计算和存储资源。</p>
+<p><img src="img/image-1624431333949.png" alt=""></p>
+<h2>2.2 数据流</h2>
+<p>点击【下一步】进入到数据流信息填写步骤，数据流信息填写有四个模块：基础信息、数据来源、数据信息、数据流向。</p>
+<p>在数据流流程中可以点击【新建数据流】，创建一个新的数据流信息填写页面：</p>
+<p><img src="img/image-1624431416449.png" alt=""></p>
+<h3>2.2.1 基础信息</h3>
+<p>需用户对该接入任务中数据流的基础信息进行填写：</p>
+<p><img src="img/image-1624431435574.png" alt=""></p>
<ul>
-<li>数据流ID：前缀根据BG/产品/项目自动生成，数据在业务中的唯一标识，TDBank中某个业务数据定义的唯一标识，跟数据源中的数据流ID、入TDW库信息表中的数据流ID一致</li>
+<li>数据流ID：前缀根据BG/产品/项目自动生成，数据在业务中的唯一标识，InLong中某个业务数据定义的唯一标识，跟数据源中的数据流ID、入库信息表中的数据流ID一致</li>
<li>数据流名称：接口信息说明,长度限制为varchar(64)，32个中文</li>
<li>数据流责任人：数据流责任人可查看、修改数据流信息，新增和修改所有接入配置项</li>
<li>数据流介绍：数据流简单文本介绍</li>
</ul>
-<h4>2.2.2 数据来源</h4>
-<p>需用户选择该数据流的消息来源，目前支持文件、自主推送三种方式，并且可以在高级选项中补充该数据来源详细信息；</p>
+<h3>2.2.2 数据来源</h3>
+<p>需用户选择该数据流的消息来源，目前支持文件、自主推送三种方式，并且可以在高级选项中补充该数据来源详细信息：</p>
<ul>
-<li>文件：业务数据以文件形式存放，业务机器部署TDBank Agent,根据定制的策略规则进行读取，详细说明链接</li>
-<li>自主推送：文案待定，技术实现与109消息中间件类型有关联
-<img src="img/image-1624431594406.png" alt=""></li>
+<li>
+<p>文件：业务数据以文件形式存放，业务机器部署 InLong Agent，根据定制的策略规则进行读取</p>
+</li>
+<li>
+<p>自主推送：通过 SDK 向消息中间件推送数据</p>
+<p><img src="img/image-1624431594406.png" alt=""></p>
+</li>
</ul>
-<h4>2.2.3 数据信息</h4>
-<p>需用户填写该数据流中数据相关信息
-<img src="img/image-1624431617259.png" alt=""></p>
+<h3>2.2.3 数据信息</h3>
+<p>需用户填写该数据流中数据相关信息：</p>
+<p><img src="img/image-1624431617259.png" alt=""></p>
<ul>
<li>数据格式：数据来源格式，是普通文本类型，或者KV键值对数据</li>
-<li>数据编码：如数据源含中文，需要选UTF-8或GBK,否则编码格式不对，入库为乱码</li>
-<li>源字段分隔符：数据发送到mq里面的格式</li>
-<li>源数据字段：数据在mq里按某种格式划分的不同含义的属性</li>
+<li>数据编码：如数据源含中文，需要选UTF-8或GBK，否则编码格式不对，入库后会乱码</li>
+<li>源字段分隔符：数据发送到 MQ 里的格式</li>
+<li>源数据字段：数据在 MQ 里按某种格式划分的不同含义的属性</li>
</ul>
-<h4>2.2.4 数据流向</h4>
-<p>需用户对此任务的流向终流向进行选择，此部分为非必填项
-目前支持hive流向和自主推送两种
-<img src="img/image-1624431713360.png" alt="">
-HIVE流向
-<img src="img/image-1624431787323.png" alt=""></p>
+<h3>2.2.4 数据流向</h3>
+<p>需用户对此任务的流向终流向进行选择，此部分为非必填项，目前支持Hive和自主推送两种：</p>
+<p><img src="img/image-1624431713360.png" alt=""></p>
+<p>HIVE流向：</p>
+<p><img src="img/image-1624431787323.png" alt=""></p>
<ul>
<li>目标库：hive数据库名（需要提前准备创建好）</li>
<li>目标表：hive表名</li>
@@ -82,87 +85,85 @@ HIVE流向
<li>JDBC url：hiveserver 的jdbcurl</li>
<li>字段相关信息： 源字段名、源字段类型、HIVE字段名、HIVE字段类型、字段描述，并支持删除和新增字段</li>
</ul>
-<h2>3.接入详情</h2>
-<h3>3.1 执行日志</h3>
-<p>当数据接入任务状态为”批准成功“和”配置失败“状态，可通过”执行日志“功能，以便用户查看任务执行进程进程和详情
-<img src="img/image-1624432002615.png" alt=""></p>
-<p>点击【执行日志】将以弹窗形式展示该任务执行日志详情
-<img src="img/image-1624432022859.png" alt="">
-执行日志中将展示该接入流程执行中任务类型、执行结果、执行日志内容、结束时间、如果执行失败可以”重启“该任务再次执行</p>
-<h3>3.2 任务详情</h3>
-<p>业务负责人/关注人可以查看该任务接入详情，并在【待提交】、【配置成功】、【配置失败】状态下可对部分信息进行修改更新
-接入任务详情中具有业务信息、数据流、流向、三个模块</p>
-<h4>3.2.1 业务信息</h4>
-<p>展示接入任务中基础业务信息，点击【编辑】可对部分内容进行修改更改
-<img src="img/image-1624432076857.png" alt=""></p>
-<h4>3.2.2 数据流</h4>
-<p>展示该接入任务下数据流基础信息，点击【新建数据流】可新建一条数据流信息
-<img src="img/image-1624432092795.png" alt=""></p>
-<h4>3.2.3 流向</h4>
-<p>展示该接入任务中数据流向基础信息，通过通过下拉框选择不同流向类型，点击【新建流向配置】可新建一条数据流向信息
-<img src="img/image-1624432114765.png" alt=""></p>
-<h2>4 数据消费</h2>
-<p>数据消费目前不支持直接消费接入数据，需走数据审批流程后方可正常消费数据；
-点击【新建消费】，进入数据消费流程，需要对消费信息相关信息进行填写；
+<h1>3. 接入详情</h1>
+<h2>3.1 执行日志</h2>
+<p>当数据接入任务状态为”批准成功“和”配置失败“状态，可通过”执行日志“功能，以便用户查看任务执行进程进程和详情：</p>
+<p><img src="img/image-1624432002615.png" alt=""></p>
+<p>点击【执行日志】将以弹窗形式展示该任务执行日志详情：</p>
+<p><img src="img/image-1624432022859.png" alt=""></p>
+<p>执行日志中将展示该接入流程执行中任务类型、执行结果、执行日志内容、结束时间、如果执行失败可以”重启“该任务再次执行。</p>
+<h2>3.2 任务详情</h2>
+<p>业务负责人/关注人可以查看该任务接入详情，并在【待提交】、【配置成功】、【配置失败】状态下可对部分信息进行修改更新接入任务详情中具有业务信息、数据流、流向三个模块。</p>
+<h3>3.2.1 业务信息</h3>
+<p>展示接入任务中基础业务信息，点击【编辑】可对部分内容进行修改更改：</p>
+<p><img src="img/image-1624432076857.png" alt=""></p>
+<h3>3.2.2 数据流</h3>
+<p>展示该接入任务下数据流基础信息，点击【新建数据流】可新建一条数据流信息：</p>
+<p><img src="img/image-1624432092795.png" alt=""></p>
+<h3>3.2.3 流向</h3>
+<p>展示该接入任务中数据流向基础信息，通过通过下拉框选择不同流向类型，点击【新建流向配置】可新建一条数据流向：</p>
+<p><img src="img/image-1624432114765.png" alt=""></p>
+<h1>4. 数据消费</h1>
+<p>数据消费目前不支持直接消费接入数据，需走数据审批流程后方可正常消费数据； 点击【新建消费】，进入数据消费流程，需要对消费信息相关信息进行填写：
<img src="img/image-1624432235900.png" alt=""></p>
-<h3>4.1 消费信息</h3>
-<p>申请人需在该信息填写模块中逐步填写数据消费申请相关基础消费业务信息
-<img src="img/image-1624432254118.png" alt=""></p>
+<h2>4.1 消费信息</h2>
+<p>申请人需在该信息填写模块中逐步填写数据消费申请相关基础消费业务信息：</p>
+<p><img src="img/image-1624432254118.png" alt=""></p>
<ul>
<li>消费组名称：前缀根据BG/产品/项目自动生成，消费者的简要名称，必须是小写字母、数字、下划线组成，最后审批会根据简称拼接分配出消费者名称</li>
<li>消费责任人：自行选择责任人，必须至少2人；责任人可查看、修改消费信息</li>
<li>消费目标业务ID：需要选择消费数据的业务ID，可以点击【查询】后，在弹窗页面中选择合适的业务ID，如下图所示：</li>
<li>数据用途：选择数据使用用途</li>
-<li>数据用途说明：需申请人根据自身消费场景，简要说明使用的项目和数据的用途
-信息填完完成后，点击【提交】后，会将次数据消费流程正式提交待审批人审批后方可生效</li>
+<li>数据用途说明：需申请人根据自身消费场景，简要说明使用的项目和数据的用途</li>
</ul>
+<p>信息填完完成后，点击【提交】后，会将次数据消费流程正式提交待审批人审批后方可生效。</p>
<p><img src="img/image-1624432286674.png" alt=""></p>
-<h2>5.审批管理</h2>
-<p>审批管理功能模块目前包含了我的申请和我的审批，管理系统中数据接入和数据消费申请审批全部任务</p>
-<h3>5.1 我的申请</h3>
-<p>展示目前申请人在系统中数据接入、消费提交的任务列表，点击【详情】可以查看目前该任务基础信和审批进程
-<img src="img/image-1624432445002.png" alt=""></p>
-<h4>5.1.1 数据接入详情</h4>
-<p>数据接入任务详细展示目前该申请任务基础信息包括：申请人相关信息、申请接入基础信息、资源预估信息、以及目前审批进程节点
-<img src="img/image-1624432458971.png" alt=""></p>
-<h4>5.1.2 数据消费详情</h4>
-<p>数据消费任务详情展示目前申请任务基础信息包括：申请人信息、基础消费信息、资源预估、以及目前审批进程节点
-<img src="img/image-1624432474526.png" alt=""></p>
-<h3>5.2 我的审批</h3>
-<p>作为具有审批权限的数据接入员和系统成员，具备对数据接入或者消费审批职责
-<img src="img/image-1624432496461.png" alt=""></p>
-<h4>5.2.1 数据接入审批</h4>
-<p>新建数据接入审批：目前为一级审批，由系统管理员审批
-系统管理员将根据数据接入业务信息审核此次接入流程是否符合接入要求
-<img src="img/image-1624432515850.png" alt=""></p>
-<h4>5.2.2 新建数据消费审批</h4>
-<p>新建数据消费审批：目前为一级审批，由业务负责人审批
-业务审批：主要由数据接入业务负责人根据接入参数信息判断是否符合接入要求，以此依据审批该申请消费任务
-<img src="img/image-1624432535541.png" alt=""></p>
-<h2>6 系统管理</h2>
-<p>系统管理目前针对于具有系统管理员身份用户，可以进行账号创建、修改、删除操作
-<img src="img/image-1624432652141.png" alt=""></p>
-<h3>6.1 新建用户</h3>
-<p>具有系统管理员权限用户，可以进行创建新用户账号
-<img src="img/image-1624432668340.png" alt=""></p>
+<h1>5. 审批管理</h1>
+<p>审批管理功能模块目前包含了我的申请和我的审批，管理系统中数据接入和数据消费申请审批全部任务。</p>
+<h2>5.1 我的申请</h2>
+<p>展示目前申请人在系统中数据接入、消费提交的任务列表，点击【详情】可以查看目前该任务基础信和审批进程：</p>
+<p><img src="img/image-1624432445002.png" alt=""></p>
+<h3>5.1.1 数据接入详情</h3>
+<p>数据接入任务详细展示目前该申请任务基础信息包括：申请人相关信息、申请接入基础信息，以及目前审批进程节点：</p>
+<p><img src="img/image-1624432458971.png" alt=""></p>
+<h3>5.1.2 数据消费详情</h3>
+<p>数据消费任务详情展示目前申请任务基础信息包括：申请人信息、基础消费信息，以及目前审批进程节点：</p>
+<p><img src="img/image-1624432474526.png" alt=""></p>
+<h2>5.2 我的审批</h2>
+<p>作为具有审批权限的数据接入员和系统成员，具备对数据接入或者消费审批职责：</p>
+<p><img src="img/image-1624432496461.png" alt=""></p>
+<h3>5.2.1 数据接入审批</h3>
+<p>新建数据接入审批：目前为一级审批，由系统管理员审批。</p>
+<p>系统管理员将根据数据接入业务信息，审核此次接入流程是否符合接入要求：</p>
+<p><img src="img/image-1624432515850.png" alt=""></p>
+<h3>5.2.2 新建数据消费审批</h3>
+<p>新建数据消费审批：目前为一级审批，由业务负责人审批。</p>
+<p>业务审批：由数据接入业务负责人根据接入信息判断此消费是否符合业务要求：</p>
+<p><img src="img/image-1624432535541.png" alt=""></p>
+<h1>6. 系统管理</h1>
+<p>角色为系统管理员的用户才可以使用此功能，他们可以创建、修改、删除用户：</p>
+<p><img src="img/image-1624432652141.png" alt=""></p>
+<h2>6.1 新建用户</h2>
+<p>具有系统管理员权限用户，可以进行创建新用户账号：</p>
+<p><img src="img/image-1624432668340.png" alt=""></p>
<ul>
-<li>账号类型： 普通用户（具有数据接入和数据消费权限，不具有数据接入审批和账号管理权限）； 系统管理员（具有数据接入和数据消费权限、同时也需要对数据接入审批和账号管理权限）</li>
+<li>账号类型： 普通用户（具有数据接入和数据消费权限，不具有数据接入审批和账号管理权限）；系统管理员（具有数据接入和数据消费权限、数据接入审批和管理账号的权限）</li>
<li>用户名称：用户登录账号ID</li>
<li>用户密码：用户登录密码</li>
<li>有效时长：该账号可在系统使用期限</li>
</ul>
<p><img src="img/image-1624432740241.png" alt=""></p>
-<h3>6.2 删除用户</h3>
-<p>系统管理员可以对已创建的用户进行账户删除，删除后次账号将停止使用
-<img src="img/image-1624432759224.png" alt=""></p>
-<h3>6.3 用户编辑</h3>
-<p>系统管理员可以对以已创建账号，进行二次编辑
-<img src="img/image-1624432778845.png" alt="">
-目前对于系统管理员支持对已有账号中：账号类型和有效时长进行修改
-<img src="img/image-1624432797226.png" alt=""></p>
-<h3>6.4 更改密码</h3>
-<p>用户可以自行更改账号密码，点击【修改密码】，用户需要输入旧密码和新密码，确认后次账号新密码将生效
-<img src="img/image-1624432829313.png" alt=""></p>
+<h2>6.2 删除用户</h2>
+<p>系统管理员可以对已创建的用户进行账户删除，删除后此账号将停止使用：</p>
+<p><img src="img/image-1624432759224.png" alt=""></p>
+<h2>6.3 修改用户</h2>
+<p>系统管理员可以修改已创建的账号：</p>
+<p><img src="img/image-1624432778845.png" alt=""></p>
+<p>系统管理员可以修改账号类型和有效时长进行：</p>
+<p><img src="img/image-1624432797226.png" alt=""></p>
+<h2>6.4 更改密码</h2>
+<p>用户可以修改账号密码，点击【修改密码】，输入旧密码和新密码，确认后此账号新密码将生效：</p>
+<p><img src="img/image-1624432829313.png" alt=""></p>
</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/incubator-logo.svg"/><div class="cols-container"><div class="col col-24"><p>Apache InLong (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with [...]
<script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
<script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
diff --git a/zh-cn/docs/modules/manager/user_manual.json b/zh-cn/docs/modules/manager/user_manual.json
index f5e65a4..abf9240 100644
--- a/zh-cn/docs/modules/manager/user_manual.json
+++ b/zh-cn/docs/modules/manager/user_manual.json
@@ -1,6 +1,6 @@
{
"filename": "user_manual.md",
- "__html": "<h2>1.用户登录</h2>\n<p>需系统使用用户输入账号名称和密码</p>\n<p><img src=\"img/image-1624433272455.png\" alt=\"\"></p>\n<h2>2.数据接入</h2>\n<p>数据接入模块展示目前用户权限内接入系统所有任务列表，可以对这些任务详情查看、编辑更新和删除操作\n点击【数据接入】接入流程，数据接入信息填写有两个步骤：业务信息、数据流\n<img src=\"img/image-1624431177918.png\" alt=\"\"></p>\n<h3>2.1 业务信息</h3>\n<h4>2.1.1 业务信息</h4>\n<p>需要用户对接入任务填写基础业务信息\n<img src=\"img/image-1624431271642.png\" alt=\"\"></p>\n<ul>\n<li>业务ID：统一小写英文名称，请尽量包含产品名和简洁规范，如wechat_pay_base</li>\n<li>业务中文名称：业务的中文描述，便于使用与检索，最多128个字</l [...]
+ "__html": "<h1>1. 用户登录</h1>\n<p>需系统使用用户输入账号名称和密码。</p>\n<p><img src=\"img/image-1624433272455.png\" alt=\"\"></p>\n<h1>2. 数据接入</h1>\n<p>数据接入模块展示目前用户权限内接入系统所有任务列表，可以对这些任务详情查看、编辑更新和删除操作。</p>\n<p>点击【数据接入】接入流程，数据接入信息填写有两个步骤：业务信息、数据流。</p>\n<p><img src=\"img/image-1624431177918.png\" alt=\"\"></p>\n<h2>2.1 业务信息</h2>\n<h3>2.1.1 业务信息</h3>\n<p>需要用户对接入任务填写基础业务信息。</p>\n<p><img src=\"img/image-1624431271642.png\" alt=\"\"></p>\n<ul>\n<li>业务ID：统一小写英文名称，请尽量包含产品名和简洁规范，如pay_base</li>\n<li>业务中文名称：业务的中文描 [...]
"link": "/zh-cn/docs/modules/manager/user_manual.html",
"meta": {}
}
\ No newline at end of file
diff --git a/zh-cn/docs/modules/manager/user_manual.md b/zh-cn/docs/modules/manager/user_manual.md
index e2023ad..4e0bb87 100644
--- a/zh-cn/docs/modules/manager/user_manual.md
+++ b/zh-cn/docs/modules/manager/user_manual.md
@@ -1,65 +1,93 @@
-## 1.用户登录
-需系统使用用户输入账号名称和密码
+# 1. 用户登录
+
+需系统使用用户输入账号名称和密码。
-## 2.数据接入
-数据接入模块展示目前用户权限内接入系统所有任务列表，可以对这些任务详情查看、编辑更新和删除操作
-点击【数据接入】接入流程，数据接入信息填写有两个步骤：业务信息、数据流
+# 2. 数据接入
+
+数据接入模块展示目前用户权限内接入系统所有任务列表，可以对这些任务详情查看、编辑更新和删除操作。
+
+点击【数据接入】接入流程，数据接入信息填写有两个步骤：业务信息、数据流。
+
-### 2.1 业务信息
-#### 2.1.1 业务信息
-需要用户对接入任务填写基础业务信息
+## 2.1 业务信息
+
+### 2.1.1 业务信息
+
+需要用户对接入任务填写基础业务信息。
+
-- 业务ID：统一小写英文名称，请尽量包含产品名和简洁规范，如wechat_pay_base
+
+- 业务ID：统一小写英文名称，请尽量包含产品名和简洁规范，如pay_base
- 业务中文名称：业务的中文描述，便于使用与检索，最多128个字
- 业务责任人：至少2人，业务责任人可查看、修改业务信息，新增和修改所有接入配置项
- 业务介绍：剪短信对此次接入任务进行业务背景和应用介绍：
-#### 2.1.2 接入要求
-接入要求需要用户进行选择消息中间件： 高吞吐（TUBE）
+### 2.1.2 接入要求
+
+接入要求需要用户进行选择消息中间件：高吞吐（TUBE）：
+
-高吞吐—Tube ：高吞吐消息传输组件，适用于日志类的消息传递
-#### 2.1.3 接入规模
-接入规模需要用户预先针对接入数据进行规模判断，以便后续分配计算和存储资源
+高吞吐—Tube ：高吞吐消息传输组件，适用于日志类的消息传递。
+
+### 2.1.3 接入规模
+
+接入规模需要用户预先针对接入数据进行规模判断，以便后续分配计算和存储资源。
+
-### 2.2 数据流
-点击【下一步】进入到数据流信息填写步骤，数据流信息填写有四个模块：基础信息、数据来源、数据信息、数据流向
-在数据流流程中可以点击【新建数据流】，创建一个新的数据流信息填写页面
+## 2.2 数据流
+
+点击【下一步】进入到数据流信息填写步骤，数据流信息填写有四个模块：基础信息、数据来源、数据信息、数据流向。
+
+在数据流流程中可以点击【新建数据流】，创建一个新的数据流信息填写页面：
+
-#### 2.2.1 基础信息
-需用户对该接入任务中数据流的基础信息进行填写
+### 2.2.1 基础信息
+
+需用户对该接入任务中数据流的基础信息进行填写：
+
-- 数据流ID：前缀根据BG/产品/项目自动生成，数据在业务中的唯一标识，TDBank中某个业务数据定义的唯一标识，跟数据源中的数据流ID、入TDW库信息表中的数据流ID一致
+
+- 数据流ID：前缀根据BG/产品/项目自动生成，数据在业务中的唯一标识，InLong中某个业务数据定义的唯一标识，跟数据源中的数据流ID、入库信息表中的数据流ID一致
- 数据流名称：接口信息说明,长度限制为varchar(64)，32个中文
- 数据流责任人：数据流责任人可查看、修改数据流信息，新增和修改所有接入配置项
- 数据流介绍：数据流简单文本介绍
-#### 2.2.2 数据来源
-需用户选择该数据流的消息来源，目前支持文件、自主推送三种方式，并且可以在高级选项中补充该数据来源详细信息；
-- 文件：业务数据以文件形式存放，业务机器部署TDBank Agent,根据定制的策略规则进行读取，详细说明链接
-- 自主推送：文案待定，技术实现与109消息中间件类型有关联
-
+### 2.2.2 数据来源
+
+需用户选择该数据流的消息来源，目前支持文件、自主推送三种方式，并且可以在高级选项中补充该数据来源详细信息：
+- 文件：业务数据以文件形式存放，业务机器部署 InLong Agent，根据定制的策略规则进行读取
+- 自主推送：通过 SDK 向消息中间件推送数据
+
+ 
+
+### 2.2.3 数据信息
+
+需用户填写该数据流中数据相关信息：
-#### 2.2.3 数据信息
-需用户填写该数据流中数据相关信息
+
- 数据格式：数据来源格式，是普通文本类型，或者KV键值对数据
-- 数据编码：如数据源含中文，需要选UTF-8或GBK,否则编码格式不对，入库为乱码
-- 源字段分隔符：数据发送到mq里面的格式
-- 源数据字段：数据在mq里按某种格式划分的不同含义的属性
+- 数据编码：如数据源含中文，需要选UTF-8或GBK，否则编码格式不对，入库后会乱码
+- 源字段分隔符：数据发送到 MQ 里的格式
+- 源数据字段：数据在 MQ 里按某种格式划分的不同含义的属性
+
+### 2.2.4 数据流向
+
+需用户对此任务的流向终流向进行选择，此部分为非必填项，目前支持Hive和自主推送两种：
-#### 2.2.4 数据流向
-需用户对此任务的流向终流向进行选择，此部分为非必填项
-目前支持hive流向和自主推送两种
-HIVE流向
+
+HIVE流向：
+
+
- 目标库：hive数据库名（需要提前准备创建好）
- 目标表：hive表名
- 一级分区：hive数据划分hdfs数据一级子目录的字段名
@@ -70,95 +98,144 @@ HIVE流向
- JDBC url：hiveserver 的jdbcurl
- 字段相关信息： 源字段名、源字段类型、HIVE字段名、HIVE字段类型、字段描述，并支持删除和新增字段
-## 3.接入详情
-### 3.1 执行日志
-当数据接入任务状态为”批准成功“和”配置失败“状态，可通过”执行日志“功能，以便用户查看任务执行进程进程和详情
+# 3. 接入详情
+
+## 3.1 执行日志
+
+当数据接入任务状态为”批准成功“和”配置失败“状态，可通过”执行日志“功能，以便用户查看任务执行进程进程和详情：
+
-点击【执行日志】将以弹窗形式展示该任务执行日志详情
+点击【执行日志】将以弹窗形式展示该任务执行日志详情：
+
-执行日志中将展示该接入流程执行中任务类型、执行结果、执行日志内容、结束时间、如果执行失败可以”重启“该任务再次执行
-### 3.2 任务详情
-业务负责人/关注人可以查看该任务接入详情，并在【待提交】、【配置成功】、【配置失败】状态下可对部分信息进行修改更新
-接入任务详情中具有业务信息、数据流、流向、三个模块
+执行日志中将展示该接入流程执行中任务类型、执行结果、执行日志内容、结束时间、如果执行失败可以”重启“该任务再次执行。
+
+## 3.2 任务详情
+
+业务负责人/关注人可以查看该任务接入详情，并在【待提交】、【配置成功】、【配置失败】状态下可对部分信息进行修改更新接入任务详情中具有业务信息、数据流、流向三个模块。
+
+### 3.2.1 业务信息
+
+展示接入任务中基础业务信息，点击【编辑】可对部分内容进行修改更改：
-#### 3.2.1 业务信息
-展示接入任务中基础业务信息，点击【编辑】可对部分内容进行修改更改
-#### 3.2.2 数据流
-展示该接入任务下数据流基础信息，点击【新建数据流】可新建一条数据流信息
+### 3.2.2 数据流
+
+展示该接入任务下数据流基础信息，点击【新建数据流】可新建一条数据流信息：
+
-#### 3.2.3 流向
-展示该接入任务中数据流向基础信息，通过通过下拉框选择不同流向类型，点击【新建流向配置】可新建一条数据流向信息
+### 3.2.3 流向
+
+展示该接入任务中数据流向基础信息，通过通过下拉框选择不同流向类型，点击【新建流向配置】可新建一条数据流向：
+
-## 4 数据消费
-数据消费目前不支持直接消费接入数据，需走数据审批流程后方可正常消费数据；
-点击【新建消费】，进入数据消费流程，需要对消费信息相关信息进行填写；
+# 4. 数据消费
+
+数据消费目前不支持直接消费接入数据，需走数据审批流程后方可正常消费数据； 点击【新建消费】，进入数据消费流程，需要对消费信息相关信息进行填写：
-### 4.1 消费信息
-申请人需在该信息填写模块中逐步填写数据消费申请相关基础消费业务信息
+## 4.1 消费信息
+
+申请人需在该信息填写模块中逐步填写数据消费申请相关基础消费业务信息：
+
+
- 消费组名称：前缀根据BG/产品/项目自动生成，消费者的简要名称，必须是小写字母、数字、下划线组成，最后审批会根据简称拼接分配出消费者名称
- 消费责任人：自行选择责任人，必须至少2人；责任人可查看、修改消费信息
- 消费目标业务ID：需要选择消费数据的业务ID，可以点击【查询】后，在弹窗页面中选择合适的业务ID，如下图所示：
- 数据用途：选择数据使用用途
- 数据用途说明：需申请人根据自身消费场景，简要说明使用的项目和数据的用途
-信息填完完成后，点击【提交】后，会将次数据消费流程正式提交待审批人审批后方可生效
+
+信息填完完成后，点击【提交】后，会将次数据消费流程正式提交待审批人审批后方可生效。
-## 5.审批管理
-审批管理功能模块目前包含了我的申请和我的审批，管理系统中数据接入和数据消费申请审批全部任务
-### 5.1 我的申请
-展示目前申请人在系统中数据接入、消费提交的任务列表，点击【详情】可以查看目前该任务基础信和审批进程
+# 5. 审批管理
+
+审批管理功能模块目前包含了我的申请和我的审批，管理系统中数据接入和数据消费申请审批全部任务。
+
+## 5.1 我的申请
+
+展示目前申请人在系统中数据接入、消费提交的任务列表，点击【详情】可以查看目前该任务基础信和审批进程：
+
-#### 5.1.1 数据接入详情
-数据接入任务详细展示目前该申请任务基础信息包括：申请人相关信息、申请接入基础信息、资源预估信息、以及目前审批进程节点
+### 5.1.1 数据接入详情
+
+数据接入任务详细展示目前该申请任务基础信息包括：申请人相关信息、申请接入基础信息，以及目前审批进程节点：
+
-#### 5.1.2 数据消费详情
-数据消费任务详情展示目前申请任务基础信息包括：申请人信息、基础消费信息、资源预估、以及目前审批进程节点
+
+### 5.1.2 数据消费详情
+
+数据消费任务详情展示目前申请任务基础信息包括：申请人信息、基础消费信息，以及目前审批进程节点：
+
-### 5.2 我的审批
-作为具有审批权限的数据接入员和系统成员，具备对数据接入或者消费审批职责
+
+## 5.2 我的审批
+
+作为具有审批权限的数据接入员和系统成员，具备对数据接入或者消费审批职责：
+
-#### 5.2.1 数据接入审批
-新建数据接入审批：目前为一级审批，由系统管理员审批
-系统管理员将根据数据接入业务信息审核此次接入流程是否符合接入要求
+
+### 5.2.1 数据接入审批
+
+新建数据接入审批：目前为一级审批，由系统管理员审批。
+
+系统管理员将根据数据接入业务信息，审核此次接入流程是否符合接入要求：
+
-#### 5.2.2 新建数据消费审批
-新建数据消费审批：目前为一级审批，由业务负责人审批
-业务审批：主要由数据接入业务负责人根据接入参数信息判断是否符合接入要求，以此依据审批该申请消费任务
+
+### 5.2.2 新建数据消费审批
+
+新建数据消费审批：目前为一级审批，由业务负责人审批。
+
+业务审批：由数据接入业务负责人根据接入信息判断此消费是否符合业务要求：
+
-## 6 系统管理
-系统管理目前针对于具有系统管理员身份用户，可以进行账号创建、修改、删除操作
+# 6. 系统管理
+
+角色为系统管理员的用户才可以使用此功能，他们可以创建、修改、删除用户：
+
-### 6.1 新建用户
-具有系统管理员权限用户，可以进行创建新用户账号
+
+## 6.1 新建用户
+
+具有系统管理员权限用户，可以进行创建新用户账号：
+
-- 账号类型： 普通用户（具有数据接入和数据消费权限，不具有数据接入审批和账号管理权限）； 系统管理员（具有数据接入和数据消费权限、同时也需要对数据接入审批和账号管理权限）
+
+- 账号类型： 普通用户（具有数据接入和数据消费权限，不具有数据接入审批和账号管理权限）；系统管理员（具有数据接入和数据消费权限、数据接入审批和管理账号的权限）
- 用户名称：用户登录账号ID
- 用户密码：用户登录密码
- 有效时长：该账号可在系统使用期限
-### 6.2 删除用户
-系统管理员可以对已创建的用户进行账户删除，删除后次账号将停止使用
+## 6.2 删除用户
+
+系统管理员可以对已创建的用户进行账户删除，删除后此账号将停止使用：
+
-### 6.3 用户编辑
-系统管理员可以对以已创建账号，进行二次编辑
+## 6.3 修改用户
+
+系统管理员可以修改已创建的账号：
+
-目前对于系统管理员支持对已有账号中：账号类型和有效时长进行修改
+
+系统管理员可以修改账号类型和有效时长进行：
+
-### 6.4 更改密码
-用户可以自行更改账号密码，点击【修改密码】，用户需要输入旧密码和新密码，确认后次账号新密码将生效
+## 6.4 更改密码
+
+用户可以修改账号密码，点击【修改密码】，输入旧密码和新密码，确认后此账号新密码将生效：
+
