Validating the proe2pv Configuration
Validate your configuration by following the next steps:
1. After exiting proe2pv_config, verify that the following files are now located in the <setup_directory> specified earlier:
a. proe2pv_config.log—Log file created by the tool during the configuration process. See this log file for details on any configuration issues.
b. adapter.pvi—Lets you determine whether a directory has a configuration and for which adapter. Windows users can double-click this file to open the configuration tool for an adapter, with the appropriate data filled in.
c. debug_options.txt—Provides extra command line options to the adapter when it has to run in verbose (debug) mode. When Start verbose workers option is enabled in the Worker Agent Administration window, any worker that is started from this window includes options specified in this debug options file.
For details on the command line options, see the Advanced Adapter Configurations chapter for your adapter type.
e. proebatch.bat—Command line publishing script. Review the section
proebatch Overview for instructions for using this script.
f. proepublish.bat—Interactive publishing script. Review the section
proepublish Overview for instructions for using this script.
g. proeworker.bat—Server controlled publishing script. Review the section
proeworker Overview for instructions for using this script.
h. proipublish.bat—Pro/INTRALINK publishing script. Instructions for using this script were provided in the previous section.
i. protk.dat—An internal file required by the adapter.
j. purge.bat—Removes all log files generated by the adapter from the <setup_directory>.
2. You can verify each component of your configuration is working correctly by the following methods:
a. Follow the instructions in
Interactive Publishing to use proepublish. Successful interactive publishing confirms your
Creo Parametric environment supports proepublish.
b. Follow the instructions in
Command Line Publishing to use proebatch. Successful batch publishing from the command line means the environment of your configuration supports command line publishing.