{"id":5988,"date":"2021-08-26T01:05:07","date_gmt":"2021-08-25T16:05:07","guid":{"rendered":"https:\/\/www.wexal.jp\/document-3-0-0\/setting\/migrate-setting-manager\/"},"modified":"2023-01-06T22:00:53","modified_gmt":"2023-01-06T13:00:53","slug":"migrate-setting-manager","status":"publish","type":"page","link":"https:\/\/www.wexal.jp\/en\/document-3-0-0\/setting\/migrate-setting-manager\/","title":{"rendered":"When Migrating from a Previous PST (2.x) - Setup in PST Manager (3.0.0)"},"content":{"rendered":"\n<p>PST (3.x) has changed configuration from the previous PST (2.x). Therefore, a configuration migration is required. You cannot update PST by using \"yum update\".<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Updating_from_the_PST_2x_Module\"><\/span>Updating from the PST (2.x) Module<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Before migrating to PST (3.x), update PST (2.x) to the latest version. Root privileges are necessary to update.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>$ sudo yum update kusanagi-prem<\/code><\/pre>\n\n\n\n<p>or<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>$ su -\n&#91;root@kusanagi8 ~]# yum update kusanagi-prem<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Updating_PST_2x_Profiles\"><\/span>Updating PST (2.x) Profiles<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Before migrating to PST (3.x), update all PST (2.x) enabled profiles to the latest version. You can find PST enabled profiles in PST Manager. Or, you can find them with the following root privilege commands.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91;root@kusanagi8 ~]# for i in \/home\/kusanagi\/*; do test -f $i\/wexal\/pst.config.yaml &amp;&amp; echo $i; done\n\/home\/kusanagi\/%PROFILE-NAME%<\/code><\/pre>\n\n\n\n<p>Update profiles with the PST (2.x) \"pst\" command. Note, root privileges are required to execute the PST (2.x) \"pst\" command.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91;root@kusanagi8 ~]# cd \/home\/kusanagi\/%PROFILE-NAME%\n&#91;root@kusanagi8 %PROFILE-NAME%]# pst -v\n\nWhen the Profile Version is the same as the Global Version:\n\nNo update is required.\n\nWhen the Profile Version is earlier than v2.4.4:\n\n&#91;root@kusanagi8 %PROFILE-NAME%]# test -f \/etc\/httpd\/conf.d\/ssl.conf &amp;&amp; mv \/etc\/httpd\/conf.d\/ssl.conf \/etc\/httpd\/conf.d\/ssl.conf.bak\n&#91;root@kusanagi8 %PROFILE-NAME%]# pst init --rebuildconf\n\nWhen the Profile Version is v2.4.4 or later\n\n&#91;root@kusanagi8 %PROFILE-NAME%]# pst init<\/code><\/pre>\n\n\n\n<p>If you use a reverse proxy, \"--reverseproxy\" and \"--origin options\" must also be specified in the \"pst init\" command.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Uninstalling_the_PST_2x_Module\"><\/span>Uninstalling the PST (2.x) Module<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>First, uninstall the PST (2.x) module. You must have root privileges to uninstall.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91;root@kusanagi8 ~]# yum erase kusanagi-prem kusanagi-nodejs-prem kusanagi-lua-prem<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Installing_the_PST_3x_Module\"><\/span>Installing the PST (3.x) Module<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Install the PST (3.x) module. You must have root privileges to install.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91;root@kusanagi8 ~]# yum install kusanagi-prem3<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Adding_Users_for_PST_Manager\"><\/span>Adding Users for PST Manager<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>PST Manager is a web administration page for controlling PST functions. You can add users able to login to PST Manager on this page and set their credentials. Adding users is executed with the \"pst passwd\" command.<\/p>\n\n\n\n<p>The user name must be a combination of lowercase and uppercase letters, numbers, . (period), _ (underscore), and - (hyphen), and at least 3 and no more than 16 characters long.<\/p>\n\n\n\n<p>The password must be lowercase or uppercase letters, numbers, . (period), ! (exclamation), # (sharp), % (percent), + (plus), _ (underscore), and - (hyphen).<\/p>\n\n\n\n<p>To execute the \"pst\" command,\"kusanagi\" user or root privileges are required. Note, you can keep users and authentication that were set up in PST Manager (2.x). In that case, you will not need to add users.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91;kusanagi@kusanagi8 ~]$ pst passwd add --user %USER-NAME% --pass %PASSWORD%<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Configuring_Initial_Profile_Settings\"><\/span>Configuring Initial Profile Settings<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Setup the initial profile settings to all enabled PST (2.x) profiles. The initial settings are executed with the PST (3.x) \"pst init\" command. The profile is specified at the end of the \"pst\" command. Or, the command can be executed from the profile directory (as the current directory). Note, \"kusanagi\" user or root privileges are required to execute the PST (3.x) \"pst\" command.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91;kusanagi@kusanagi8 ~]$ pst init \u30d7\u30ed\u30d5\u30a1\u30a4\u30eb\u540d<\/code><\/pre>\n\n\n\n<p>or<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91;kusanagi@kusanagi8 ~]$ cd \/home\/kusanagi\/%PROFILE-NAME%\n&#91;kusanagi@kusanagi8 %PROFILE-NAME%]$ pst init<\/code><\/pre>\n\n\n\n<p>Once the initial PST settings are complete, the PST Manager URL will be displayed.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>pst watch stopped.\npst watch started.\nInfo: open WEXAL manager form http:\/\/xxx.xxx.xxx.xxx:61000<\/code><\/pre>\n\n\n\n<p>The following steps can also be performed with PST commands. To set up by PST commands, refer to <a href=\"..\/setting\/migrate-setting-command\/\" data-type=\"URL\" data-id=\"..\/setting\/migrate-setting-command\/\">\"When Migrating from a Previous PST (2.x) - PST Commands\"<\/a> for more information.<a href=\"https:\/\/www.wexal.jp\/document-3-0-0\/migrate-setting-command\/\"><\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Opening_a_Port\"><\/span>Opening a Port<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>By default, PST Manager uses the system's global IP address, port 61000. According to your cloud environment, setup the protocol and port for PST in order to access the server using TCP protocol and port number 61000. Also, set connection restrictions for IP addresses to improve security.<\/p>\n\n\n\n<p>Note, if you use PST (2.x) Manager, this step will not be necessary because the port is already open.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Accessing_PST_Manager\"><\/span>Accessing PST Manager<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Access the PST Manager web page (URL) displayed in \"Configuring Initial Profile Settings\" on your browser. Enter the user name and password set in \"Adding Users to PST Manager\" or the user name and password used for PST (2.x) Manager at the login page.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Enabling_PST\"><\/span>Enabling PST<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Enable PST for a profile that has completed the initial setup. You can enable PST on the profile dashboard. Turn the PST switch to ON to enable PST. In addition, make sure that the switch for resource monitoring is turned on. If the profile for which you want to enable PST is not on the dashboard, it means the profile has not completed the initial setup. In that case, please refer to \"Configuring Initial Profile Settings\".<\/p>\n\n\n\n<p>Note, if PST has been enabled in PST (2.x), the settings will be the same.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Modifying_PST_Configurations\"><\/span>Modifying PST Configurations<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>You can change PST settings from profile mode on the PST Manager dashboard. Select from Smart-mode, Expert-mode, or Developer-mode. When you want to change the setting, select a new \"mode\" and click \"Change\". The default setting is \"Smart-mode\".<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Changing_PST_Smart-mode_Settings\"><\/span>Changing PST Smart-mode Settings<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>In Smart-mode, more detailed settings can be selected under \"Basic Settings\" and \"Smart-mode\" in the menu pane. Click \"Save &amp; Apply\" button after making changes.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Resource Optimization: These settings allow you to change the types and paths of resources you want to exclude from resource optimization, as well as the compression level of images.\n<ul class=\"wp-block-list\">\n<li>Optimization Strategy:\n<ul class=\"wp-block-list\">\n<li>Enable\/disable by selecting the three check boxes for images, CSS, and JS.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Image Compression Level:\n<ul class=\"wp-block-list\">\n<li>Enter the image compression level by setting a value between 1 and 100. The lower the value, the more compressed the image and smaller the file size, but the quality of the image will be lower.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\"Exclude\" Directories:\n<ul class=\"wp-block-list\">\n<li>Enter directories to be excluded from PST optimization by absolute path from the profile DocumentRoot.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\"Save\" button:\n<ul class=\"wp-block-list\">\n<li>Save the above settings.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\"Optimize Resources\" button:\n<ul class=\"wp-block-list\">\n<li>Resource Optimization is performed for all resources based on the above settings. Note, if you want to optimize a specific resource on a priority basis, click ON for \"Optimize resources with highest priority\", specify the path to the folder or file, and execute \"Optimize Resources\".<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Remove Optimized Resources: This setting allows you to delete optimized resources by specifying the time period and\/or resources.\n<ul class=\"wp-block-list\">\n<li>Remove optimized resources for a specified period of time:\n<ul class=\"wp-block-list\">\n<li>Specify the year, month, day, hour, and minute.<\/li>\n\n\n\n<li>Remove optimized resources older than the specified period by clicking the \"Remove Resources Older Than\" button.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Remove optimized resources in specified directories:\n<ul class=\"wp-block-list\">\n<li>Enter the path to the folder or file you want to remove and click \"Remove Already Optimized Resources\". Note, if you want to remove only the resources excluded from optimization, click ON for \"Remove only resources excluded from optimization\", and then execute \"Remove Already Optimized Resources\".<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Optimization Strategy: This setting allows you to change the optimization strategies generated by Strategic AI \"David\".\n<ul class=\"wp-block-list\">\n<li>Optimization Strategy Settings (Enable\/Disable):\n<ul class=\"wp-block-list\">\n<li>Enable\/disable by selecting the four check boxes \"lazy load\", \"proxy\", \"webfont\", and \"engagement delay\".<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\"engagement delay\" Exclusion Settings:\n<ul class=\"wp-block-list\">\n<li>File type, path\/needle, Strategic AI \"David\" status, and exclusion check boxes for each setting will be listed. By checking ON\/OFF, set the exclusion settings.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\"Save &amp; Apply\" button:\n<ul class=\"wp-block-list\">\n<li>Save the above settings.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p>Changes in resource optimization settings will be applied the next time PST executes resource optimization. If you want to apply these changes immediately, click the \"Optimize Resource\" button. If an optimized resource has already been generated for the resource you want to exclude from resource optimization, the resource will not be automatically removed until that resource is updated. If you want to apply these changes immediately, click the \"Remove Optimized Resources\" button.<\/p>\n\n\n\n<p>Changes to the optimization strategy will be applied the next time a request is made for a web page (URL) and PST generates an optimization strategy. Note, optimization strategies will not be generated again for a certain period of time (1 hour by default.) Therefore, changes will only take effect after the specified amount of time has elapsed and the optimization strategy is generated once again.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Changing_PST_Expert-mode_Settings\"><\/span>Changing PST Expert-mode Settings<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>In Expert-mode, more detailed settings can be selected under \"Basic Settings\" and \"Expert-mode\" in the menu pane. Click \"Save &amp; Apply\" after making changes.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Resource Optimization: These settings allow you to change the types and paths of resources you want to exclude from resource optimization, as well as the compression level of images.\n<ul class=\"wp-block-list\">\n<li>Optimization Strategy:\n<ul class=\"wp-block-list\">\n<li>Enable\/disable by selecting the three check boxes for images, CSS, and JS.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Image Compression Level:\n<ul class=\"wp-block-list\">\n<li>Enter the image compression level by setting a value between 1 and 100. The lower the value, the more compressed the image and smaller the file size, but the quality of the image will be lower.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\"Exclude\" Directories:\n<ul class=\"wp-block-list\">\n<li>Enter directories to be excluded from PST optimization by absolute path from the profile DocumentRoot.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\"Save\" button:\n<ul class=\"wp-block-list\">\n<li>Save the above settings.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\"Optimize Resources\" button:\n<ul class=\"wp-block-list\">\n<li>Resource Optimization is performed for all resources based on the above settings. Note, if you want to optimize a specific resource on a priority basis, click ON for \"Optimize resources with highest priority\", specify the path to the folder or file, and execute \"Optimize Resources\".<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Remove Optimized Resources: This setting allows you to delete optimized resources by specifying the time period and\/or resources.\n<ul class=\"wp-block-list\">\n<li>Remove optimized resources for a specified period of time:\n<ul class=\"wp-block-list\">\n<li>Specify the year, month, day, hour, and minute.<\/li>\n\n\n\n<li>Remove optimized resources older than the specified period by clicking the \"Remove Resources Older Than\" button.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Remove optimized resources in specified directories:\n<ul class=\"wp-block-list\">\n<li>Enter the path to the folder or file you want to remove and click \"Remove Already Optimized Resources\". Note, if you want to remove only the resources excluded from optimization, click ON for \"Remove only the resources excluded from optimization\", and then execute \"Remove Already Optimized Resources\".<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Optimization Strategy: This allows you to change the optimization strategies generated by Strategic AI \"David\".<ul><li>Optimization Strategy Settings (Enable\/Disable):<ul><li>Enable\/disable by selecting the four check boxes \"lazy load\", \"proxy\", \"webfont\", and \"engagement delay\".<\/li><\/ul><\/li><\/ul>\n<ul class=\"wp-block-list\">\n<li>Settings for Exclude Directives:\n<ul class=\"wp-block-list\">\n<li>Configure exclusion settings for directives. Specify the paths to be excluded by regular expressions. The following directives can be configured.\n<ul class=\"wp-block-list\">\n<li>defer external js, lazy load, lazy youtube, lazy video, link dns prefetch, link lcp preload, normalize newlines, proxy, reduce script, repair jquery, secure target blank, split inline css webfont, tidy, wp opt genericons, wp remove emoji, wp remove header, wp remove meta, wp shorten url, wp remove wpcf7<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\"engagement delay\" Exclusion Settings\n<ul class=\"wp-block-list\">\n<li>File type, path\/needle, Strategic AI \"David\" status, and exclusion check boxes for each setting will be listed. By checking ON\/OFF, set the apply and exclusion setting.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\"Save &amp; Apply\" button:\n<ul class=\"wp-block-list\">\n<li>Save the above settings.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p>Changes in resource optimization settings will be applied the next time PST executes resource optimization. If you want to apply these changes immediately, click the \"Optimize Resource\" button. If an optimized resource has already been generated for the resource you want to exclude from resource optimization, the resource will not be automatically removed until that resource is updated. If you want to apply these changes immediately, click the \"Remove Optimized Resources\" button.<\/p>\n\n\n\n<p>Changes to the optimization strategy will be applied the next time a request is made for a web page (URL) and PST generates an optimization strategy. Note, optimization strategies will not be generated again for a certain period of time (1 hour by default.) Therefore, changes will only take effect after the specified amount of time has elapsed and the optimization strategy is generated once again.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Changing_PST_Developer-mode_Settings\"><\/span>Changing PST Developer-mode Settings<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>In Developer-mode, settings cannot be changed through PST Manager. Refer to the above \"Modifying PST Configurations\" for more information.<\/p>\n\n\n\n<p>If you are in Developer-mode because you accidentally edited the PST configuration file, you can initialize the PST configuration file with the \"pst config init\" command. Refer to <a href=\".\/document-3-0-0\/pst-command\/\" data-type=\"URL\" data-id=\".\/document-3-0-0\/pst-command\/\">\"PST Commands\"<\/a> for more information.<a href=\"https:\/\/www.wexal.jp\/document-3-0-0\/pst-command\/\"><\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Optimizing_Resources\"><\/span>Optimizing Resources<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>PST Resource Monitoring Service (\"watch\") monitors changes to resources in profiles and generates optimized resource files for images, scripts, and style sheets in response to updates. However, for resources that existed in a profile before executing the initial PST configuration, an optimized resource file will not be generated until the resource is updated. Therefore, it is necessary to generate an optimized resource file for the resources in the profile.<\/p>\n\n\n\n<p>You can optimize resources from the profile dashboard on PST Manager. Resource optimization will take time if the number of resource files is large. By limiting the number of target directories to be optimized, optimization time can be shortened.<\/p>\n\n\n\n<p>Note that optimized resource files from PST (2.x) can be used. If already optimized resource files exist, optimization will not be executed.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>PST (3.x) has changed configuration from the previous PST (2.x). Therefore, a configuration migration is required. You cannot update PST by using \"yum update\". Updating from the PST (2.x) Module Before migrating to PST (3.x), update PST (2.x) to the latest version. Root privileges are necessary to update. or Updating PST (2.x) Profiles Before migrating to PST (3.x), update all PST (2.x) enabled profiles to the latest version. You can find PST enabled profiles in PST Manager. Or, you can find them with the following root privilege commands. Update profiles with the PST (2.x) \"pst\" command. Note, root privileges are required to execute the PST (2.x) \"pst\" command. If you ... <\/p>\n<p class=\"read-more-container\"><a title=\"When Migrating from a Previous PST (2.x) - Setup in PST Manager (3.0.0)\" class=\"read-more button\" href=\"https:\/\/www.wexal.jp\/en\/document-3-0-0\/setting\/migrate-setting-manager\/#more-5988\" aria-label=\"Read more about When Migrating from a Previous PST (2.x) - Setup in PST Manager (3.0.0)\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":5963,"menu_order":4,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"version":[16],"class_list":["post-5988","page","type-page","status-publish"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>When Migrating from a Previous PST (2.x) - Setup in PST Manager (3.0.0) - WEXAL\u00ae Page Speed Technology<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.wexal.jp\/en\/document-3-0-0\/setting\/migrate-setting-manager\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"When Migrating from a Previous PST (2.x) - Setup in PST Manager (3.0.0) - WEXAL\u00ae Page Speed Technology\" \/>\n<meta property=\"og:description\" content=\"PST (3.x) has changed configuration from the previous PST (2.x). Therefore, a configuration migration is required. You cannot update PST by using &quot;yum update&quot;. Updating from the PST (2.x) Module Before migrating to PST (3.x), update PST (2.x) to the latest version. Root privileges are necessary to update. or Updating PST (2.x) Profiles Before migrating to PST (3.x), update all PST (2.x) enabled profiles to the latest version. You can find PST enabled profiles in PST Manager. Or, you can find them with the following root privilege commands. Update profiles with the PST (2.x) &quot;pst&quot; command. Note, root privileges are required to execute the PST (2.x) &quot;pst&quot; command. If you ... Read more\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.wexal.jp\/en\/document-3-0-0\/setting\/migrate-setting-manager\/\" \/>\n<meta property=\"og:site_name\" content=\"WEXAL\u00ae Page Speed Technology\" \/>\n<meta property=\"article:modified_time\" content=\"2023-01-06T13:00:53+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.wexal.jp\/wp-content\/uploads\/2021\/10\/wexal_og.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.wexal.jp\\\/en\\\/document-3-0-0\\\/setting\\\/migrate-setting-manager\\\/\",\"url\":\"https:\\\/\\\/www.wexal.jp\\\/en\\\/document-3-0-0\\\/setting\\\/migrate-setting-manager\\\/\",\"name\":\"When Migrating from a Previous PST (2.x) - Setup in PST Manager (3.0.0) - WEXAL\u00ae Page Speed Technology\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.wexal.jp\\\/#website\"},\"datePublished\":\"2021-08-25T16:05:07+00:00\",\"dateModified\":\"2023-01-06T13:00:53+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.wexal.jp\\\/en\\\/document-3-0-0\\\/setting\\\/migrate-setting-manager\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.wexal.jp\\\/en\\\/document-3-0-0\\\/setting\\\/migrate-setting-manager\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.wexal.jp\\\/en\\\/document-3-0-0\\\/setting\\\/migrate-setting-manager\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.wexal.jp\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentation (3.0.0)\",\"item\":\"https:\\\/\\\/www.wexal.jp\\\/en\\\/document-3-0-0\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Settings (3.0.0)\",\"item\":\"https:\\\/\\\/www.wexal.jp\\\/en\\\/document-3-0-0\\\/setting\\\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"When Migrating from a Previous PST (2.x) - Setup in PST Manager (3.0.0)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.wexal.jp\\\/#website\",\"url\":\"https:\\\/\\\/www.wexal.jp\\\/\",\"name\":\"WEXAL\u00ae Page Speed Technology\",\"description\":\"the best UX for all Websites.\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.wexal.jp\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"When Migrating from a Previous PST (2.x) - Setup in PST Manager (3.0.0) - WEXAL\u00ae Page Speed Technology","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.wexal.jp\/en\/document-3-0-0\/setting\/migrate-setting-manager\/","og_locale":"en_US","og_type":"article","og_title":"When Migrating from a Previous PST (2.x) - Setup in PST Manager (3.0.0) - WEXAL\u00ae Page Speed Technology","og_description":"PST (3.x) has changed configuration from the previous PST (2.x). Therefore, a configuration migration is required. You cannot update PST by using \"yum update\". Updating from the PST (2.x) Module Before migrating to PST (3.x), update PST (2.x) to the latest version. Root privileges are necessary to update. or Updating PST (2.x) Profiles Before migrating to PST (3.x), update all PST (2.x) enabled profiles to the latest version. You can find PST enabled profiles in PST Manager. Or, you can find them with the following root privilege commands. Update profiles with the PST (2.x) \"pst\" command. Note, root privileges are required to execute the PST (2.x) \"pst\" command. If you ... Read more","og_url":"https:\/\/www.wexal.jp\/en\/document-3-0-0\/setting\/migrate-setting-manager\/","og_site_name":"WEXAL\u00ae Page Speed Technology","article_modified_time":"2023-01-06T13:00:53+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.wexal.jp\/wp-content\/uploads\/2021\/10\/wexal_og.png","type":"image\/png"}],"twitter_card":"summary_large_image","schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.wexal.jp\/en\/document-3-0-0\/setting\/migrate-setting-manager\/","url":"https:\/\/www.wexal.jp\/en\/document-3-0-0\/setting\/migrate-setting-manager\/","name":"When Migrating from a Previous PST (2.x) - Setup in PST Manager (3.0.0) - WEXAL\u00ae Page Speed Technology","isPartOf":{"@id":"https:\/\/www.wexal.jp\/#website"},"datePublished":"2021-08-25T16:05:07+00:00","dateModified":"2023-01-06T13:00:53+00:00","breadcrumb":{"@id":"https:\/\/www.wexal.jp\/en\/document-3-0-0\/setting\/migrate-setting-manager\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.wexal.jp\/en\/document-3-0-0\/setting\/migrate-setting-manager\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.wexal.jp\/en\/document-3-0-0\/setting\/migrate-setting-manager\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.wexal.jp\/en\/"},{"@type":"ListItem","position":2,"name":"Documentation (3.0.0)","item":"https:\/\/www.wexal.jp\/en\/document-3-0-0\/"},{"@type":"ListItem","position":3,"name":"Settings (3.0.0)","item":"https:\/\/www.wexal.jp\/en\/document-3-0-0\/setting\/"},{"@type":"ListItem","position":4,"name":"When Migrating from a Previous PST (2.x) - Setup in PST Manager (3.0.0)"}]},{"@type":"WebSite","@id":"https:\/\/www.wexal.jp\/#website","url":"https:\/\/www.wexal.jp\/","name":"WEXAL\u00ae Page Speed Technology","description":"the best UX for all Websites.","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.wexal.jp\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"}]}},"_links":{"self":[{"href":"https:\/\/www.wexal.jp\/en\/wp-json\/wp\/v2\/pages\/5988","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wexal.jp\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.wexal.jp\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.wexal.jp\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wexal.jp\/en\/wp-json\/wp\/v2\/comments?post=5988"}],"version-history":[{"count":7,"href":"https:\/\/www.wexal.jp\/en\/wp-json\/wp\/v2\/pages\/5988\/revisions"}],"predecessor-version":[{"id":6574,"href":"https:\/\/www.wexal.jp\/en\/wp-json\/wp\/v2\/pages\/5988\/revisions\/6574"}],"up":[{"embeddable":true,"href":"https:\/\/www.wexal.jp\/en\/wp-json\/wp\/v2\/pages\/5963"}],"wp:attachment":[{"href":"https:\/\/www.wexal.jp\/en\/wp-json\/wp\/v2\/media?parent=5988"}],"wp:term":[{"taxonomy":"version","embeddable":true,"href":"https:\/\/www.wexal.jp\/en\/wp-json\/wp\/v2\/version?post=5988"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}