1. Step 1: Configure your server if necessary.
2. Step 2: Generate your application.
3. Step 3: Install the application on the Private Store.

Step 1: Configure your server

• You are using a PCSCloud platform: the necessary elements are installed by default on your platform.
  Reminder: PCSCloud is a pay-as-you-go, turnkey solution. For more details, see PCSCloud.
  To have your Private Store hosted by PCSCloud, choose Operating platform.
• You're not using a PCSCloud platform: install the following:
  • an HFSQL server,
  • the reserved server, including the modules for the Mobile User Groupware (WDBaaS).
  For more details, see Configuring a BaaS server (User Groupware and Private Store).

Step 2: Generate the application installation

1. On the "Project" tab, in the "Generation" group, expand "Setup procedure" and select "Create setup procedure".
2. The wizard that appears allows you to create the executable and the setup of your application.
3. If you have not yet created the executable, follow the corresponding steps.
4. Click "Setup" and select "Setup on a Private Store". Go to the next step.
5. Enter the application parameters for the Private Store:
   • Application name,
   • Application visibility (private or public):
     • A public application in the Private Store: anyone connected to the Private Store can download and install the application..
     • A private application in the Private Store: only authenticated users can access the application installation..
   • Description and image associated with the application.
6. Go to the next step.
7. Indicate the specific properties of the reference executable, as well as the description of the version for the Private Store.
8. Go to the next step.
9. The following steps are the same as those for generating the setup of a standard application. For more details, see Setup wizard: Steps for creating a WINDEV application setup program.
10. 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.
11. Click "Finish". The setup program is generated.

Step 3: Install the application on the Private Store

• directly ("Test").
• by running the "exe" program, located in the "Install_xxx" subdirectory of the project directory.

1. If necessary, select the language in which the installation will run.
2. Specify the Private Store connection options:
   • The address of the BaaS server used.
   • The supervisor's login credentials.
   This information was provided during the setup of the server reserved.
   • 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.
3. Specify the application setup parameters:
   • Setup signature
   • Integration of a custom configuration file.
   • Switch from "network" to "Private Store" installation: Specify whether your application's network installation must be upgraded to be available in the Private Store.. In this case, the old versions deployed on user computers will automatically update to use Private Store.
4. 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

1. Launch the Private Store: The Private Store administration site can be accessed from a browser at http(s)://<serveur ou plateforme PCSCloud>/WDBaaS.
2. Deployed applications with visibility set to "Public" will be shown (visibility set in the setup creation wizard).
3. To configure the options of the Private Store, click "Log in".
4. To log in for the first time, use "admin" as username, and enter the password specified in the setup. Once you are logged in, you can change the password if necessary.
5. The application catalog appears. Click "Administration"..
6. The administration site contains:
   • The Private Store general options, 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.

• 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 define SMTP options for the SMTP server used to send emails to users..
• Options: This page contains all the options for customizing and configuring the Private Store:
  • Private Store label, which appears in the site banner (by default, "Application catalog").
  • Add Windows applications: Select whether or not all users can add applications to the Private Store (this setting can also be set at the individual user level)..
  • Account creation: Allows you to specify account creation rights: all users, none or only some users.
  • New user activation rules: activation can be automatic or by email.
  • Two-factor authentication: two-factor authentication can be either 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 key: Allows you to enter reCAPTCHA version 3 information (available in the application's Google console)..
  • Token reset: When the Application Server was installed, a connection token was supplied.. You can generate this token again in case of loss.

• 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.