Connect to Live GMO MakeShop Data in PostGresSQL Interface through CData Connect Cloud

There are a vast number of PostgreSQL clients available on the Internet. PostgreSQL is a popular interface for data access. When you pair PostgreSQL with CData Connect Cloud, you gain database-like access to live GMO MakeShop data from PostgreSQL. In this article, we walk through the process of connecting to GMO MakeShop data in Connect Cloud and establishing a connection between Connect Cloud and PostgreSQL using a TDS foreign data wrapper (FDW).

CData Connect Cloud provides a pure SQL Server interface for GMO MakeShop, allowing you to query data from GMO MakeShop without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect Cloud pushes all supported SQL operations (filters, JOINs, etc.) directly to GMO MakeShop, leveraging server-side processing to return the requested GMO MakeShop data quickly.

Connect to GMO MakeShop in Connect Cloud

CData Connect Cloud uses a straightforward, point-and-click interface to connect to data sources.

1. Log into Connect Cloud, click Connections and click Add Connection

2. Select "GMO MakeShop" from the Add Connection panel

3. Enter the necessary authentication properties to connect to GMO MakeShop.

   Configuring Access to GMO MakeShop

   GMO MakeShop requires AccessCode for each API. To obtain MembersAccessCode, OrdersAccessCode, ProductsAccessCode, and ShopId, follow the steps below:

   • Log in to the GMO MakeShop Store Manager and click Create Shop.
   • Click any target connection setting from External System Connection in the left-hand navigation menu. If you cannot find it in the menu, please contact GMO Makeshop.
   • Product Data Connection Settings: Click Issue to retrieve the authentication code and ProductsAccessCode.
   • Order Data Connection Settings: First select Get Order Information > Change Order Information settings. Then click Issue to retrieve the authentication code and OrdersAccessCode.
   • Members Data Connection Settings: Select Get/Post/Update/Delete Members Information settings. Then click Issue to retrieve the authentication code and MembersAccessCode.
   < li>Members Authentication Connection Settings: Click Issue to retrieve the authentication code and ProductsAccessCode.

   Authenticating to GMO MakeShop Account

   Set the following connection properties to connect:

   • ShopId: Set the GMO MakeShop Store ID of the connection destination. The GMO MakeShop Store ID is the same as the ID for login.
   • OrdersAccessCode: Set the orders access code retrieved from Order Data Connection Settings. This property is required to access the Orders table.
   • ProductsAccessCode: Set the products access code retrieved from Product Data Connection Settings. This property is required to access the Products table.
   • MembersAccessCode: Set the members access code retrieved from Members Data Connection Settings. This property is required to access the Members table.
   • MemberAuthenticationCode: Set the member authentication code retrieved from Members Authentication Connection Settings. This property is required to execute MemberAuthenticationConfirm.
   • Password: Specify the password for the GMO MakeShop Store Manager login user. This property is required to execute ProductCategoryRegistrationOrModification, ProductMemberGroupPriceRegistrationOrModification, ProductOptionRegistrationOrModification, and ProductRegistrationOrModification.
   
4. Click Create & Test
5. Navigate to the Permissions tab in the Add GMO MakeShop Connection page and update the User-based permissions.

Add a Personal Access Token

If you are connecting from a service, application, platform, or framework that does not support OAuth authentication, you can create a Personal Access Token (PAT) to use for authentication. Best practices would dictate that you create a separate PAT for each service, to maintain granularity of access.

1. Click on your username at the top right of the Connect Cloud app and click User Profile.
2. On the User Profile page, scroll down to the Personal Access Tokens section and click Create PAT.
3. Give your PAT a name and click Create.

4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

Build the TDS Foreign Data Wrapper

The Foreign Data Wrapper can be installed as an extension to PostgreSQL, without recompiling PostgreSQL. The tds_fdw extension is used as an example (https://github.com/tds-fdw/tds_fdw).

1. You can clone and build the git repository via something like the following view source: sudo apt-get install git git clone https://github.com/tds-fdw/tds_fdw.git cd tds_fdw make USE_PGXS=1 sudo make USE_PGXS=1 install Note: If you have several PostgreSQL versions and you do not want to build for the default one, first locate where the binary for pg_config is, take note of the full path, and then append PG_CONFIG= after USE_PGXS=1 at the make commands.
2. After you finish the installation, then start the server: sudo service postgresql start
3. Then go inside the Postgres database psql -h localhost -U postgres -d postgres Note: Instead of localhost you can put the IP where your PostgreSQL is hosted.

Connect to GMO MakeShop data as a PostgreSQL Database and query the data!

After you have installed the extension, follow the steps below to start executing queries to GMO MakeShop data:

1. Log into your database.
2. Load the extension for the database: CREATE EXTENSION tds_fdw;
3. Create a server object for GMO MakeShop data: CREATE SERVER "GMOMakeShop1" FOREIGN DATA WRAPPER tds_fdw OPTIONS (servername'tds.cdata.com', port '14333', database 'GMOMakeShop1');
4. Configure user mapping with your email and Personal Access Token from your Connect Cloud account: CREATE USER MAPPING for postgres SERVER "GMOMakeShop1" OPTIONS (username 'username@cdata.com', password 'your_personal_access_token' );
5. Create the local schema: CREATE SCHEMA "GMOMakeShop1";
6. Create a foreign table in your local database: #Using a table_name definition: CREATE FOREIGN TABLE "GMOMakeShop1".Members ( id varchar, MemberName varchar) SERVER "GMOMakeShop1" OPTIONS(table_name 'GMOMakeShop.Members', row_estimate_method 'showplan_all'); #Or using a schema_name and table_name definition: CREATE FOREIGN TABLE "GMOMakeShop1".Members ( id varchar, MemberName varchar) SERVER "GMOMakeShop1" OPTIONS (schema_name 'GMOMakeShop', table_name 'Members', row_estimate_method 'showplan_all'); #Or using a query definition: CREATE FOREIGN TABLE "GMOMakeShop1".Members ( id varchar, MemberName varchar) SERVER "GMOMakeShop1" OPTIONS (query 'SELECT * FROM GMOMakeShop.Members', row_estimate_method 'showplan_all'); #Or setting a remote column name: CREATE FOREIGN TABLE "GMOMakeShop1".Members ( id varchar, col2 varchar OPTIONS (column_name 'MemberName')) SERVER "GMOMakeShop1" OPTIONS (schema_name 'GMOMakeShop', table_name 'Members', row_estimate_method 'showplan_all');
7. You can now execute read/write commands to GMO MakeShop: SELECT id, MemberName FROM "GMOMakeShop1".Members;

More Information & Free Trial

Now, you have created a simple query from live GMO MakeShop data. For more information on connecting to GMO MakeShop (and more than 100 other data sources), visit the Connect Cloud page. Sign up for a free trial and start working with live GMO MakeShop data in PostgreSQL.