Solutions:

using the configuration file, put the information such as password in a configuration file, run the package when read from the configuration file (the configuration file is best stored in a safe place) to replace the ProtectionLevel that package EncryptSensitiveWithPassword and set the password, open CommandLines after deployment, will be prompted for a password, after input, run the package successfully. After deployment, enter DataSource, check the required DataSource, and then enter CommandLines. The previously selected DataSource will be automatically generated in it, and Password will be edited into it.

The first is a formal approach, good security, but more troublesome, because to deploy to a remote server, but do not have the authority to put configuration files into this server, so temporarily unable to adopt this approach.
The latter two are gradually tried out by myself. They are simple and not safe (especially the third one).

Reproduced in: https://www.cnblogs.com/Muller/archive/2012/02/16/2354377.html