Difference between revisions of "42Q-MES0166 Customization Platform"
(26 intermediate revisions by the same user not shown) | |||
Line 6: | Line 6: | ||
| | ||
− | = <span class="mw-headline" id="Introduction"><span class="mw-headline" id="Introduction"><span class="mw-headline" id="Introduction"><span class="mw-headline" id="Introduction">Introduction</span></span></span></span> = | + | |
+ | |||
+ | = <span class="mw-headline" id="Introduction"><span class="mw-headline" id="Introduction"><span class="mw-headline" id="Introduction"><span class="mw-headline" id="Introduction"><span class="mw-headline" id="Introduction"><span class="mw-headline" id="Introduction">Introduction</span></span></span></span></span></span> = | ||
The Customization Application Platform provides a platform that allows customization teams or customers to develop customized applications that can access MES data through an API. | The Customization Application Platform provides a platform that allows customization teams or customers to develop customized applications that can access MES data through an API. | ||
Line 39: | Line 41: | ||
<br/> | <br/> | ||
− | + | = <span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration">Server Information Configuration</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> = | |
− | |||
− | |||
− | |||
− | = <span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration"><span class="mw-headline" id="Server_Information_Configuration">Server Information Configuration</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span> = | ||
| | ||
Line 55: | Line 53: | ||
'''Figure 1: Server Information Portlet''' | '''Figure 1: Server Information Portlet''' | ||
− | [[File:SIP test.jpg| | + | [[File:SIP test.jpg|1200px|SIP test.jpg]] |
| | ||
Line 74: | Line 72: | ||
| | ||
− | + | | |
− | + | = <span class="mw-headline" id="Customization_Apps"><span class="mw-headline" id="Customization_Apps"><span class="mw-headline" id="Customization_Apps">Customization Apps</span></span></span> = | |
− | |||
− | |||
− | + | The Customization Apps Section is groped by the following three portlets: Custom Apps Management, Launch Pad MAintenance, and Target Info, below, each of these portlets will be explained. | |
| | ||
− | + | '''Figure 3: Customization Apps''' | |
− | + | [[File:SIP CustomizationApps.png|SIP CustomizationApps.png]] | |
| | ||
− | |||
− | |||
− | |||
− | |||
| | ||
− | + | == <span class="mw-headline" id="Custom_Apps_Management"><span class="mw-headline" id="Custom_Apps_Management"><span class="mw-headline" id="Custom_Apps_Management">Custom Apps Management</span></span></span> == | |
− | + | The Site administrator utilizes this portlet to effortlessly upload and deploy custom apps. Users have the freedom to develop their application and package it as a .war file. By using the launching pad upload page, users can easily upload the .war file. Once uploaded, users can navigate to the launchpad, where they will find their application's icon, ready to be launched and opened. | |
| | ||
− | + | === <span class="mw-headline" id="Upload"><span class="mw-headline" id="Upload"><span class="mw-headline" id="Upload"><span class="mw-headline" id="Upload">Upload''' '''</span></span></span></span> === | |
− | |||
− | < | ||
− | + | To upload a new file packed .war file. users can take a .war file as an installation package. | |
| | ||
− | + | '''Figure 4: Customization Apps Upload''' | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | '''[[File:SIP Upload.png|1200px|SIP Upload.png]]''' | |
| | ||
− | |||
− | |||
| | ||
− | + | === <span class="mw-headline" id="Deploy_All_Custom_Apps"><span class="mw-headline" id="Deploy_All_Custom_Apps"><span class="mw-headline" id="Deploy_All_Custom_Apps"><span class="mw-headline" id="Deploy_All_Custom_Apps"><span class="mw-headline" id="Deploy_All_Custom_Apps">Deploy All Custom Apps</span></span></span></span></span> === | |
− | |||
− | + | To access the Custom Apps Management portlet, navigate to'''Administration > Customization Apps > Custom Apps Management'''. | |
− | ''' | + | To deploy all the custom applications, click on the '''Deploy All''' button and a pop-up window will display, users may notice that the column '''Status''' indicates whether the deployment was successful (blue tick icon) or not (red ex icon). |
− | ''' | + | <br/> '''Figure 5: Deploying All The Custom Apps''' |
− | + | [[File:SIP DeployAll.png|1200px|SIP DeployAll.png]] | |
− | |||
− | |||
− | |||
− | |||
| | ||
− | ''' | + | '''<u>Note:</u> '''It is not possible to deploy only one or various custom apps; By clicking on the '''Deploy All''' button, all the apps listed will be deployed. |
− | |||
− | ''' | ||
− | + | Press the '''Deploy All '''button as seen to retry deploying all the apps that failed to be deployed, however, if users retry the deployment, the '''Deployment History ID''' and '''Time''' values will change. | |
| | ||
− | + | '''Figure 6: Deployment Details''' | |
− | |||
− | |||
− | |||
− | |||
− | + | '''[[File:SIP DeployAllDetails.png|1200px|SIP DeployAllDetails.png]]''' | |
− | |||
| | ||
− | + | '''<u>Note:</u> '''Users may have to wait between 5 and 15 minutes to run the launchpad after deploying successfully. | |
− | |||
− | |||
| | ||
− | |||
− | |||
| | ||
− | + | === <span class="mw-headline" id="Delete_a_Custom_App"><span class="mw-headline" id="Delete_a_Custom_App"><span class="mw-headline" id="Delete_a_Custom_App"><span class="mw-headline" id="Delete_a_Custom_App"><span class="mw-headline" id="Delete_a_Custom_App">Delete a Custom App</span></span></span></span></span> === | |
− | |||
− | |||
− | + | To delete a custom app, select the app to be deleted and click on the Delete button. | |
− | + | <br/> '''Figure 7: Select and Delete Custom App''' | |
− | + | '''[[File:SIP SelectandDelete.png|1200px|SIP SelectandDelete.png]]''' | |
| | ||
Line 189: | Line 150: | ||
| | ||
− | + | # | |
− | + | == <span class="mw-headline" id="Launchpad_Maintenance_Configuration"><span class="mw-headline" id="Launchpad_Maintenance_Configuration">Launchpad Maintenance Configuration</span></span> == | |
− | + | The'''Launchpad Maintenance Configuration Portlet i'''s used by the 42Q support team, site admin, and customization team to maintain the custom app entry in the MES Portal. | |
| | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| | ||
− | + | === <span class="mw-headline" id="Add_a_New_Application"><span class="mw-headline" id="Add_a_New_Application"><span class="mw-headline" id="Add_a_New_Application">Add a New Application</span></span></span> === | |
− | + | From the menu panel, navigate to '''Administration > Customization Apps > LaunchPad Maintenance''' | |
− | ''' | + | To add a new application, click the '''Add''' button. |
− | + | #'''Enter''' a name for the application. | |
− | + | #'''Enter''' the URL of the application. | |
− | ''' | + | #In the Icon field, '''enter''' the image address of the application icon. |
+ | #Notice that the '''Type''' field is filled in automatically with the default value ‘Iframe’. | ||
+ | #'''Enter''' the application’s version | ||
+ | #'''Click''' the '''Save''' button to save the information or '''Cancel''' to abort | ||
− | + | <br/> '''Figure 8: Filling In The App Information''' | |
− | + | [[File:SIP AddAppInfo.png|1200px|SIP AddAppInfo.png]] | |
| | ||
− | + | Edit will change how the application shows when opening. | |
− | To | + | '''Note: '''To '''Edit''' an application, select an application from the list and click the edit button on the header. '''Change''' the information of the app and click to '''Save''' or '''Cancel'''. |
| | ||
− | ''' | + | === <span class="mw-headline" id="Active_.2F_Disable_an_Application"><span class="mw-headline" id="Active_.2F_Disable_an_Application"><span class="mw-headline" id="Active_.2F_Disable_an_Application"><span class="mw-headline" id="Active_.2F_Disable_an_Application">'''Active / Disable an Application'''</span></span></span></span> === |
− | + | Users are able to activate or disable current applications listed in the Launchpad Maintenance portlet. | |
− | | + | In order to activate or disable an application, users must follow the next steps below: |
− | + | #'''Select''' an application from the list. | |
− | + | #'''Click''' [[File:SIP icon1.png|SIP icon1.png]] the button on the header to activate or disable the selected application | |
− | |||
− | + | '''Note: '''Applications that are currently active are marked with a blue checked icon under the “'''Active'''” column, and applications that have been disabled are marked with a gray checked icon under the'''“Active” '''column. | |
| | ||
− | '''Figure | + | '''Figure 9: Active / Disable''' |
− | [[File: | + | '''[[File:SIP Active Disable.png|1200px|SIP Active Disable.png]]''' |
| | ||
− | |||
− | |||
| | ||
− | + | # | |
− | |||
− | |||
− | |||
− | | ||
− | | + | == <span class="mw-headline" id="Target_Info"><span class="mw-headline" id="Target_Info">Target Info </span></span> == |
− | + | This portlet is used by the 42Q administrator to generate the site-target string and add this string to the app attribute in Apigee. Doing so will allow the app to gain access to the site/target’s data defined in the string. | |
− | + | From the menu panel, navigate to '''Administration > Customization Apps > Target Info.''' | |
− | + | This portlet will be used by the 42Q support team in order to provide external Engineers with the Target. | |
− | |||
− | |||
| | ||
− | |||
− | |||
− | |||
− | |||
| | ||
− | + | === <span class="mw-headline" id="Targets"><span class="mw-headline" id="Targets"><span class="mw-headline" id="Targets">Targets</span></span></span> === | |
− | + | To visualize the user’s Target, select the Site and click on the Targets button, to close the pop-up window click on the '''OK''' button. | |
| | ||
− | + | '''Figure 10: Target Provided By The 42Q Support Team''' | |
− | + | [[File:SIP Targets.png|1200px|SIP Targets.png]] | |
| | ||
− | |||
− | |||
− | |||
− | |||
| | ||
Line 295: | Line 236: | ||
'''Figure 19: Server Information Shop Floor ID''' | '''Figure 19: Server Information Shop Floor ID''' | ||
− | [[File:CP ServerInfoShopOrderID.png| | + | [[File:CP ServerInfoShopOrderID.png|1200px|CP ServerInfoShopOrderID.png]] |
'''<u>Note:</u> '''Notice that the Target matches with the Shop Floor ID from the server information portlet. | '''<u>Note:</u> '''Notice that the Target matches with the Shop Floor ID from the server information portlet. | ||
Line 302: | Line 243: | ||
| | ||
− |
Latest revision as of 21:09, 18 July 2023
42Q Home > Administration > Customization Platfom
Administration
Customization Platform
Version MES 15.77
Revision B1
Introduction
The Customization Application Platform provides a platform that allows customization teams or customers to develop customized applications that can access MES data through an API.
Process of Customization Platform for External Customers:
- Developer Register
- The support team configures the app and assigns the APIs to the developer
- The developer develops the custom app
- Dev-Ops run Terraform script to create a Sandbox server to host custom apps
- The support team configures the Sandbox information into Server Information
- Site admin uploads and deploys the custom apps
Process of customization platform for 42Q:
- The customization team develops custom apps
- Dev-Ops run TF script to deploy the custom apps to a Sandbox server
The Customization Application Platform is organized by the following portlets:
- Server Information Configuration
- Customizations Apps
- Custom Apps Management
- Target Info
Server Information Configuration
The Server Information form must be filled in by the 42Q support team; Below are the steps listed to set up the configuration for Server Information:
From the menu panel, navigate to Administration > Server Information
Figure 1: Server Information Portlet
To add new server information, click the Add button.
- Fill in the fields with the corresponding information.
- To save the server information, click the Save button or Cancel to abort
Figure 2: Filling In The New Server Information
Customization Apps
The Customization Apps Section is groped by the following three portlets: Custom Apps Management, Launch Pad MAintenance, and Target Info, below, each of these portlets will be explained.
Figure 3: Customization Apps
Custom Apps Management
The Site administrator utilizes this portlet to effortlessly upload and deploy custom apps. Users have the freedom to develop their application and package it as a .war file. By using the launching pad upload page, users can easily upload the .war file. Once uploaded, users can navigate to the launchpad, where they will find their application's icon, ready to be launched and opened.
Upload
To upload a new file packed .war file. users can take a .war file as an installation package.
Figure 4: Customization Apps Upload
Deploy All Custom Apps
To access the Custom Apps Management portlet, navigate toAdministration > Customization Apps > Custom Apps Management.
To deploy all the custom applications, click on the Deploy All button and a pop-up window will display, users may notice that the column Status indicates whether the deployment was successful (blue tick icon) or not (red ex icon).
Figure 5: Deploying All The Custom Apps
Note: It is not possible to deploy only one or various custom apps; By clicking on the Deploy All button, all the apps listed will be deployed.
Press the Deploy All button as seen to retry deploying all the apps that failed to be deployed, however, if users retry the deployment, the Deployment History ID and Time values will change.
Figure 6: Deployment Details
Note: Users may have to wait between 5 and 15 minutes to run the launchpad after deploying successfully.
Delete a Custom App
To delete a custom app, select the app to be deleted and click on the Delete button.
Figure 7: Select and Delete Custom App
Launchpad Maintenance Configuration
TheLaunchpad Maintenance Configuration Portlet is used by the 42Q support team, site admin, and customization team to maintain the custom app entry in the MES Portal.
Add a New Application
From the menu panel, navigate to Administration > Customization Apps > LaunchPad Maintenance
To add a new application, click the Add button.
- Enter a name for the application.
- Enter the URL of the application.
- In the Icon field, enter the image address of the application icon.
- Notice that the Type field is filled in automatically with the default value ‘Iframe’.
- Enter the application’s version
- Click the Save button to save the information or Cancel to abort
Figure 8: Filling In The App Information
Edit will change how the application shows when opening.
Note: To Edit an application, select an application from the list and click the edit button on the header. Change the information of the app and click to Save or Cancel.
Active / Disable an Application
Users are able to activate or disable current applications listed in the Launchpad Maintenance portlet.
In order to activate or disable an application, users must follow the next steps below:
- Select an application from the list.
- Click the button on the header to activate or disable the selected application
Note: Applications that are currently active are marked with a blue checked icon under the “Active” column, and applications that have been disabled are marked with a gray checked icon under the“Active” column.
Figure 9: Active / Disable
Target Info
This portlet is used by the 42Q administrator to generate the site-target string and add this string to the app attribute in Apigee. Doing so will allow the app to gain access to the site/target’s data defined in the string.
From the menu panel, navigate to Administration > Customization Apps > Target Info.
This portlet will be used by the 42Q support team in order to provide external Engineers with the Target.
Targets
To visualize the user’s Target, select the Site and click on the Targets button, to close the pop-up window click on the OK button.
Figure 10: Target Provided By The 42Q Support Team
Figure 19: Server Information Shop Floor ID
Note: Notice that the Target matches with the Shop Floor ID from the server information portlet.