EasyManage

EasyManage Platform : Quickstart Guide

Table Of Contents


 

Quickstart Guide

 

 

(Updated: May-02-19, Build 2019 April)

 

 

 


 

Contents

 

Introduction 4

Chapter 1: Installation 4

Chapter 2: EM Platform Configuration Parameters 25

Chapter 3: Java Utility Programs, Batch Jobs 34

Chapter 4: Administering EM Platform 46

Chapter 5: Migrating From Previous Platform Release 48

 


 

 

Introduction



This guide describes the install, setup and configuration features. dministrator

 

 

Chapter 1: Installation


This section describes how to install EasyManage Platform on Microsoft Windows and/or Unix operating platforms.

 

Installation Type

 

Initial Installation

If you are installing EasyManage Platform for the first time, follow the sections below in this chapter.

Migrating From previous Release

If you are upgrading or migrating from previous versions of EasyManage Platform then please refer to chapter “Migrating from EasyManage Platform Previous Release ”.

 

System Requirements


This section lists the system requirements for machine, Software, OS, Database and Browser.

Software Requirements

EM products require following software.

 

Java - JDK

Following JDK are supported:

  • JDK 7 (e.g. jdk1.7.0_79)

 

 

Application Server/

Jsp Container

Any Of:

  • Tomcat Ver. 7.0.79
  • Or Other equivalent

 

Web Services Runtime for WsGen

For API Plus, Generated Web Services

For (SOAP), Following J2EE is supported:

  • Java EE 7 Glassfish Server

For Microservices - REST, Following is supported:

  • Spring Boot, Spring REST

 

Browser

Latest Browsers:
Google Chrome
Mozilla Firefox

Database

MySQL 5.5+
MariaDB Latest

 

Recommended IDE to work with generated web services source files :

 

IDE

IntelliJ IDEA Community Edition 2018

 

 

 

Platforms Supported

 

 

Products are tested and validated on the following reference platforms:

 

Reference Platforms

 

Operating Environment

Software / Database

Windows 7

 

With

  • MySQL 5.5

CentOS 7 Linux

With

  • MariaDB 10

 

 

 

 

System Requirements for Database

Please refer to the database vendor supplied system requirement documentation.

Machine / Cloud Requirement

 

RAM 4GB, Storage 30GB

 

 

Installation / Setup Tasks

 

Download emSetup.zip from Download page ( Click Here For emSetup.zip )
then extract to folder e.g. E:\, then Follow instructions below:

 

-------------------------------------------------------
EasyManage Platform Setup
-------------------------------------------------------
Details: Setup EasyManage Platform On-premise Edition
and also API deployment setup
-------------------------------------------------------


[A] Pre-Requisites:

1] Install and setup Java 7 e.g. F:\ProgFiles\jdk1.7.0_79
2]
Download and setup Tomcat 7.0.x from link :
https://tomcat.apache.org/download-70.cgi
at dir below as CATALINA_BASE:
E:\emSetup\Platform\run\apache-tomcat-7.0.79

EasyManage provided tomcat conf files are in dir:
E:\emSetup\Platform\run\tomcat_files
Copy files (or replace content) from here to destination
E:\emSetup\Platform\run\apache-tomcat-7.0.79

Please Note:
- Edit E:\emSetup\Platform\run\tomcat_files\bin\setenv.bat to update your Java installed path
- Tomcat port is setup to 9080 as Spring Rest App will use 8080


3] Install and setup IntelliJ IDEA Community Edition 2018 at any location.
4] Install and setup MySQL ver 5.5 or above for database
(You can use latest MariaDB also, https://mariadb.org/download/)

-------------------------------------------------------
[B] Set-Up EasyManage Platform war
-------------------------------------------------------
- Download EMPlatTrial.zip from EasyManage Download page and extract at:
E:\emSetup\Platform\EMPlatTrial

- Create Database in mysql/mariadb, by following instructions in
E:\emSetup\Platform\EMPlatTrial\sql\mysql\Readme.txt
(Database url, user and password values will be used lateron in em_param file)

- Copy E:\emSetup\Platform\EMPlatTrial\emPlat.war
to dir E:\emSetup\Platform\run\apache-tomcat-7.0.79\webapps

Start tomcat and Check App running at URL:
http://127.0.0.1:9080/emPlat/

Now Shutdown tomcat, Edit em_param_conf files and re-start tomcat.
Edit file:
E:\emSetup\Platform\run\apache-tomcat-7.0.79\webapps\emPlat\WEB-INF\classes\em_param_en_US.properties

1) Verify/Set correct values for below in this file:
---------------------------------------------------------
em.db.mysql.url=jdbc:mysql://localhost:3306/EMADB?useUnicode=true&characterEncoding=utf8
em.db.mysql.user=emadb
em.db.mysql.password=emadb

em.param.file_dest_dir=E:\\emSetup\\Platform\\run\\em_files_mysql

em.param.em_user_su=<DEVELOPER1<

em.param.em_user_developer=<DEVELOPER1<
em.param.em_user_application=<DEVELOPER1<
em.param.em_user_selfapp=<DEVELOPER1<
em.param.em_user_apponly=<USER01<
em.param.em_user_advanced=<DEVELOPER1<
em.param.em_user_portal=
em.param.em_user_content=
---------------------------------------------------------


2) Enable and setup API License Configured USER-IDs as per your needs
---------------------------------------------------------
# API use: List of Usr-Id|Wp Id|Scr Id
em.param.em_api_usr_wp_scr=<USERID|1001|2001<USERID|1001|2002<
--------------------------------------------------------


-------------------------------------------------------
[C] Define APIs and Generate Code
-------------------------------------------------------
- Using EasyManage Platform App, Create your app and WP
- Generate Code For Web Services

-------------------------------------------------------
[B] Set-Up / Configure your APIs via Spring Rest project or other methods
-------------------------------------------------------
- Locate your generated web services (APIs) in dir
E:\emSetup\Platform\run\em_files_mysql
e.g.
E:\emSetup\Platform\run\em_files_mysql\WSGEN\MYTEMP01\WS_50120\

Then follow the instructions in below file to complete API setup :
E:\emSetup\Platform\EMPlatTrial\sdk\wsgen\README.txt

-------------------------------------------------------


Appendix A - Install/Set-Up Database

 

MySQL:

  • Install MySQL 5.0.x
  • Refer to Readme.txt in sql/mysql dir.
  • On Unix/Linux: set at least following options in /etc/my.cnf:

[mysqld]

lower_case_table_names=1

 

default-character-set=utf8

default-storage-engine=INNODB

sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

 

# max_connections=100

 

  • Further Configure and change MySQL settings by referring to provided sample my.ini file.
  • Create a database e.g. EMDB (Refer to details later on under Setup Database)
  • Note: Please select appropriate character set and collation if case sensitive searches are required.
  • Set-up/verify MySQL JDBC driver directory jar:

