OZ e-Form Developer
  • OZ e-Form Concepts
  • 🌈e-Form DEVELOPER
    • Day 1: Welcome On Board
      • About Course
      • Preparations
      • OZ e-Form Overview
    • Day 2: e-Form Design
      • Designer Environments
      • e-Form Layout Structure
      • e-Form Components
      • e-Form From Documents
      • Preview / Export / Save
      • Hands-on Practice
    • Day 3: Dynamic e-Form
      • e-Form Scripting Guide
      • Hands-on Practice
      • Advanced Features
    • Day 4: e-Form Application
      • Server Deployment
      • Viewer In HTML
      • Viewer APIs
      • Prefilling e-Form
      • Submitting e-Form
      • Sending MemoryStream
    • Get Your Certificate
    • Design Guide
      • Dialogue Flow
        • Overview
        • Creating Dialogue Flow
        • Uploading e-Form to Server
        • Running Dialogue Flow
        • Group and Statement
        • Custom Styling
      • Multilingual e-Form
      • Miscellaneous
      • Videosign
        • Videosign User Guide
      • OZ Verifier
        • OZ Verifier Introduction
        • Implementation and Use
        • Requirements
      • HTML5 Editor
        • HTML5 Editor Introduction
        • HTML Editor
        • Requirements and Sample
    • Day 5. Server & Reporting
  • 🌈Server Developer
    • OZ Server Console
    • OZ Scheduler
      • Features
      • Installing OZ Scheduler
      • Scheduler Task
    • Binding & Exporting
      • Overview
      • Export API Example
        • Extract Input Data
        • Export with OZ Server
        • Export with Scheduler
        • Export with Scheduler Task
    • Repository Server
    • Sync Server
      • Overview
      • Installing Sync-Server
        • SSL configration
      • Sample Application
      • Implementation
    • QR Link Mobile Sign
  • 🌈Report Developer
    • Overview
      • About Course
      • Preparation
      • Report Designer Overview
    • Query Design
      • Database Connection
      • Designer Environment
      • Dataset Design
    • Report Design
      • Designer Environment
      • Components
      • Table
      • Master-Detail
      • ODI Parameter
      • CrossTab
      • Chart
  • 🌈MOBILE DEVELOPER
    • Android Native
    • iOS Native
    • TOTO Framework
      • TOTO Overview
      • Sample App Overview
      • Server Application
      • Android Project
  • ⬇️Product Downloads
  • 📚 Product Documentation
  • 📕Technical Guide
  • ⚛️ ReactJS Integration
Powered by GitBook
On this page
  • Types of OZ Repository
  • Setting OZ Server Configurations
  • db. properties
  • repository.properties
  • Creating OZ Repository administrator account
  • Setting Categories, Users, Groups, Permissions
  • Creating categories
  • Creating user groups and users
  • Assign user or group permissions to categories
  • OZ Repository Manager
  • BUILTIN Type OZ Repository

Was this helpful?

  1. Server Developer

Repository Server

Types of OZ Repository

You can choose one of the 4 types of OZ Repository according to the way how to store and manage data needed to manage item files, categories, users, and permissions.

Type

Description

NONE

By default, OZ server uses OS file system, not a database.

BUILTIN

Use a built-in database provided by OZ server.

RDB

Use RDB provided by the user.

HYBRID

Use both RDB and NONE (use NONE type for backup purposes).

If you use NONE type repository, you can see your item files in ordinary formats (OZR and ODI) under the repository_files folder.

You are not able to see, however, those item files under the repository_files folder when using BUILTIN or RDB type repository because item files are managed in the internal format of OZ Server.

HYBRID type repository uses a database (BUILTIN or RDB) and also keeps item files in ordinary formats (ODI and OZR) under a folder designated by you to allow you to see your item files.

Here we’re learning how to use HYBRID type because it is a superset of repository types.

Setting OZ Server Configurations

Go to the conffolder under the OZ Server installation home under your web application. Here you need to modify 2 files, db. properties and repository.properties.

db. properties

If you want to use a different repository database from your application database, you need to add a database alias for OZ Repository manager in the db.properties file as below.

repo.vendor=mssql2008
repo.portNo=1433
repo.dbName=repository
repo.serverAddress=localhost
repo.user=sa
repo.password=yourpassword
repo.maxconns=20
repo.initconns=5
repo.timeout=5
repo.initSqls=
repo.closeSqls=
repo.doConnectionCheck=true
repo.testQueryString=select 1
repo.sessionQuery=
repo.encodecharset=
repo.decodecharset=
repo.fetchrow=0
repo.ignoreQueryError=false

