Activator automatically imports community or partner profiles written to a certain system directory. These must be profiles that have been exported from B2Bi, or from Interchange or Activator.
Profiles written to <install directory>\profiles\autoImport are imported by Activator when the server is running. Once imported, the system moves the profiles files from profiles\autoImport to the appropriate profiles\backup subdirectory, either community or partner. The system makes all imported partner profiles members of all communities. The system creates pickups and deliveries for an imported community.
If Activator is unable to import a profile file in the autoImport directory, the system moves the file to \profiles\autoImport\rejected.
| Note | If you have exported a community and its partners to a backup file (see Back up a community and its partners ), do not use the autoImport directory to import the file. Activator rejects the file. |
The system also has some profile staging directories, as shown in the following illustration. The system does not write to these directories, except during installation when a user is upgrading from a previous version. The directories are a place to hold profile files before a user moves them to the autoImport directory. The software installer, for instance, writes profile files to the staged directories if the user during installation chooses to have profiles exported from an earlier version of Activator.
|
\profiles |
\autoImport |
\rejected |
|
|
\backup |
\community\partner |
|
|
\staged |
\community\partner |
Activator cannot import a password-protected profile through the autoImport directory. The password protects the certificate private key. Make sure to securely handle a company profile exported without a password.
Events for profile imports and rejects are written to control node events log(hostname_cn_events.log)in the logs directory. The events are:
Administration.Configuration.Party.CommunityImported
Administration.Configuration.Party.PartnerImported
Administration.Configuration.Party.ImportFailedSecret1