- 论坛徽章:
- 0
|
How to enable DB2 Web Query (5733-QU2) on your system?
1. Install DB2 WEB QUERY
- Install Product Base
RSTLICPGM LICPGM(5733QU2) DEV(OPT01)
- If purchased - Install the Active Reports option
RSTLICPGM LICPGM(5733QU2) DEV(OPT01) OPTION(1)
- If purchased - Install the OLAP Enablement option
RSTLICPGM LICPGM(5733QU2) DEV(OPT01) OPTION(2)
- If purchased - Install the Developer Workbench:
RSTLICPGM LICPGM(5733QU2) DEV(OPT01) OPTION(3)
- If purchased – (V1R1M1 Only) Install the Run Time User Enablement option
RSTLICPGM LICPGM(5733QU2) DEV(OPT01) OPTION(4)
2. To register the DB2 Web Query HTTP Instance
CALL QWEBQRY76/REGWEBQRY
3. The first time the product is installed, it creates a user profile QWEBQRYADM with no
password supplied. Run the following command to set its password.
CHGUSRPRF USRPRF(QWEBQRYADM) PASSWORD(<yourpwd>)
4. Start and End Web Query
- QWEBQRY76/STRWEBQRY START(*ALL)
Use the STRTWEBQRY command to start all the jobs that are required to run Web Query.
- QWEBQRY76/ENDWEBQRY
Use the ENDWEBQRY command to end the Reporting Server.
We recommend that you use the OPTION (*CLEAR).
- QWEBQRY76/TRCWEBQRY
The TRCWEBQRY command turns on, turns off, and saves server traces.
- QWEBQRY76/DSPWEBQRY
The DSPWEBQRY command displays the server status output using DSPF.
NOTE=============================================================================
DB2 Web Query server jobs
DB2 Web Query connects to i5/OS using the SQL call-level interface (CLI). CLI is a callable
SQL programming interface that is available in DB2 on i5/OS. CLI consists of application
programming interfaces (APIs) that are used to connect to the server and start dynamic SQL
statements. The CLI is a subset of Open Database Connectivity (ODBC). The system job that
processes CLI is QSQSRVR. For more information about CLI, refer to System i Database
DB2 UDB SQL call level interface (ODBC) on the Web at:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/cli/rzadp.pdf
The following jobs run on your server when the Reporting Server is running. For all jobs, the
start time of the job is the start time of the Reporting Server.
(01). EDAPTH: There is one job that helps with the workspace process.
(02). EDAPLOG: There is one job that contains startup information.
(03). EDAPGWY: There are three of these jobs, which are listener jobs, one each for HTTP, TCP, and Java.
These jobs receive incoming requests and hand off work to the TSCOM3 jobs.
(04). TSCOM3: By default, four of these jobs are running. These jobs accept the request from the EDAPGWY
job and translate the DB2 Web Query request into SQL. One TSCOM3 job does not correspond to one
user; one TSCOM3 job can service several users. For this reason, the design of these jobs contributes
to the scalability of the product. They are referred to as "agents."
(05). JSCOM3: There is one job, which services Java processes.
(06). HLISNK: There is one job, which is an internal server process.
(07). QP0ZSPWP: This job is the DB2 Web Query JVM thread.
(08). WQLWI7: This job is for integrated application server jobs. Three of these jobs should be running
whenever DB2 Web Query is active.
(09). QSQSRVR: This i5/OS native prestart job handles SQL requests that are made over CLI. This job does
the actual database work of optimization and returning the result.
All these jobs are started in QSYSWRK when the STRWEBQRY command is used. The QSQSRVR jobs always
run in the QSYSWRK subsystem, even if you configure all the other jobs to run in their own subsystem.
You can find information about the runtime environment, including the ports that are used, in
/QIBM/UserData/webquery/ibi/srv76/wfs/edaprint.log.
=============================================================================NOTE
5. Create DB2WQRY
CHGSYSVAL SYSVAL(QLOCALE) VALUE('/QSYS.LIB/ZH_CN.LOCALE')
CHGSYSVAL SYSVAL(QSETJOBATR) VALUE('*CCSID *DATFMT *DATSEP *TIMSEP *DECFMT *SRTSEQ')
CHGUSRPRF USRPRF(QSECOFR) LANGID(CHS) CNTRYID(CN) CCSID(*SYSVAL)
SETJOBATR(*SYSVAL) LOCALE(*SYSVAL)
CHGUSRPRF USRPRF(QWEBQRYADM) LANGID(CHS) CNTRYID(CN) CCSID(*SYSVAL)
SETJOBATR(*SYSVAL) LOCALE(*SYSVAL)
CRTUSRPRF USRPRF(DB2WQRY) PASSWORD(<yourpwd>) USRCLS(*SECOFR)
TEXT('User Profile for DB2 Web Query')
LANGID(CHS) CNTRYID(CN) CCSID(*SYSVAL)
SETJOBATR(*SYSVAL) LOCALE(*SYSVAL)
// In order to create a Domain, a user should be in group MRADMIN
CHGUSRPRF USRPRF(DB2WQRY) GRPPRF(MRADMIN)
NOTE=============================================================================
// If user already has a group profile, you can set MRADMIN into his supplemental group
CHGUSRPRF USRPRF(DB2WQRY) SUPGRPPRF(MRADMIN) // Supplemental group
=============================================================================NOTE
6. Registering named users
CALL QWEBQRY76/WQADDLIC 'DB2WQRY'
NOTE=============================================================================
Named User Licensing (each user needs to be pre-authorized):
(1) Registering a new user
- To register a user with DB2 Web Query, enter the following command:
CALL QWEBQRY76/WQADDLIC 'USERPROFILE'
USERPROFILE references your System i user profile name and must be specified in
uppercase letters.
(2) Removing a DB2 Web Query registration
- To remove a registered DB2 Web Query user, enter the following command:
CALL QWEBQRY76/WQRLSLIC 'USERPROFILE'
Again your user profile must be in uppercase.
(3) Displaying the registered users
- To display your currently registered users, enter the following command:
WRKLICINF PRDID(5733QU2)
Then select option 8 for feature 5050.
=============================================================================NOTE
7. Log into DB2 Web Query
For Login:
http://<ip_address>:11331/webquery => DB2WQRY / <yourpwd>
For Administration:
http://<ip_address>:11331/webquery_html/wfconsole.htm => QWEBQRYADM / <yourpwd>
NOTE=============================================================================
If you get the following error message:
Invalid userid and password. Please try again.
please consider entering:
ADDLNK OBJ('/QIBM/ProdData/OS400/jt400/lib/jt400Native.jar')
NEWLNK('/QIBM/UserData/webquery/ibi/webfocus76/WQLWI7/lwi/lib/jt400Native.jar')
LNKTYPE('*SYMBOLIC')
Restart DB2WEB server and its HTTP server instance
QWEBQRY76/ENDWEBQRY OPTION(*CLEAR)
QWEBQRY76/STRWEBQRY START(*ALL)
============================================================================NOTE
8. Create a Domain and Assign authority to users
(1). Log on to the DB2 Web Query home page as administrator, which is a user profile that
belongs to the MRADMIN group.
(2). Right-click Domains and select New Domain.
Please use exactly 8 characters for Domain name. => C609AEBF
(3). From the System i command line, create the user profiles using the following CL commands:
CRTUSRPRF USRPRF(MD<Domain>) TEXT('Group Profile for Developers')
CRTUSRPRF USRPRF(MU<Domain>) TEXT('Group Profile for Basic Users')
(4). Assign the existing users their correct authority. Enter CHGUSRPRF as follows:
CHGUSRPRF USRPRF(<user1>) GRPPRF(MD<Domain>)
CHGUSRPRF USRPRF(<user2>) GRPPRF(MU<Domain>)
For example:
CRTUSRPRF USRPRF(DB2WEBDEV) PASSWORD(<yourpwd>) USRCLS(*SECOFR)
TEXT('User Profile for DB2 Web Query')
LANGID(CHS) CNTRYID(CN) CCSID(*SYSVAL)
SETJOBATR(*SYSVAL) LOCALE(*SYSVAL)
CRTUSRPRF USRPRF(DB2WEBUSR) PASSWORD(<yourpwd>) USRCLS(*SECOFR)
TEXT('User Profile for DB2 Web Query')
LANGID(CHS) CNTRYID(CN) CCSID(*SYSVAL)
SETJOBATR(*SYSVAL) LOCALE(*SYSVAL)
CHGUSRPRF USRPRF(DB2WEBDEV) GRPPRF(MD<Domain>) // Developer Group
CHGUSRPRF USRPRF(DB2WEBUSR) GRPPRF(MU<Domain>) // User Group
CALL QWEBQRY76/WQADDLIC 'DB2WEBDEV'
CALL QWEBQRY76/WQADDLIC 'MU<Domain>' // Assign authority to the whole user group.
NOTE=============================================================================
User Type ------------------------------- Authority ---------------------------------
MRADMIN Create Domain / Create Subfolder/ Create report/ Change Report / Run Report
MD<Domain> Create Subfolder/ Create report/ Change Report / Run Report
MU<Domain> Run Report
=============================================================================NOTE
9. Download QWQCENT.SAVF from the following URL, and upload it to your system:
ftp://www.redbooks.ibm.com/redbooks/SG247214
On the command line, enter:
RSTLIB SAVLIB(QWQCENT) DEV(*SAVF) SAVF(QGPL/QWQCENT)
10. Log into DB2 Web Query by using DB2WEBDEV, Create subfolder under <Domain>/Report.
11. Right-click subfolder and select Metadata.
NOTE=============================================================================
Metadata are under /QIBM/USERDATA/webquery/ibi/apps/baseapp
If built from a file, the metadata will include:
* Master File (*.mas): This file identifies the fields of the table.
* Access File (*.acx): This file identifies the object name and type on which the metadata is created.
If built from a Query Definition, the metadata will include:
* Master File (*.mas): This file identifies QRYDFN, the fields of that query's result set.
* Access File (*.acx): This file identifies the object name and type on which the metadata is created.
and three additional files:
* (*.fex)
* (*.inf)
* (*_Info2.txt)
To delete Metadata files, enter:
WRKLNK OBJ('/QIBM/USERDATA/webquery/ibi/apps/baseapp/*')
Find and delete the coresponding files.
=============================================================================NOTE
12. Now, you can start using DB2 Web Query.
Refer to the following redbook, see Chapter 4/5/6/7...
SG24-7214-00 Getting Started with DB2 Web Query for System i (November 2007)
http://www.redbooks.ibm.com/abstracts/sg247214.html?Open
[ 本帖最后由 oliverchenbing 于 2009-7-25 14:24 编辑 ] |
|
免费注册
发表于 2009-07-25 13:38
发表于 2009-07-27 12:50