- How to install and use a Private Store
- Step 1: Configure your server
- Step 2: Generate the application setup
- Step 3: Install the application on the Private Store
- Using and configuring the Private Store
Private Store for WINDEV applications
Versions 27 and later include a Private Store. This store allows you to group applications used within an organization.
The Private Store can be accessed from within the organization only, or be publicly accessible .
A portal with optional authentication allows authorized users to install applications.
This standardizes and simplifies app distribution within an organization.
How to install and use a Private Store
Step 1: Configure your server
Two cases may occur:
- If you are using a PCSCloud platform: the required elements are installed by default on your platform.
Reminder: PCSCloud is a paid, turnkey solution. For more details, see PCSCloud.
- If you are not using a PCSCloud platform: install the following elements:
For more details, see Configuring a BaaS server (User Groupware and Private Store).
- an HFSQL server,
- the reserved server, including the modules for the Mobile User Groupware (WDBaaS).
Step 2: Generate the application setup
Application setups for the Private Store can be generated in the same way as standard application setups. Only a few options are different.
To generate the setup of your application in the Private Store:
- On the "Project" tab, in the "Generation" group, expand "Setup procedure" and select "Create setup procedure".
- The wizard that appears allows you to create the executable and the setup of your application.
- If you have not yet created the executable, follow the corresponding steps.
- Click "Setup" and select "Setup on a Private Store". Go to the next step.
- Enter the application parameters for the Private Store:
- Application name,
- Application visibility (private or public):
- Public application in the Private Store: Any user connected to Private Store can download and install the application.
- Private application in the Private Store: only authenticated users can access the application setup program.
- Description and image associated with the application.
- Go to the next step.
- Indicate the specific properties of the reference executable, as well as the description of the version for the Private Store.
- Go to the next step.
- The following steps are the same as those for generating the setup of a standard application. For more details, see Setup wizard: The steps for creating the setup of a WINDEV application.
- At the end of the wizard, you can choose how to generate the setup program. For applications deployed to the Private Store, only a self-extracting executable can be generated.
- Click "Finish". The setup program is generated.
Step 3: Install the application on the Private Store
Once the application setup program has been generated, it can be executed:
- directly ("Test").
- by running the "exe" program, located in the "Install_xxx" subdirectory of the project directory.
When installing the application:
- If necessary, select the setup language.
- Specify the Private Store connection options:
This information was provided during the setup of the server reserved.
- The address of the BaaS server used.
- The supervisor's login credentials.
- If you are using a PCSCloud platform, the server address is the name of your platform.
- The Private Store administration site can be accessed at http(s)://<PCSCLOUD server or platform>/WDBaaS. To log in for the first time, use "admin" as username, and enter the password specified in the setup.
- Specify the application setup parameters:
- Setup signature
- Integration of a custom configuration file.
New in version 28
Transition from a setup on the network to a setup on the Private Store: Indicate if the network setup of your application needs to become available in the Private Store. In this case, the old versions deployed on user computers will automatically update to use Private Store.
- Validate. The application is installed on the Private Store. You can share the Private Store link with the users of your application.
Using and configuring the Private Store
To verify and configure your application in the Private Store:
- Open the Private Store: The Private Store administration site can be accessed at http(s)://<PCSCLOUD server or platform>/WDBaaS.
- Deployed applications with visibility set to "Public" will be shown (visibility set in the setup creation wizard).
- To configure the options of the Private Store, click "Log in".
- To log in for the first time, use "admin" as username, and enter the password specified in the setup ("admin" by default). Once you are logged in, you can change the password if necessary.
- The application catalog appears. Click "Administration"..
- The administration site contains:
- The general options of Private Store, which can be accessed via a menu at the top of the page.
- The different applications in the Private Store, on the left. you can click the name of an application to see its options.
1. General options of the Private Store.
The general options of Private Store are:
- User and group management. You can add users and set a specific user as administrator (supervisor). Once the user is created, you can edit their profile and indicate if they are allowed to add Windows applications to the Private Store. This option is particularly useful for test Private Stores or for Private Stores specific to development teams.
- SMTP settings: This option allows you to configure the SMTP server to send emails to users.
- Options: This page contains all the customization and configuration options of the Private Store:
- Private Store label, which appears in the site banner (by default, "Application catalog").
- Add Windows applications: Allows or prevents users from adding applications to Private Store (you can also configure this option for each user).
- Account creation: Specifies the rights to create accounts: all users, none or only some users.
- User activation mode: Automatic or by email.
- Two-factor authentication: Mandatory or enabled only by the user. You can create a message prompting the user to contact an administrator if they cannot get the code.
- reCAPTCHA keys: Allows you to specify the reCAPTCHA v3 details (available in Google's Admin console).
- Token reset: A connection token is provided when the Application Server is installed. You can generate this token again in case of loss.
2. Application options.
The Windows application options allow you to:
- Get the reference version number of the application and the minimum version required. You can also determine if the application has been downloaded.
- Transform a public application into a private application. This allows you to define download rights:
- Download available to everyone.
- Download available only to connected users.
- Download available only to some users or groups.