bitnami alfresco community admin console url

Bitnami alfresco community admin console url how to#
Bitnami alfresco community admin console url update#
Bitnami alfresco community admin console url code#

If you are following along: git checkout step2Īt this point Alfresco is running and a Node.js app is running. Step 2: Add a service class and web script run.sh build_start then invoke this URL in your browser: The API returns a list of project names and IDs as JSON. This is the original docker-compose.yml file provided by the Alfresco SDK, updated to include the new projects API. All we need to do is add it to the docker-compose.yml file that was bootstrapped when we created the project so that Docker Compose will create and run a container for the API alongside the containers for ACS, Share, and the others. Now we have a new Maven module called fake-projects-api that will build a Docker image that has the Node.js app. This is a Dockerfile that builds the image with Node.js, Express, and the API app.

fake-projects-api/src/main/docker/Dockerfile.

This is a Node.js app that establishes an API endpoint and returns the project list as JSON.

fake-projects-api/src/main/docker/server.js.

fake-projects-api/src/main/docker/projects.json.

This is the POM file for the new Maven module. So, we’ll add a new container to our Docker setup so that when we run Alfresco locally it will launch the fake API app. A really easy way to do that is with Node.js and Express. We want an API that returns a list of projects as JSON. If you are following along: git checkout step1 Step 1: Add a simple API to return project data

Bitnami alfresco community admin console url how to#

Once those steps are complete the path diverges: one step shows how to implement the custom admin console in Enterprise Edition and the other shows how to do it in Community Edition. The first three steps are about setting up the fake API as a Docker container, implementing a repo tier web script to fetch project data from the API, and then implementing a simple UI action that displays the project data in a Share dialog. We’ll optionally switch over to Enterprise Edition in a while when the implementation steps become edition-specific. At this point it is configured to use Community Edition.

Bitnami alfresco community admin console url code#

The code now reflects an empty project created from the Alfresco SDK. If you are going to follow along, clone the project: git clone After you clone the repository you can switch between steps by doing git checkout step1 or git checkout step2 etc. When you’re done, you’ll be able to invoke the API from Share and then change the API endpoint via the Alfresco admin console, and see that change reflected immediately on subsequent invocations from Share. It doesn’t really matter what we do with the data because the point of this example is to show how to make the API endpoint configurable via the admin console. On the Alfresco side, we’ll create a UI action that gets the project list from the API and displays the projects in a dialog. In the real world your API won’t likely be part of the project–we use this “fake” API here as a convenient stand-in for demonstration purposes. This example uses a basic API built using Node and Express that returns a list of project names and IDs.

Bitnami alfresco community admin console url update#

This post shows how to add your own admin console panel to update settings of your custom service classes at runtime whether you use Enterprise or Community Edition. We could put it in the alfresco-global.properties file and read it from there, which is a little better, but not great.Īlfresco already has an admin console that it uses to display and, in the case of Enterprise Edition, manage settings at runtime. We could hardcode the project API URL, but then we’d have to build and deploy if it ever needs to be changed. The service class will need to know the URL of the project API. It would be a good idea to centralize the logic that invokes the project API in a service class. And, maybe we want to do something with that data from Alfresco. Maybe it has a REST API that returns a list of projects. One way to handle this is to add your own custom admin console panels to the out-of-the-box Alfresco admin console.įor example, suppose that at our company there is a system that manages data about our projects. A common requirement for an Alfresco installation is the need to update configuration on customizations at runtime.