

Product Profiles

When a WSO2 product starts, it starts all components, features and related artifacts bundled with it. Multi-profile support allows you to run the product on a selected profile so that only the features specific to that profile along with common features start up with the server.

Tip

Starting a product on a preferred profile only blocks/allows the relevant OSGI bundles. As a result, even if you start the server on a profile such as the api-devportal for example, you can still access the API Publisher web application.

Osgi

OSGI bundle is a tightly coupled, dynamically loadable collection of classes, jars, and configuration files that explicitly declare their external dependencies (if any). In OSGi, a bundle is the primary deployment format. Bundles are applications that are packaged in JARs, and can be installed, started, stopped, updated, and removed.

API-M Profiles

The following are the different profiles available in WSO2 API Manager.

Profile	Command Option with Profile Name	Description
Gateway worker	-Dprofile=gateway-worker	Only starts the components related to the API Gateway. You use this when the API Gateway acts as a worker node in a cluster. This profile starts the backend features for data processing and communicates with the management node.
Key Manager	-Dprofile=api-key-manager	Only starts the features relevant to the Key Manager component of the API Manager.
Traffic Manager	-Dprofile=traffic-manager	Only starts the features relevant to the Traffic Manager component of the API Manager. The Traffic Manager helps users to regulate API traffic, make APIs and applications available to consumers at different service levels, and secure APIs against security attacks. The Traffic Manager features a dynamic throttling engine to process throttling policies in real-time, including rate limiting of API requests.
API Publisher	-Dprofile=api-publisher	Only starts the front end/backend features relevant to the API Publisher.
Developer Portal	-Dprofile=api-devportal	Only starts the front end/backend features relevant to the Developer Portal.

Starting an API-M profile

You can start an API Manager profile in the following methods, based on your requirement

• Method 1 - Optimizing before starting the server
• Method 2 - Optimizing while starting the server

Note

It is recommended to start the components in the following order:

1. Traffic Manager
2. Key Manager
3. Publisher
4. Developer Portal
5. Gateway

Method 1- Optimizing before starting the server

Create an optimized distribution for a particular API-M profile.

1. Run the <API-M_HOME>/bin/profileSetup.sh script or <API-M_HOME>/bin/profileSetup.bat script based on your operating system, with the profile flag.

   Sample Format

   sh <API-M_HOME>/bin/profileSetup.sh  -Dprofile=<preferred-profile>

   Example:Linux/Solaris/MacOS

   sh <API-M_HOME>/bin/profileSetup.sh  -Dprofile=api-publisher

   Example:Windows

   <PRODUCT_HOME>/bin/profileSetup.bat -Dprofile=api-publisher

2. Copy the respective databasee connector JAR to /lib directory.

   For example, if you are using a MySQL database,

   1. Download the MySQL connector JAR file and extract it.

   2. Copy it to the <API-M_HOME>/repository/components/lib/ directory.

3. Create the required databases, namely the API-M database (apimgtdb also known as WSO2_AM_DB) and the shared database (WSO2_SHARED_DB also known as shareddb).

4. Update the default DB configurations to match your environment.

   Change the following DB configurations, which is in the <API-M_HOME>/repository/conf/deployment.toml file.

   [database.apim_db]
   type = "mysql"
   hostname = "localhost"
   name = "apimgt_db"
   port = "3306"
   username = "root"
   password = "root"
   
   [database.shared_db]
   type = "mysql"
   hostname = "localhost"
   name = "shared_db"
   port = "3306"
   username = "root"
   password = "root"

5. Start the server with the specified profile.

   If the product pack is "in-place updated" using the "WSO2 in-place updates tool" after the initial profile optimization, it would have fetched irrelevant files for this profile. With the --optimize option, the pack will be profile-optimized again and it will make sure that the pack will be in a correctly optimized state.

   Configuration optimization is one of the steps in profile optimization process. This replaces the deployment.toml file with a pre-configured profile-specific TOML file that exists in the pack. If required, you can skip this step from the profile optimization process via passing the additional --skipConfigOptimization option. This prevents the existing deployment.toml file in the pack from being overridden.

   Sample Format

   sh <API-M_HOME>/bin/wso2server.sh -Dprofile=<preferred-profile> --optimize --skipConfigOptimization

   Example:Linux/Solaris/MacOS

   sh <API-M_HOME>/bin/wso2server.sh -Dprofile=api-publisher --optimize --skipConfigOptimization

   Example:Windows

   <PRODUCT_HOME>/bin/wso2server.bat -Dprofile=api-publisher --optimize --skipConfigOptimization

Method 2 - Optimizing while starting the server