In this example, we use MS SQL Server for repository management. The Database name is repository and the database alias name is repo. Please make sure to create a schema named repository before going further.

repository.properties

Copy the content below and paste it into repository.properties and save.

## Repository Properties
REPOSITORY_TYPE = HYBRID
#REPOSITORY_TYPE = RDB
REPOSITORY_DB_ALIAS = repo
#REPOSITORY_TYPE = BUILTIN
#REPOSITORY_TYPE = NONE
REPOSITORY_FILE_PATH = %OZ_HOME%/repository_files/
REPOSITORY_HYBRID_FILE_PATH=%OZ_HOME%/repository_files_backup/
#Backup History for None Type
REPOSITORY_NONE_BACKUP=false
REPOSITORY_NONE_BACKUP_PATH=%OZ_HOME%/repository_files_bak/
REPOSITORY_NONE_12 BACKUP_ITEM_COUNT=10
REPOSITORY_NONE_BACKUP_ITEM_VALIDDAYS=0
REPOSITORY_ITEM_NUMBER_PER_DIRECTORY = 500
REPOSITORY_HISTORY_ITEM_VALID_DAYS = 30
REPOSITORY_TEMP_DIRECTORY=%OZ_HOME%/temp
REPOSITORY_ACCESS_BY_HTTP_GET=false
REPOSITORY_HTTP_GET_CHECK_SESSION=false
REPOSITORY_RDB_BUILTIN_GUEST_ACCESS=true
# End

REPOSITORY_HYBRID_FILE_PATH indicates the path that you want to save item files in ordinary formats. Please refer to OZ Enterprise Server Administrator’s Guide for more detailed options. Once finished with setting files and creating a database, we need to restart WAS (or tomcat).

Creating OZ Repository administrator account

Open OZ server information page with “your application url + /server”. Create an admin account by entering the admin username and password.

Once you have clicked create account button, OZ Server will create the folder repository_files_backup under OZ server home and create 10 tables in the database named repository.

In the table dbo.oz_user, you can see the admin user has been created. All users you create will be added to this table.

Now you are ready to create item categories, users or user groups and assign category permissions to users or user groups.

Setting Categories, Users, Groups, Permissions

With OZ Repository manager, add a server connection and connect to it as illustrated below.

Creating categories

Once connected to the server, create your categories in the Category tab. Here I created 2 empty categories, Samples and Standard.

Creating user groups and users

Move to Group tab and you can see we already have admin user. Let’s create your groups. Here I created 2 groups, Group-A and Group-B.

Now add your users under groups.

Assign user or group permissions to categories

Now go back to Category tab, right click on a category (in this example, Standard) and select Permission. In Permissions Popup window, click Add button.

Now, user-A, a member of Group-A can access the category Standard. It means that user-A can see all items in the category Standard, and upload local files to or download items from the category.

OZ Repository Manager

The user can access OZ Repository Server with OZ Repository Manager, OZ e-Form Designer, or OZ Query Designer. Here we’ll use OZ e-Form Designer. Open Repository as shown below.

OZ Repository Manager, OZ e-Form Designer, and OZ Query Designer use the same Server List popup window.

Add server connection as done above and connect as user-A.

Once you connected, you can only see the category Standard because user-A was given access permission only to Standard.

In the Working Folder, make sure that you have a folder having the same name with the category name in the server repository.

Now you can upload files to the category Standard in the OZ Repository from the local folder Standard in the Working Folder.

Right-click on a file you want to upload and select Upload to Repository.

Check Keep checked out if you want to allow other users to access the uploaded file.

Click Upload button and then you can see the uploaded file in the Repository.

We set the repository file path and repository hybrid file path in the repository.properties file above as below.

REPOSITORY_FILE_PATH = %OZ_HOME%/1 repository_files/
REPOSITORY_HYBRID_FILE_PATH=%OZ_HOME%/repository_files_backup/

Under the repository_files folder, you can see some folders have been created. Those are the internal format of information of categories, items, groups and users.

Under the repository_files_backup folder, you can see form files (OZR and ODI) that you can actually open.

BUILTIN Type OZ Repository

If you want to use BUILTIN type, you only need to specify the type in the repository.properties as below.

REPOSITORY_TYPE = BUILTIN

BUILTIN type repository uses HSQLDB and you will need HSQLDB client tool to browse data.

PreviousExport with Scheduler TaskNextSync Server

Last updated 2 years ago

Was this helpful?

🌈