The XM environment is already running, but the admin interface is in the default English. This time, we'll introduce the steps to add Japanese language resources, enabling the use of Japanese in the admin interface.
![](/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzi1ovlormku8%2F2n6eEmu2oIISziNqtizGWT%2F85364ae6e92dc36411bc3eb20aa6bd52%2Fjajp02.png&w=3840&q=75)
Preparation of Japanese resources
This time we will apply the Japanese resources for XM1 and SXA. This file can be downloaded from the following Web site
Easy to deploy
An easy way to deploy the files is to deploy them in the docker\deploy\platform\App_Data folder. Make sure the files are located as follows
![jajp01.png](/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzi1ovlormku8%2F2o7MoWxTbNO6pG11QiGJtr%2F56b752750076532b8a6a76755d66cac1%2Fjajp01.png&w=1920&q=75)
When Sitecore is started in this state, Japanese resources will be imported. Since the administrative resources will be added to the Core database, the following additional work is required
- Access to Desktop
- Switch to Core database
- Starting the Control Panel
- Click Add a New Language to add japanese-japan.
Japanese data will now be valid.
![jajp02.png](/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzi1ovlormku8%2F2n6eEmu2oIISziNqtizGWT%2F85364ae6e92dc36411bc3eb20aa6bd52%2Fjajp02.png&w=3840&q=75)
In terms of verifying the behavior, we can see that placing files in this folder is reflected in the cm container.
Add to project and deploy
In the case of the above deployment, the problem is actually that running clean.ps1 under docker will delete the resource files. This is because all the files under docker(docker\deploy) will be deleted. It is a hassle to add Japanese resources every time because we often use it to revert the environment back to the beginning. Therefore, we will introduce a procedure to incorporate them into the files deployed by Solution.
- Extract the same file as above to src\Platform\App_Data
![jajp03.png](/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzi1ovlormku8%2FhhK1K4bKA9Y5fk2ixhg9X%2Fb4c212bc317755948a0ee3fbedcea4be%2Fjajp03.png&w=1920&q=75)
- Visual Studio solution file is located at the top of the project, use it to start Visual Studio
- For files added to the project
![jajp04.png](/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzi1ovlormku8%2F6cugzXdnv5UQVrF7WLgW3T%2Fd34dbbde404ff1f47778588587001010%2Fjajp04.png&w=2048&q=75)
- Rebuild the solution and make sure it succeeds
Now you are ready. To reflect this in the image, execute the following command
docker compose build
After completion, start the system and confirm that the files have been extracted to the cm container.
![jajp05.png](/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fzi1ovlormku8%2F6xNohE3RgeKu0AW1cKCKQ9%2F4dc16e9e04bc8d4f12f1207e2c29e7d4%2Fjajp05.png&w=1920&q=75)
In this form, the file is maintained after clean.ps1 is run, eliminating the need to perform the Japanese resource procedure each time.
Summary
This time we introduced two procedures for importing Japanese resources. If you have a configuration file that you want to reflect on the CM server, you can use this procedure to verify and deploy the file.