·        On Windows: e.g. at E:\ProgFiles\ jdbc_drivers\mysql5\mysql-connector-java-5.0.7-bin.jar

·        On Unix: e.g. at /MySQL/mysql-connector-java-5.0.7

  • Add MySQL JDBC driver classes to CLASSPATH for your container:

·        set CLASSPATH= %CLASSPATH%;E:\ProgFiles\ jdbc_drivers\mysql5\mysql-connector-java-5.0.7-bin.jar;

 

 

 

Set-Up and Run EM Platform Java Batch Utilities

To run emutil java utility programs and batch programs:

   Add CLASSPATH to Java Util classes (in addition to J2EE JDK classpaths):

 

set TOMDIR=E:\Work_em_local\ProgFiles\apache-tomcat-7.0.79

 

set CLASSPATH=%TOMDIR%\webapps\em\WEB-INF\classes;%TOMDIR%\webapps\em\WEB-INF\lib\emlib.jar;E:\ProgFiles\jdbc_drivers\mysql5\mysql-connector-java-5.0.7-bin.jar;%JAVAEE_HOME%\lib\javaee.jar;

 

   Run the em util program, e.g.:

  java emutil.EjUser_stat %

 

 

 

Test the installation


Open the client browser window.
Enter following URL Address (Pls note port - if not updated is 8080):
http://127.0.0.0:9080/em
 

 

Installing EM License

 

EM License (EmLicense.class): Using, Applying, Upgrading:

EM License is supplied in a java class file named ‘EmLicense.class’. The License is pre-marked for a particular product build and with a unique License Id. Interchanging License file with other environments and releases, than those it has been marked for, is not allowed and is not compatible.

 

To upgrade or to apply the new License received, please follow these steps:

 

  • Back-up old EmLicense.class file, located under ‘em\WEB-INF\classes\emlic’ dir.
  • Replace it with the supplied new EmLicense.class file.
  • Stop and re-start the JSP container server.
  • Sign-Up/Sign-In with new User Id, Verify the license message on server log window for correctness.

 

 

 

Chapter 2: EM Platform Configuration Parameters


This section describes configuration parameters for EM 5.0 Server.

 

 

How to use EM Configuration Parameters?

 

  • EM Configuration Parameters file contains configurable parameters for EM 5.0 software.
  • EM Configuration Parameters file contains Instance (Site) and User specific configurable parameters.
  • Configuration parameters file is at:  emv50\em\beans\em\em_param_en_US.properties
  • Values take effect at next JSP Container Server Start-up.
  • Note: For comments use '#' in beginning of line
  • This file can be overridden by a specific file for a “Plan” or “User”. Please refer to “User Guide: Appendix A: Administrator Information” for details.

 

Database JDBC drivers supported are (not changeable):

  • Oracle: em.db.oracle.driver=oracle.jdbc.driver.OracleDriver
  • Mssql : em.db.mssql.driver=sun.jdbc.odbc.JdbcOdbcDriver
  • Access: em.db.access.driver=sun.jdbc.odbc.JdbcOdbcDriver

 

 

Parameter List

 

em.db.<database>.url

em.db.<database>.user

em.db.<database>.password

em.param.em_db_type

em.param.em_mail_out

em.param.em_mail_in

em.param.records_per_form

em.param.da_records_per_form

em.param.max_records_per_form

em.param.file_upload_size_kb

em.param.file_download_size_kb

em.param.file_dest

em.param.file_dest_dir

em.param.max_table_fields

em.param.max_table_keys

em.param.max_query_lines

em.param.style_class_ids

em.param.data_owner_change

em.param.em_user_lkup

em.param.em_user_da

em.param.em_user_developer

em.param.em_user_application

em.param.em_user_selfapp

em.param.em_user_apponly

em.param.em_user_advanced

em.param.em_user_portal

em.param.em_user_content

em.param.em_user_appsu

em.param.em_user_su

em.param.em_tg_<AppId|ALL>

em.param.em_tg_tagp_<AppId|ALL>

em.param.em_tg_ext_<AppId|ALL>

em.param.em_block_users_apps

 

Optional Parameters:

em.param.em_dur_def_si_timeout

em.param.em_easy_qry_form

em.param.max_records_sql_limits

em.param.em_app_mail

em.param.em_seq_id_grp

em.param.em_enable_cust_html

em.param.em_disp_htmlObj

em.param.em_check_si_dur_days

em.param.em_tp_sharing_enable

em.param.em_tp_sharing_code

em.param.em_sem_tags_enable

 

 

Parameter Usage, Defaults, Optimum Values

 

em.db.<database>.<param>:

 

Database Details:

  • Specify url, database user id and password for connecting to database.
  • Oracle url consists of:Db Server IP Address:Listener Port:Database SID
  • MS SQL Server and MS Access URL consists of:Odbc Data (System) Source Name

 

em.db.oracle.url=jdbc:oracle:thin:@127.0.0.1:1521:ORA10G

em.db.oracle.user=jspuser

em.db.oracle.password=jsppass

 

em.db.mssql.url=jdbc:sqlserver://localhost:1433;databaseName=EMDB;

#em.db.mssql.url=jdbc:odbc:EMDB

em.db.mssql.user=jspuser

em.db.mssql.password=jsppass

 

em.db.access.url=jdbc:odbc:EMADB

em.db.access.user=jspuser

em.db.access.password=jsppass

 

em.db.mysql.url=jdbc:mysql://localhost:3306/EMDB

em.db.mysql.user=emdb

em.db.mysql.password=emdb

 

em.db.db2.url=jdbc:db2:EMDB

em.db.db2.user=emdb

em.db.db2.password=emdb

 

em.db.sybase.url=jdbc:sybase:Tds:localhost:5000/EMDB

em.db.sybase.user=emdb

em.db.sybase.password=emdb

 

 

em.param.em_db_type:

  • Sets the database type if multiple db allowed in lic.
  • Set to one of: default|oracle|mssql|access

 

em.param.em_db_type=default

 

em.param.em_mail_out:

  • Outgoing Mail server protocol, host, port (blank=default) for use by EM Mail.

 

em.param.em_mail_out=<smtp<127.0.0.1<<

 

em.param.em_mail_in:

  • Incoming Mail server protocol, host, port (blank=default) for use by EM Mail

 

em.param.em_mail_in=<pop3<127.0.0.1<<

 

em.param.records_per_form:

  • Limits no of records displayed per form
  • 0=No Limit, Optimum value 10

 

em.param.records_per_form=10

 

em.param.da_records_per_form:

  • In Direct Access Mode, Limits no of records displayed per form
  • 0=No Limit, Optimum value 100

 

em.param.da_records_per_form=100

 

em.param.max_records_per_form:

  • Max no of records up to which [da_]records_per_form or da_records_per_form value can be tweaked using [{RECNo-nn-RECNO]} form token
  • 0=No Max Limit, Optimum value = 20

 

