This project was developed by a team of students at the Center for Enterprise Information Research at the University of Koblenz. The HCL Connections Community Copy App is a Node.js application for copying communities including the content, such as wiki pages, blog posts, files and others. It makes use of Connections' APIs and basic authentication.
All credit goes to the students, who developed this application: Janos Justen, Lisa Küppers, Dominik Lienen, Tim Merzhäuser, Lennard Metzler, Manuel Musialik and Andreas Weber. The project was supervised by Julian Mosen and Prof. Dr. Petra Schubert.
Set up project locally for development
After the repository has been cloned, execute npm install in the repository directory via the console. This will install all dependencies defined in the package.json.
To run the application locally, the development proxy server must be configured. To do this, copy the file "proxy.conf.json.template", name the copy "proxy.conf.json" and enter a valid authentication for the copied version. To do this, use for example https://www.blitter.se/utils/basic-authentication-header-generator/ (username+password are those you use to log in to the IBM Connections test system.
Start the development server with npm start. If changes are made to the source files, the application reloads automatically.
The url of the test system is entered under src/assets in the config.json, and in 3 places in the proxy.conf.json. Furthermore, adapted to the test system, the Basic Auth Token has to be regenerated (see above)
Development is done in the src/app directory. Newly created components (ng generate component xyz) have to be moved to the corresponding subfolder in /components. Auxiliary classes for certain functions (e.g. XML parser) are located in the /helpers directory. Models, which represent entities of the Connections-Api (e.g. a community) can be found in /models, Angular Services in /services.
ng build --prod executes the build; the created artifacts end up in the dist/ folder The --prod flag executes a production build. The relative path under which the application is productively hosted must be entered in the angular.json in the configuration of the production build under baseHref.
Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.
The project was generated with Angular CLI version 8.0.0.