1. Start the server using the script based on your operating system, using the command given below.

   Sample Format

   sh <PRODUCT_HOME>/bin/wso2server.sh --optimize -Dprofile=<preferred-profile>

   Example:Linux/Solaris/MacOS

   sh <PRODUCT_HOME>/bin/wso2server.sh --optimize -Dprofile=api-publisher

   Example:Windows

   <PRODUCT_HOME>/bin/wso2server.bat --optimize -Dprofile=api-publisher

   Click here to see the sample output when you optimize the server for Publisher profile while starting in Publisher profile.

   [2020-02-26 11:50:39] INFO - Starting to optimize API Manager for the API Publisher profile
   [2020-02-26 11:50:39] INFO - Starting to optimize configs in deployment.toml
   [2020-02-26 11:50:39] INFO - Renamed the existing ../repository/conf/deployment.toml file as deployment.toml
               .backup
   [2020-02-26 11:50:39] INFO - Renamed the existing ../repository/resources/conf/deployment-templates/api-publisher.toml file as deployment.toml
   [2020-02-26 11:50:39] INFO - Removed the WebSocketInboundEndpoint.xml file from ../repository/deployment/server/synapse-configs/default/inbound-endpoints/
   [2020-02-26 11:50:39] INFO - Removed the SecureWebSocketInboundEndpoint.xml file from ../repository/deployment/server/synapse-configs/default/inbound-endpoints/
   [2020-02-26 11:50:39] INFO - Removed the api#identity#consent-mgt#v1.0.war file from ../repository/deployment/server/webapps
   [2020-02-26 11:50:39] INFO - Removed the throttle#data#v1.war file from ../repository/deployment/server/webapps
   [2020-02-26 11:50:39] INFO - Removed the am#sample#pizzashack#v1.war file from ../repository/deployment/server/webapps
   [2020-02-26 11:50:39] INFO - Removed the api#am#store#v0.16.war file from ../repository/deployment/server/webapps
   [2020-02-26 11:50:39] INFO - Removed the api#am#store.war file from ../repository/deployment/server/webapps
   [2020-02-26 11:50:39] INFO - Removed the api#identity#recovery#v0.9.war file from ../repository/deployment/server/webapps
   [2020-02-26 11:50:39] INFO - Removed the api#identity#user#v1.0.war file from ../repository/deployment/server/webapps
   [2020-02-26 11:50:39] INFO - Removed the api#identity#oauth2#dcr#v1.1.war file from ../repository/deployment/server/webapps
   [2020-02-26 11:50:39] INFO - Removed the am#sample#calculator#v1.war file from ../repository/deployment/server/webapps
   [2020-02-26 11:50:39] INFO - Removed devportal directory from ../repository/deployment/server/jaggeryapps
   Finished the optimizations
   Starting the server...
   JAVA_HOME environment variable is set to /Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home
   CARBON_HOME environment variable is set to /Users/samithac/WSO2/RND-Projects/16-profile-optimization-fix/setup/wso2am-3.1.0-beta
   Using Java memory options: -Xms256m -Xmx1024m
   [2020-02-26 11:50:41,936]  INFO {org.wso2.config.mapper.ConfigParser} - Applying Configurations upon new Templates
   [2020-02-26 11:50:41,938]  WARN {org.wso2.config.mapper.ConfigParser} - Overriding files in configuration directory /Users/samithac/WSO2/RND-Projects/16-profile-optimization-fix/setup/wso2am-3.1.0-beta
   [2020-02-26 11:50:42,759]  INFO {org.wso2.config.mapper.ConfigParser} - Writing Metadata Entries...
   [2020-02-26 11:50:47,604]  INFO - CarbonCoreActivator Starting WSO2 Carbon...
   [2020-02-26 11:50:47,612]  INFO - CarbonCoreActivator Operating System : Mac OS X 10.14.6, x86_64
   [2020-02-26 11:50:47,613]  INFO - CarbonCoreActivator Java Home        : /Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/jre
   [2020-02-26 11:50:47,613]  INFO - CarbonCoreActivator Java Version     : 1.8.0_152

   Sample Format

   sh <PRODUCT_HOME>/bin/wso2server.sh --optimize -Dprofile=<preferred-profile> --skipConfigOptimization

   Example:Linux/Solaris/MacOS

   sh <PRODUCT_HOME>/bin/wso2server.sh --optimize -Dprofile=api-publisher --skipConfigOptimization    

   Example:Windows

   <PRODUCT_HOME>/bin/wso2server.bat --optimize -Dprofile=api-publisher --skipConfigOptimization
   

Before running this command (with the --skipConfigOptimization option) you are expected to do the configuration changes in the deployment.toml file manually in the pack. Passing this option allows you to preserve the configurations that you previously manually applied while optimizing the profile.

Note

Profile optimization using scripts is the recommended approach. Manually optimizing and including the usage of the --skipConfigOptimization option should be done only in the cases where it can't be avoided.

Top