em.param.max_records_per_form=20

 

em.param.file_upload_size_kb:

  • Maximum File size in KB for Upload
  • 0=Disable File Upload, Optimum value 200

 

em.param.file_upload_size_kb=2048

 

em.param.file_download_size_kb:

  • Maximum File size in KB for download
  • 0=Disable File Download, Optimum value 200

 

em.param.file_download_size_kb=2048

 

em.param.file_dest:

  • File storage destination: Db or Disk
  • 1=Database, 2=Disk, If set to 2, specify file_dest_dir also

 

em.param.file_dest=1

 

em.param.file_dest_dir:

  • File storage directory on disk, Used when file_dest=2 and for custom My Menu files
  • On Windows: Use '\\' instead of '\', as in D:\\em_dir\\em_files
  • On Unix: Use '/', as in /user/home/em_dir/em_files

 

em.param.file_dest_dir=D:\\tmp\\em_files

 

em.param.max_table_fields:

  • Max. No of fields in tables
  • Used only when specific such license is issued...
  • 0=Disable Fields, Optimum value 20 (on windows)

 

em.param.max_table_fields=40

 

em.param.max_table_keys:

  • Max. No of keys for a table
  • Used only when specific such license is issued...
  • 0=Disable Keys, Optimum value 5

 

em.param.max_table_keys=5

 

em.param.max_query_lines:

  • Max. No of query lines on query form
  • Used only when specific such license is issued...
  • 0=Disable Query, Optimum value 5

 

em.param.max_query_lines=5

 

em.param.style_class_ids:

  • Put html style sheet class ids in tags
  • 0=No, 1=Yes

 

em.param.style_class_ids=1

 

em.param.data_owner_change:

  • Enable data record ownership changes
  • 0=No, 1=App User (DataRec Owner), 2=Data Group

 

em.param.data_owner_change=2

 

em.param.em_user_lkup:

  • Application Look-Up allowed "<User Id:Tbl Id:Mode<"
  • Used for Look Up table access. e.g. <DEMO:10010:[C|M]<DEMO:10015:[C|M]<
  • where C=Combined with receiver User Id, M=Master Only
  • i.e <DEMO:10010:C<DEMO:10015:M<
  • OR, <DEMO:0:M< , zero means for all tbls

 

em.param.em_user_lkup=<Student:10043:C<Student:0:C<

 

em.param.em_user_da:

  • Allowed “Table DirectAccess” User Ids
  • e.g. "<DEMO<CONSUMER<" , used for viewing table data without user id, val id checks

 

em.param.em_user_da=<DEMO<John<

 

em.param.em_user_<User Type>:

  • Validates Licensed User Ids as
  • below, when specific such license is issued...
  • Use "<" to separate each Id, at begin and end. e.g. <DEMO1<DEMO2<

 

em.param.em_user_developer=

em.param.em_user_application=

em.param.em_user_selfapp=

em.param.em_user_apponly=<DEMO1<DEMO2<

em.param.em_user_advanced=<DEMO<CONSUMER<

em.param.em_user_portal=

em.param.em_user_content=

 

em.param.em_user_su:

  • EM Superuser (Administrator)- User Id
  • Authorized to run online administration functions remotely from browser
  • e.g. batch jobs, Can define application access security, data groups, etc.

 

em.param.em_user_su=<DEMO<PortalSecurity<

 

Reserved For Future Use:

em.param.em_user_appsu:

  • Application Superuser - User Id
  • Used for reverse navigations of all discrete inbox data by App SU
  • # em.param.em_user_appsu=DEMO

 

em.param.em_tg_<AppId>:

  • Define tagging parameters for given App User Id
  • >isTG>isTG_EUT>SessionSettings><GT_M<GT_O<EU_T<>
  • Where Session Settings == <Disp GT_M<Disp GT_O<Disp EUT<
  • And User Lists e.g. GT_M == [*|Usr1:attr[Usr2:attr[Usr3:attr[
  • Where, '*' = all users, attr = YYYYYYYYYYYYYYY

 

 

em.param.em_tg_DEMO=>1>0><1<1<1<><[:CONSUMER:YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY:[:John:YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY:[<[:TEST:YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY:[:Student:YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY:[<[:CONSUMER:YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY:[:DEMO:YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY:[<>

 

em.param.em_tg_tagp_DEMO=<[(LR(|1|Agreement|1|1|||||(|3^Agree||4^DisAgree||5^Neutral||([(L1(|7|Approvals|1|1|S||||(|8^Approve||9^Reject||([(LM(|30|Action|1|1|M|3|||(|32^Accepted||33^In Process||34^Forwarded||35^Need Info||36^Need Enhancement||37^Invalid||([(L1(|50|Preference|1|1|B||||(|52^Like It||53^Do Not Like||([(L1(|55|Rating|1|1|||||(|56^Excellent||57^Good||58^Average||59^Needs Improvement||60^Unsatisfactory||([(LF(|80|Provide Feedback|1|1|100|15|||(|82^Price Wish||83^Preferred Color||([(LV(|90|Vote For This Rec|1|1|C|92|||(|92^Vote Yes||93^Vote No||([(LV(|100|Vote My Preferred Color|1|1|R||||(|102^Red||103^Blue||104^Metallic||([<<[(IC(|200|Icon Group|1|1|||||(|202^I1001||203^I1002||([<

 

 

em.param.em_block_users_apps:

  • Define apps that allow blocking users
  • E.g. User1 using this app can block User2 so that User2 will not be able to see records created or last updated by User1

 

em.param.em_block_users_apps=<DEMO<CONSUMER<PortalSecurity<

 

Optional Parameters:

# --------------------------------------------------------------------------------------

 

# em.param.em_dur_def_si_timeout [30]: In minutes -

#        Default SignIn timeout duration from last activity

em.param.em_dur_def_si_timeout=120

 

# em.param.em_easy_qry_form [0]: 0=No, 1=enable easy keywords in table qry form.

em.param.em_easy_qry_form=1

 

# em.param.max_records_sql_limits [0]: Max no of records fetched in sql qry

# 0=No Max Limit, Optimum value = 1000, -1=Disable : <enable_hvy_qry[1|0]<TblQry<PwrSrhDv<UsrSrh<PwrSrhOther<MultAppSrh<PSrh<CSrh<ColSrh<Othr<

em.param.max_records_sql_limits=<1<1000<1000<100<0<0<0<0<0<0<

 

# em.param.em_app_mail : <DisableFILE_MailComp<DisableFILE_MailImp<NotImpl:DisableFILE_Collab<fill1<fill2<

#        0=No, 1=disable

em.param.em_app_mail=<0<0<0<0<0<

 

# em.param.em_seq_id_grp : For Odbc Sequence Id Table Group Suffix

em.param.em_seq_id_grp=

 

# em.param.em_enable_cust_html [0]: <FormProp<WP_Exec<My_Menu<Uploaded App Help Files<ProfilePublic<fill1<

#        0=No, (1+)=yes : 1=yes Safe Html + HREFs, 2= +images, 3= +iframe tags, 4= +videos/audio, xml data / OBJECT / embed tags, 5= +script tag

em.param.em_enable_cust_html=<2<2<2<1<1<0<

 

# em.param.em_disp_htmlObj : <DispHtmlObjForFileStream<DispHtmlObjForHyLnk<DispHtmlObjForText<DispTextHtmlEditor<DispDatePicker<filler<

#        For DispHtmlObjForFileStream , DispHtmlObjForHyLnk :

#        0=No, (1+)=yes : 1=yes images/code/text win, 2= videos/audio, 3= enable iframe tag, 4= enable OBJECT / embed tag as well

#        For DispHtmlObjForText :

#        0=No, (1+)=yes : 1=yes Safe Html + HREFs, 2= +images, 3= +iframe tags, 4= +videos/audio, xml data / OBJECT / embed tags, 5= +script tag

#        For DispTextHtmlEditor , DispDatePicker :

#        0=No, 1=yes

em.param.em_disp_htmlObj=<2<2<2<1<1<0<

 

# em.param.em_check_si_dur_days [0] : If enabled, Permitt User Si as per setting

# 0=No Check, >=1 : allow Si if user's CL_AUTH_DATE is > than today ,

#                   OR if user's create date is >  (Today - em_check_si_dur_days)

em.param.em_check_si_dur_days=0

 

# em.param.em_tp_sharing_enable [0]: 0=No, 1=enable sharing / publishing to third party sites like facebook

em.param.em_tp_sharing_enable=1

em.param.em_tp_sharing_code= \

<!-- AddThis Button BEGIN --> \n \

<div class="addthis_toolbox addthis_default_style " style="float: right;" \n \

  EMURL \n \

  EMTITLE \n \

  EMDESC \n \

> \n \

<a class="addthis_button_preferred_1"></a> \n \

<a class="addthis_button_preferred_2"></a> \n \

<a class="addthis_button_preferred_3"></a> \n \

<a class="addthis_button_preferred_4"></a> \n \

<a class="addthis_button_compact"></a> \n \

<a class="addthis_counter addthis_bubble_style"></a> \n \

</div> \n \

<script type="text/javascript">var addthis_config = {"data_track_clickback":true};</script> \n \

<script type="text/javascript" src="http://s7.addthis.com/js/250/addthis_widget.js#pubid=YourPubIdOnAddThis"></script> \n \

<!-- AddThis Button END --> 

 

# optinal custom values

# <div class="addthis_toolbox addthis_default_style " \n \

# addthis:url="EMURL"       \n \

# addthis:title="EMTITLE"        \n \

# addthis:description="EMDESC" \n \

# > \n \

 

 

# em.param.em_sem_tags_enable [0]: 0=No, 1=enable semantic tags in display

em.param.em_sem_tags_enable=1

 

# --------------------------------------------------------------------------------------

 

Note: After making any changes re-start the JSP Container for new values to take effect.

 

How to use Plan or User specific EM Configuration Parameters?

 

 

Order of reading file is as below (Keep looking in next file till parameter is found):

  • User specific File.
  • Plan specific File.
  • Default system file.

 

 

The user property is specified as a string with parts mentioned below:

<CL_PARAM_FLG<CL_PARAM_VAL<CL_PARAM_CONF_FLG<CL_PARAM_CONF_VAL<

Where:

CL_PARAM_FLG =

          Values "" : Default, | "UserPlan" : UserFile then Plan File | "Plan" | "User"

e.g. "Plan" will look for: em_param_<PlanName>_en_US.properties

 

          CL_PARAM_VAL  = ‘PlanName|User Id’

          CL_PARAM_CONF_FLG = same as CL_PARAM_FLG

          CL_PARAM_CONF_VAL = ‘PlanName|User Id’

e.g. "Plan" will look for: em_param_conf_<PlanName>_en_US.properties

 

Usage scenarios:

   e.g.  "<New Prop>" = <UserPlan<|Plan25|DEMO|<<<

   e.g.  "<New Prop>" = <Plan<|Plan10||<<<

   e.g.  "<New Prop>" = <User<||CONSUMER|<<<

 

Example usage scenario: Assign “Plan10” to user ‘DEMO’, and user file ‘DEMO10’ as well.

 

E:\>java emutil.EjUser_prop

Needs User parameters eg. ...

java <program> "User Id"

java <program> "User Id" "User Sec Id" "UpdateProp" "<New Prop>"

   Where "<New Prop>" = "<em_param flag<em_param value<em_param_conf flag<em_par

am_conf value<"

   e.g.  "<New Prop>" = <UserPlan<|Plan25|DEMO|<<<

   e.g.  "<New Prop>" = <Plan<|Plan10||<<<

   e.g.  "<New Prop>" = <User<||CONSUMER|<<<

 

E:\>java emutil.EjUser_prop DEMO

03/07/2011 03:33:24.135 PM IST Mon :   <<  make db conn [mysql 30100 jdbc:mysql:

//localhost:3306/EMDB?useUnicode=true&characterEncoding=utf8]

----------------------------------------------------------------

Parameters Received: DEMO, , , ,

----------------------------------------------------------------

User                -Status    -User Sec Id   -[E-Mail, Updated]

----------------------------------------------------------------

 

DEMO VALID 10002 [<UserPlan<|Plan10|DEMO10|<<<]

-----------------Over-------------------------------------------

 

03/07/2011 03:33:24.166 PM IST Mon :     >>clse db conn

 

E:\>java emutil.EjUser_prop DEMO 10002 UpdateProp "<UserPlan<|Plan10|DEMO10|<<<"

03/07/2011 03:33:41.088 PM IST Mon :   <<  make db conn [mysql 30100 jdbc:mysql:

//localhost:3306/EMDB?useUnicode=true&characterEncoding=utf8]

----------------------------------------------------------------

Parameters Received: DEMO, 10002, UpdateProp, <UserPlan<|Plan10|DEMO10|<<<,

----------------------------------------------------------------

User                -Status    -User Sec Id   -[E-Mail, Updated]

----------------------------------------------------------------

 

DEMO VALID 10002 [<UserPlan<|Plan10|DEMO10|<<<]

 

----------------------------------------------------------------

Database Updated:

        User        = DEMO

        User Sec Id = 10002

        New Prop  = <UserPlan<|Plan10|DEMO10|<<<

 

Table: EM_USER          Updated Records: 1

 

----------------------------------------------------------------

 

Table: EM_USER  *** Updated WHERE PARENT USER Records: 3

-----------------Over-------------------------------------------

 

03/07/2011 03:33:41.166 PM IST Mon :     >>clse db conn

 

Note: All the EM Mail and Collaboration Ids (EMMAIL9999 / EMAPP 9999) created by user also get the User property assigned.

 

 

Which Parameters can be override via Plan / User files?

 

  • Following configurable parameters can be overridden from Plan or User files:

 

em.param.em_mail_out

em.param.em_mail_in

em.param.em_mail_param

 

em.param.records_per_form

em.param.da_records_per_form

em.param.em_user_da

 

em.param.max_records_per_form

 

em.param.file_upload_size_kb

em.param.file_download_size_kb

 

em.param.em_block_users_apps (Default set to ALL)

 

em.param.em_easy_qry_form

em.param.em_app_mail

 

em.param.em_tg_<AppId|ALL>

em.param.em_tg_tagp_<AppId|ALL>

em.param.em_tg_ext_<AppId|ALL>

 

em.param.em_enable_cust_html (Excluding WP_Exec parts)

em.param.em_disp_htmlObj

 

em.param.em_check_si_dur_days

 

Chapter 3: Java Utility Programs, Batch Jobs


This section describes EM supplied java utility programs and batch jobs that can be run from Windows Command or MS-DOS prompt.

 

List of Java Utility Programs

 

Following is the list of java utility classes present in emclasses.jar, their names begin with “Ej”. They are in package “emutil” :

 

EjCateg_tot_rep.class

EjCtgTree.class

EjSeq_id.class

EjSql.class

EjTable_ad_rep.class

EjTable_ln_data_rep.class

EjTable_data_cln.class

EjTable_data_arccln.class

EjTable_data_delcln.class

EjTable_tot_rep.class

EjUser_remove.class

EjUser_set_pref.class

EjUser_stat.class

EjUser_IdChg.class

EjUser_tbl_set_pref.class

EjUser_tsh_cln.class

EjSql_AccCrTbl.class

EjUser_passwd.class

EjLicInfo.class

 

 

 

Running Java Utility Programs

 

The utility programs are in package “emutil”, Please run them as below:

 

java emutil.EjCateg_tot_rep

 

 

Using Java Utility Programs, Examples

 

Following section describes usage, shows examples of using these utility programs and parameters required:

 

 

EjCateg_tot_rep.class:

Reports total number of categories by category type for every EM User ID in database.

 

D:\emv50>java emutil.EjCateg_tot_rep

Needs User parameters eg. ...

java <program> "User Id"

 

D:\emv50>java emutil.EjCateg_tot_rep %

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

User Id Category Type   Total

-------------------------------------------------------------

 

DEMO    tbl             [ 4 ]

DEMO    txt             [ 4 ]

DEMO    wpj             [ 3 ]

DEMOUSR txt             [ 3 ]

------------Over------------

 

    >>clse db conn

 

EjCtgTree.class:

Displays or Populates Category Tree structure for ODBC database types, used by Inbox to display Tree.

 

D:\emv50>java emutil.EjCtgTree

Needs User parameters eg. ...

java <program> "User Id" "Categ Id"

java <program> "User Id" "Categ Id" "ReGenerate"

 

D:\emv50>java EjCtgTree DEMO 200

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

CL_USER - CL_CATEG_ID - CL_PARENT_CATEG_ID - CL_CATEG_TYPE - CL_TREE_STR

-----------------------------------------------------------------------

DEMO 10072 200 wpj 200:1:

DEMO 10070 200 tbl 200:2:

DEMO 10069 200 tbl 200:3:

DEMO 10066 200 tbl 200:4:

DEMO 205 200 txt 200:5:

DEMO 10077 205 tbl 200:5:1:

    >>clse db conn

 

 

 

EjSeq_id.class:

Displays Sequence Ids used for generating unique numbers for categories, tables, fields, etc.

  • If using “Reset” also specify New value to reset to.
  • Do not use “ALL” with Reset otherwise all Sequences will be reset to value specified.
  • Oracle: Each call to EjSeq_id will waste the sequence number, this is database limitation.

 

D:\emv50>java emutil.EjSeq_id

Needs User parameters eg. ...

java <program>

java <program> "<Sequence>"

java <program> "<Sequence>" "Reset" "<New Value>"

  Where: "<Sequence>"=[ALL|USER|FIELD|CATEG|FORM|QRY|WP|SCREEN|VAL]

 

D:\emv50>java EjSeq_id ALL

----------------------------------------------------------------

Parameters Received: ALL, , ,

----------------------------------------------------------------

Sequence          -[ Current Db Value ]

----------------------------------------------------------------

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

 

USER             [ 1026 ]

FIELD            [ 10148 ]

CATEG            [ 10077 ]

FORM             [ 10014 ]

QRY              [ 10017 ]

WP               [ 10006 ]

SCREEN           [ 10011 ]

VAL              [ 10042 ]

-----------------Over-------------------------------------------

    >>clse db conn

 

D:\emv50>java EjSeq_id USER Reset 1030

----------------------------------------------------------------

Parameters Received: USER, Reset, 1030,

----------------------------------------------------------------

Sequence          -[ Current Db Value ]

----------------------------------------------------------------

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

 

USER             [ 1026 ]

----------------------------------------------------------------

Database Updated:

        Seq        = USER

        New Val    = 1030

 

Updated Records: 1

-----------------Over-------------------------------------------

    >>clse db conn

 

 

EjSql.class:

Utility class to check database type and connection status, connects and displays only 1 User ID record from database, evenif there are more.

 

D:\emv50>java emutil.EjSql

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

DEMO

    >>clse db conn

 

EjTable_ad_rep.class:

Reports for each user, table id, table name: number of archived and deleted records.

 

D:\emv50>java emutil.EjTable_ad_rep

Needs User parameters eg. ...

java <program> "User Id"

 

D:\emv50>java emutil.EjTable_ad_rep %

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

User Id Table Id        Table Name              Total

-------------------------------------------------------------

 

DEMO    10066   "Address Book"  [Archived = 1 ]

DEMO    10066   "Address Book"  [Deleted  = 1 ]

DEMO    10070   "employee"      [Deleted  = 1 ]

------------Over------------

 

    >>clse db conn

 

EjTable_ln_data_rep.class:

Linked table data records report. Reports for each user, linked table id, table name: number of total, archived, deleted, valid, in accessible total and in accessible detail records.

NOTE: In accessible detail records may/will appear for more than one table Id for the given User Id.

 

D:\emv50>java emutil.EjTable_ln_data_rep

Usage: java <program> <User Id> <Table Name>

Reporting: <User Id=ALL> <Table Name=ALL>

  <<  make db conn [access 20100 jdbc:odbc:EMADB]

 EM Table Linked : Actual Physical Table Data Report:      

---------------------------------------------------------------

Table Name  Tbl Id      User  [Db Prop / Db Ops]

---------------------------------------------------------------

  <<  make db conn [access 20100 jdbc:odbc:EMADB]

---------------------------------------------------------------

tblall_upd      10039   DEMO    [ / ]

          [ Total Records  = 384 ]

          [ Deleted = 382 ]

          [ Archived = 0 ]

          [ Valid = 2 ]

          [ In Accessible Total = 0 ]

---------------------------------------------------------------

tblall_upd_New    10040 DEMO  [ / ]

        [ Total Records  = 10 ]

        [ Deleted = 0 ]

        [ Archived = 0 ]

        [ Valid = 9 ]

        [ In Accessible Total = 1 ]

  In Accessible Rec # 10761     [ (Detail) 0 ]

    >>clse db conn

------------Over------------

    >>clse db conn

 

e.g. showing running report for a specific User and table name wild card search:

 

D:\emv50>java emutil.EjTable_ln_data_rep DEMO tblall_upd_N

  <<  make db conn [access 20100 jdbc:odbc:EMADB]

Reporting user ids like: [DEMO%]

Reporting table names like: [tblall_upd_N%]

 EM Table Linked : Actual Physical Table Data Report:      

---------------------------------------------------------------

Table Name  Tbl Id      User  [Db Prop / Db Ops]

---------------------------------------------------------------

  <<  make db conn [access 20100 jdbc:odbc:EMADB]

---------------------------------------------------------------

tblall_upd_New    10040 DEMO  [ / ]

        [ Total Records  = 10 ]

        [ Deleted = 0 ]

        [ Archived = 0 ]

        [ Valid = 9 ]

        [ In Accessible Total = 1 ]

  In Accessible Rec # 10761     [ (Detail) 0 ]

    >>clse db conn

------------Over------------

    >>clse db conn

 

EjTable_data_cln.class:

Header class used by EjTable_data_arccln.class and  EjTable_data_delcln.class. WILL  NOT RUN!

 

D:\emv50>java emutil.EjTable_data_cln

Exception in thread "main" java.lang.NoSuchMethodError: main

 

EjTable_data_arccln.class:

Batch job program to Clean-Up Archived data records for all users.

CAUTION: Will actually completely remove (i.e. physically deletes) data records from EM Tables My Table and physical tables.

CAUTION: This program does not take back-up of archived data records. Make sure Archived data is extracted and backed-up from database before running this job.

 

D:\emv50>java emutil.EjTable_data_arccln

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

Em Job Data Clean-Up: Deleted/Archived Flag = 1

-------------------------------------------------------------

 

Table: CHAR     Records: 11

Table: NUM      Records: 0

Table: FLT      Records: 0

Table: BOOL     Records: 0

Table: TEXT     Records: 0

Table: TEXTS    Records: 1

Table: DATE     Records: 1

Table: BLOB     Records: 1

Table: CLOB     Records: 0

[Info about physical table deletes here…]

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

Physical Table: tblall_upd (User:DEMO, Tbl Id:10039)    Records: 2

    >>clse db conn

Table: EM_USER_DATA,    Records: 3

 

    >>clse db conn

 

EjTable_data_delcln.class:

Batch job program to permanently Clean-Up Deleted data records for all users. CAUTION: Will actually completely remove (i.e. physically deletes) data records from EM Tables My Table and physical tables.

Recommended to run at least twice a week.

 

D:\emv50>java emutil.EjTable_data_delcln

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

Em Job Data Clean-Up: Deleted/Archived Flag = 0

-------------------------------------------------------------

 

Table: CHAR     Records: 14

Table: NUM      Records: 1

Table: FLT      Records: 2

Table: BOOL     Records: 0

Table: TEXT     Records: 0

Table: TEXTS    Records: 1

Table: DATE     Records: 2

Table: BLOB     Records: 1

Table: CLOB     Records: 0

[Info about physical table deletes here…]

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

Physical Table: tblall_upd (User:DEMO, Tbl Id:10039)    Records: 382

    >>clse db conn

Table: EM_USER_DATA,    Records: 384

 

    >>clse db conn

 

EjTable_tot_rep.class:

Reports for each user, table id, table name: number of total data records (excluding archived and deleted).

 

D:\emv50>java emutil.EjTable_tot_rep

Needs User parameters eg. ...

java <program> "User Id"

 

D:\emv50>java emutil.EjTable_tot_rep %

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

User Id Table Id        Table Name              Total

-------------------------------------------------------------

 

DEMO    10077   "Address Book"  [ 1 ]

DEMO    10066   "Address Book"  [ 3 ]

DEMO    10070   "employee"      [ 8 ]

DEMO    10069   "tt"    [ 5 ]

------------Over------------

    >>clse db conn

 

EjUser_remove.class:

Utility program to remove an EM User and all associated data from database. The User ID to be removed MUST be marked for removal by program EjUser_Stat first.

 

D:\emv50>java emutil.EjUser_remove

Needs User parameters eg. ...

java <program> "User Id" "User Sec Id" "RemoveGoAhead"

        Warning: This program deletes all data associated with given User Id

 

EjUser_set_pref.class:

Utility program to define User’s EM table to use particular list of group of EM System tables. Although prefixed the program implementation will be available in next release.

 

D:\emv50>java emutil.EjUser_set_pref

Needs User parameters eg. ...

java <program> "User Id"

java <program> "User Id" "User Sec Id" "Prefix List"

  Where: "Prefix List"=[One or more prefix separated by comma, "NULL"=Reset to blank] e.g. "EM_GRP1,EM_GRP2"

 

EjUser_stat.class:

Utility program to query on and display status of EM User Id.

  • For displaying all users use ‘%’.
  • New Status parameter values and their usage is as below:
  • Disable: Disable user from using the EM 5.0.
  • Enable: Enable user for using the EM 5.0.
  • UnRegister: Will disable and UnRegister an User ID. The User will get a message accordingly. However the User ID is present in database andcan not be re-used.
  • Remove: Mark user ID for removal from database. Subsequently Run EjUser_remove to actually remove the user Id and data.

 

 

D:\emv50>java emutil.EjUser_stat

Needs User parameters eg. ...

java <program> "User Id"

java <program> "User Id" "Sorting Option" "User Sec Id" "New Status"

               Where: "Sorting Option"= [Def/IdUp/IdDown/ CreatedDown/ UpdatedDown]

 

               Where: "New Status"=[Disable/Enable/UnRegister/Remove]

 

D:\emv50>java emutil.EjUser_stat DEMO

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

----------------------------------------------------------------

Parameters Received: DEMO, , ,

----------------------------------------------------------------

User                -Status    -User Sec Id   -[E-Mail, Updated]

----------------------------------------------------------------

DEMO VALID 1021 [demo@demo.demo, 2002-08-12 14:26:20]

DEMOUSR VALID 1024 [demousr@d.d, 2002-08-12 14:24:35]

-----------------Over-------------------------------------------

    >>clse db conn

 

D:\emv50>java emutil.EjUser_stat DEMOUSR Def 1024 Disable

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

----------------------------------------------------------------

Parameters Received: DEMOUSR, 1024, Disable,

----------------------------------------------------------------

User                -Status    -User Sec Id   -[E-Mail, Updated]

----------------------------------------------------------------

DEMOUSR VALID 1024 [demousr@d.d, 2002-08-12 14:24:35]

----------------------------------------------------------------

Database Updated:

        User        = DEMOUSR

        User Sec Id = 1024

        New Status  = DISABLED

 

Table: EM_USER          Updated Records: 1

-----------------Over-------------------------------------------

    >>clse db conn

 

D:\emv50>java emutil.EjUser_stat DEMOUSR

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

----------------------------------------------------------------

Parameters Received: DEMOUSR, , ,

----------------------------------------------------------------

User                -Status    -User Sec Id   -[E-Mail, Updated]

----------------------------------------------------------------

DEMOUSR DISABLED 1024 [demousr@d.d, 2002-09-06 00:55:07]

-----------------Over-------------------------------------------

    >>clse db conn

 

 

EjUser_IdChg.class:

Utility program to change a User Id to new one.

  • For displaying all users use ‘%’.

 

D:\emv50>java emutil.EjUser_IdChg

Needs User parameters eg. ...

java <program> "User Id"

java <program> "User Id" "User Sec Id" "New Id"

 

D:\emv50>java EjUser_IdChg DEMO 1004 NEW_DEMO

 

 

EjUser_tbl_set_pref.class:

Utility program to define EM table to use particular group of EM System tables. Although prefixed the program implementation will be available in next release.

 

D:\emv50>java emutil.EjUser_tbl_set_pref

Needs User parameters eg. ...

java <program> "User Id"

java <program> "User Id" "User Sec Id" "Table Id"

java <program> "User Id" "User Sec Id" "Table Id" "Prefix"

  Where: "Table Id"=[Valid Id of the Table, "0"=All Tables]

         "Prefix"=[One prefix to be assigned, "NULL"=Reset to blank] e.g. "EM_GRP1"

 

 

EjUser_tsh_cln.class:

Batch job program to permanently Clean-Up Trash Folder objects, categories, table, data records for all users. Recommended to run at least twice a week.

 

D:\emv50>java emutil.EjUser_tsh_cln

  <<  make db conn [odbc 20100 jdbc:odbc:EMAJSP]

Em Job Trash COMPLETE Clean-Up :

-------------------------------------------------------------

 

Table: EM_USER_CATEG_DET        Records: 0

Table: EM_USER_CATEG_SUB        Records: 0

Table: EM_USER_WEBPROJ  Records: 0

Table: EM_USER_FORMS    Records: 0

Table: EM_USER_TBLFK    Records: 0

Table: EM_USER_DATA     Records: 0

Table: EM_USER_FORMS_FLD        Records: 0

Table: EM_USER_QRY      Records: 0

Table: EM_FLD_VAL_CHAR  Records: 0

Table: EM_FLD_VAL_NUM   Records: 0

Table: EM_FLD_VAL_FLT   Records: 0

Table: EM_FLD_VAL_BOOL  Records: 0

Table: EM_FLD_VAL_TEXT  Records: 0

Table: EM_FLD_VAL_TEXTS Records: 0

Table: EM_FLD_VAL_DATE  Records: 0

Table: EM_FLD_VAL_BLOB  Records: 0

Table: EM_FLD_VAL_CLOB  Records: 0

Table: EM_FIELDS                Records: 0

 

-------------------------------------------------------------

Em Job Deleted Field COMPLETE Clean-Up :

-------------------------------------------------------------

 

Table: EM_USER_FORMS_FLD        Records: 6

Table: EM_USER_QRY      Records: 0

Table: EM_FLD_VAL_CHAR  Records: 1

Table: EM_FLD_VAL_NUM   Records: 0

Table: EM_FLD_VAL_FLT   Records: 0

Table: EM_FLD_VAL_BOOL  Records: 0

Table: EM_FLD_VAL_TEXT  Records: 0

Table: EM_FLD_VAL_TEXTS Records: 0

Table: EM_FLD_VAL_DATE  Records: 0

Table: EM_FLD_VAL_BLOB  Records: 0

Table: EM_FLD_VAL_CLOB  Records: 0

Table: EM_USER_CATEG_DET                Records: 2

Table: EM_FIELDS                Records: 2

 

    >>clse db conn

 

D:\emv50>

 

EjSql_AccCrTbl.class:

Batch job program to create SQL schema (tables, views, indexes) for MS Access database. To be run only once during installation. Uses the supplied special file emtbl_acc.sql (with commands delimited with “go”) for dropping and re-creating database tables.

WARNING: This program drops tables and re-creates them! PLEASE RUN IT WITH CAUTION.

 

 

D:\emv50>java emutil.EjSql_AccCrTbl

Needs parameters eg. ...

java <program> "CREATE" "<path>emtbl_acc.sql"

 

 

EjUser_passwd.class:

Utility program to reset password of EM User Id.

  • For displaying all users use ‘%’.
  • Old password is not required to reset to a new one.
  • Ask user to change the password to a secret one by sign-in and using “Options:Change Password” menu option.

 

D:\emv50>java emutil.EjUser_passwd

Needs User parameters eg. ...

java <program> "User Id"

java <program> "User Id" "User Sec Id" "ResetPassword" "<New Password>"

 

D:\emv50>java EjUser_passwd DEMO

  <<  make db conn [access 20100 jdbc:odbc:EMADB]

----------------------------------------------------------------

Parameters Received: DEMO, , , ,

----------------------------------------------------------------

User                -Status    -User Sec Id   -[E-Mail, Updated]

----------------------------------------------------------------

 

DEMO VALID 1002 [s@s.c, 2003-02-26 17:27:35]

-----------------Over-------------------------------------------

 

    >>clse db conn

 

D:\emv50> java emutil.EjUser_passwd DEMO 1002 ResetPassword guesswhat

  <<  make db conn [access 20100 jdbc:odbc:EMADB]

----------------------------------------------------------------

Parameters Received: DEMO, 1002, ResetPassword, guesswhat,

----------------------------------------------------------------

User                -Status    -User Sec Id   -[E-Mail, Updated]

----------------------------------------------------------------

 

DEMO VALID 1002 [s@s.c, 2003-04-08 11:25:51]

 

----------------------------------------------------------------

Database Updated:

        User        = DEMO

        User Sec Id = 1002

        New Password  = guesswhat

 

Table: EM_USER          Updated Records: 1

-----------------Over-------------------------------------------

 

    >>clse db conn

 

 

EjLicInfo.class:

Utility program to display License Information Details. It will display products licensed, edition, build information, database supported. The Licensee details and User ID’s licensed (as supplied in license and/or specified in configuration parameter file) are also displayed.

 

D:\emv50>java emutil.EjLicInfo

 

===== LICENSE INFORMATION   =========================================

    ** Product      : EMSTE50 - EM WebPlus Suite 5.0

                      With

                    : EMSVR50 - EM WebPlus Server 5.0

                    : EMSTD50 - EM WebPlus Studio 5.0

                    : EMCNT50 - EM WebPlus Content Mgmt 5.0

                    : EMPRT50 - EM WebPlus Portal 5.0

     

       Edition      : Standard Edition

    ** Build        : EM-A0520-200-020-500-P00-D103103

       Database     : access, Db No:20100

     

    ** Licensed To  : Organization/Company/Individual Name

       Location Id  : 1111111111

       License Desc : Trial License - Only for Evaluation or Demo purposes

       Lic. # Desc  : 2 Developers, 2 Apps,  5 AppOnly, 1 Portal, 1 Content

    ** Lic Expiry Dt: Wed Mar 31 00:00:00 GMT+05:30 2004

 

 ** Allow Setting (Table Fields, Keys, Query Lines) param values in Conf. file ? : Yes

** Allowed Database Connections: oracle mssql access (access is default)

 ** Db Conn set in Conf File (em.param.em_db_type) = default

===== LICENSED USER ID INFORMATION   ================================

----- [developer] User Ids: -----------------------------

Check User Id Licensed or Not ? : Yes

User Ids are                    : Supplied in License

Licensed Number Of User Ids     : 2

Valid User Ids detected are     :

<DEMO<CONSUMER<

 

----- [application] User Ids: -----------------------------

Check User Id Licensed or Not ? : Yes

User Ids are                    : Supplied in License

Licensed Number Of User Ids     : 2

Valid User Ids detected are     :

<DEMO<CONSUMER<

 

----- [selfapp] User Ids: -----------------------------

Check User Id Licensed or Not ? : Yes

User Ids are                    : Supplied in License

Licensed Number Of User Ids     : 2

Valid User Ids detected are     :

<DEMO<CONSUMER<

 

----- [apponly] User Ids: -----------------------------

Check User Id Licensed or Not ? : Yes

User Ids are                    : Supplied in License (+) Can be defined in Conf param file.

Licensed Number Of User Ids     : 5

Valid User Ids detected are     :

<DEMOAPPUSR<<DEMO1<DEMO2<

 

----- [advanced] User Ids: -----------------------------

Check User Id Licensed or Not ? : Yes

User Ids are                    : Supplied in License (+) Can be defined in Conf param file.

Licensed Number Of User Ids     : 2

Valid User Ids detected are     :

<DEMO<CONSUMER<

 

----- [portal] User Ids: -----------------------------

Check User Id Licensed or Not ? : Yes

User Ids are                    : Supplied in License

Licensed Number Of User Ids     : 1

Valid User Ids detected are     :

<DEMO<

 

----- [content] User Ids: -----------------------------

Check User Id Licensed or Not ? : Yes

User Ids are                    : Supplied in License

Licensed Number Of User Ids     : 1

Valid User Ids detected are     :

<DEMO<

 

=====================================================================

 

 

Chapter 4: Administering EM Platform


This chapter discusses various issues relating to administering EM Platform

 

 

Monitoring EM Platform Runtime Log

 

Check tomcat log dir. Any user problems can be tracked in these for any EM system error messages and warnings. Also monitor user access activities including sign-in, sign-out, failure on sign-in checks, etc.

 

Tomcat: environment allows options to keep log and it’s location specifications. Set-up the logging as per your needs and monitor the log file for above mentioned checks.

 

Monitoring em.param.file_dest_dir for Disk Space Usage

 

Monitor the EM Files location (em.param.file_dest_dir) supplied in EM Parameters file for disk space. It keeps the files for FILE datatype (if destination set to disk), Mail Composed files and User My Menu files. Especially Mail Compose/Uploaded Files can take lot of space based on User activity.

 

Monitoring Database (DBA’s Role)

 

The DBA or Administrator needs to monitor database for normal maintenance reasons. However when the EM Users are using advanced features like:

  • Linked RDBMS tables
  • SQL Post Process Triggers
  • SQL Display Modifiers
  • Import Objects (Database Tables)

the monitoring should be more vigilant as these powerful features, if used erroneously, can seriously affect database consistency or performance.

 

Please make sure that database permissions granted to the user id specified as “em.db.<dbtype>.user” in configuration file (em_param_en_US) are appropriate for your installation.

 

Running EM Batch Jobs

 

The Administrator needs to run periodically the maintenance batch jobs (java util classes discussed earlier), e.g.:

 

Twice a week:

Data Record Deleted Clean-Up

Trash complete Clean-up

 

Once a week:

Reports: No of categories, tables, data records, List of Users

 

As needed:

Extract, Back-Up Archived data records and Data Record Archives Clean-Up

 

 

Miscellaneous Issues

 

Internationalization Settings

For internationalization of OS, database, desktops, Web Server, Please follow the relevant OS, database documentation for configuring language, character sets, etc. Use EM 5.0 Profile screen to choose appropriate formats. The Java programs and browser will support the international character sets as per the international configurations of OS or desktops they are running from.

 

Customizing EM Platform

You can customize Looks and feel and other functions as supplied in Options (User Profiles, etc), EM Configuration Parameters.

 

Advanced SQL (Post Process, Modifiers): If using these you need access to DBA. We do not support the actual usage issues except when they relate to underlying problems in provisions of our software product. Customizing EM Platform for one database type will restrict you to that database environment, unless migrated manually.

 

JSP customization: Changes to JSP files supplied, made by customers themselves, are not supported and can lead to: data in-consistency, security loopholes and or other problems.

 

Sizing and Scaling

The EM software product can be implemented in different Models. It can use:

Multiple Web Servers

Multiple Databases with User segregation

 

We advise you to seek consulting help from us for any advanced sizing and scaling issues.

 

Contacting Support

Software support provided depends upon the type of License and Support purchased by customer. When provisioned, for any software installation, use or other issues please contact the re-seller or if purchased from EasyManage.com, then via email at:  support@easymanage.com.

 

Please supply your contact information, description of the issue with log details, screen captures, etc as relevant.

 

 

Chapter 5: Migrating From Previous Platform Release


CAUTION: Previous release database schema will not work with new Release, it needs to be upgraded first!

 

When Migrating from previous Release to new Release, specific tasks need to be performed. Following consideration is desired:

·        Always fully back-up the previously installed versions, databases, work and user stored files, etc before installing new versions.

·        Perform the migration in off-line mode i.e. after shutting down application servers, databases completely.

·        Since new Release will use database schema enhancements, the previous Release database schema will not work with it, so it needs to be upgraded to work with new release.

·        For further assistance please email to support@easymanage.com.

 

 


Table Of Contents

 

EasyManage Platform : Quickstart Guide
Copyright © 2019 EasyManage.com All Rights Reserved.